Remix.run Logo
hrmtst93837 2 hours ago

Assuming IPv6 kills NAT is optimistic, plenty of orgs still stack private addressing and firewalls on top.

lxgr an hour ago | parent [-]

Firewalls aren't nearly as bad as NAT.

hdgvhicv an hour ago | parent [-]

Basically the same thing. If you legitimately need to establish a connection then put a firewall rule in, whether that needs nat or pat is a function of your available addresses.

If you are tying to work around your firewall because it isn’t yours, that’s not a legitimate use.

lxgr 11 minutes ago | parent [-]

Love it when random people tell me whether my use case is legitimate or not without apparently even knowing it exists!

Take mobile data connections, for example: Most people don't want to pay for metered (by the byte) inbound traffic they didn't ask for that also drains their battery, but do want to be able to establish P2P connections for lower latency VoIP etc.

This is a firewall that's definitionally "not theirs", but that still also serves their interests, yet usually doesn't offer any user-accessible management interface.

So may I please traverse this firewall now, or is my use case still illegitimate?