4 ms·
> but what you need here is an ISP that handles IPv6 prefixes properly It's hard to get ISPs to do things properly in general; if it's for IPv6, it's even more
by toast0 4y ago
> but what you need here is an ISP that handles IPv6 prefixes properly
It's hard to get ISPs to do things properly in general; if it's for IPv6, it's even more difficult. I think the intent of IPv6 designers was for hosts to manage to be prefix fluid; you might set up ULAs for local traffic, and use whatever prefixes are advertised for non-local traffic. Of course, that's harder to do than to write an RFC about, so I can understand resorting to prefix translation to get things done in the way desired. Prefix translation has the potential to be stateless which is nice for resource management on the translation element, though.
- nybble41 4y ago> Prefix translation has the potential to be stateless which is nice for resource management on the translation element, though. It really messes with protocols where you need to tell another host how to contact you, though, since you don't know your "real" IP address without asking some other server. This gets worse if there is more than one level of translation involved. You also need hacks like "hairpin NAT" (wastefully passing local traffic through the router) since local hosts trying to connect to the public IP of a local server don't realize that they can reach it directly via the ULA. > … you might set up ULAs for local traffic, and use whatever prefixes are advertised for non-local traffic. This is the way.