Hello, On Tue, Aug 02, 2022 at 04:38:31PM -0000, Curt wrote: > I'm uncertain what happens with local addresses [in IPv6], if > anything.
At the moment if you are using RFC1918 IPv4 addresses on your network, it's either an isolated network, or else it has a router that does NAT to convert those to other IPv4 addresses, usually globally routable ones. So that stays working like that for a very long time. It is already possible to instead have the router convert v4 to v6 and have the Internet traffic all be IPv6 but this would be a quite strange and specialised configuration as not everything on the Internet HAS a v6 address. For example, if you browse to https://github.com/, it doesn't have a v6 address, so what would the router translate to in this case? Similarly, it is already possible to have your local network be IPv6-only and have the router convert anything that is v4-only back to IPv4. Some mobile networks work like this, and more and more networks might go this way as v6 eclipses v4, but that is very far in the future. Right now it's a lot simpler to just continue dual stack leaving v4-only things to use the local v4 address, because if it becomes an issue it's one that can be fixed by both ends enabling IPv6 and users not having to take an action. As others have mentioned, if you particularly wanted a local v6 network that wasn't reachable from outside then there are blocks set aside for that. Unlike in IPv4 where the RFC1918 addresses are not routable by a matter of convention, the equivalent in IPv6 are just not routable by the protocol. You have to go out of your way to NAT them to/from routable addresses to have IPv6 packets traverse. Cheers, Andy -- https://bitfolk.com/ -- No-nonsense VPS hosting
