top | item 41603845

(no title)

paperplatter | 1 year ago

The second thing is the problem with not having NAT. On a home or corp network, I like NAT. I'm not trying to host 20 servers there. Sure ipv6 can use it too, but it's never default and often not supported on the router.

So yeah, 192.168.1.55 is my Mac's local ip, it's easy to remember.

discuss

order

zamadatix|1 year ago

Inside the home you can usually get away just using the internal link local addresses. E.g. my main PC is fe80::10, my wife's pc is fe80::11, my router is fe80::. You can even use that when you get "fancy" e.g. my NAS is fe80::12 internally or ${public_prefix}::12 "externally" (that one actually works on either side).

This address will also run afoul with the "privacy first" randomizations on most devices by default. This addition is truly the scourge of letting IPv6 seem dead simple to use.

nottorp|1 year ago

And we're getting back to that old problem. Why isn't the link-local IPv6 address automatically fe80::10 if the IPv4 is 192.168.1.10? :)

paperplatter|1 year ago

I agree then, the defaults are a problem.