ThreeHalflings @ ThreeHalflings @lemmy.world

Posts

19

Comments

65

Joined

2 yr. ago

Moderating

---

And we're just ignoring the whole weapons proliferation side of things?

Pretty sure the ball bits are always screwed on (Archer: Phrasing!). If it's coming loose some locktite or nylon plumber's tape should hold it in place.

OK, I didn't read before answering, probably ignore my answer below but I'll leave it up incase someone learns something from it.

Edit: misunderstood what OP wanted to do, leaving this here in case it's interesting to anyone.

Sounds like what you are tyring to do is called Split Horizon DNS.

Requests from outside your network should resolve server.domain.com to the public IP, but requests from inside your network should resolve it to the private IP.

If that's what it is then you register the public IP with your nameservers. You also run a DNS service internally which you point all your computers at (likely by putting it as the DNS server in your networks DHCP settings). That DNS server is set up to return the private ip addresses for all your servers, and to forward any other requests to some external DNS like 1.1.1.1

I'm not sure what your use case or for needing to use the internal IP address from inside the network, but it might be to avoid traffic exiting your network just to be sent back in? Or you me a that you want external requests to go to one server and internal to go to another server? I'm which case the set up above still works, but on just use the appropriate IP addresses in the appropriate places.

An effect can be observable but still negligible in terms of the actual increase of risk.

You think a mercury sandwich isn't a realistic representation of wood.

Wow, you know, after careful consideration I think you may be right. Thanks for your wisdom. Truly enlightening.

I'll go eat some wood.

Sometimes I just don't bother learning new stuff till the old stuff stops working for me. It's amazing how many really simple things people stroll past on their way to god knows where.

If something is part edible and part not, then it really depends on the nature of that not edible bit. If it's inert, then great. If it's not, then you could be kinda fucked.

The fact that something is 45% edible says precisely nothing about whether or not it is edible.

Wood is just less than half cellulose by weight, so wood must be safe to easy.

This mercury sandwich is just less than half bread by weight, so it must be safe to eat.

The answer used to be John the Ripper, but I'm a decade out of date on this stuff, so it might not be any more.

Also, thanks, that's awesome!

OK, but is coffee a soup?

Start with -2 bread and add one bread.

You can fear the implications of war without thinking you'll lose it.

/c/mildlyinteresting

This is a technology post, not a "buy this car next" post. It's moot if all you care about is your next car.

Maybe I'm biased because my only experience with arch in the past five years was install, boot, update packages, reboot, fail to boot, laugh, install Debian.

They're usually clearly documented in support forums by people saying "MY STUFF WON'T BOOT PLESE HALP"

Also worth saying 99.9% of air gap failures are due to some idiot getting lazy with a usb stick or a phone. They're a bitch to work with.

(Another 0.09% are someone plugging the wrong cord into the wrong switch by accident or stupidity)