IPv6 Networking Challenges
Comments debate IPv6 deployment in local networks, focusing on address stability, privacy extensions, prefix changes from ISPs, multiple addresses per interface, and comparisons to IPv4 NAT practices.
Activity Over Time
Top Contributors
Keywords
Sample Comments
Seriously, using IPv6 really does helps in this case!
Is see no reason why you couldn't do the same with IPv6 - setup dhcp with ULAs and static ips, perhaps with a hosts table or local dns to keep things readable.
Your post is the kind of thing that seems intuitively to be the case, but is actually not in any practical setups.Unless you hardcode your IPv6 addresses, they will be generated automatically and change quite frequently. So the addresses become pretty meaningless and all you have to identify your devices really is the prefix of your network - pretty much the same amount of information as a network behind a NAT'ed IPv4 address.In fact, as far as I remember you can actually statically a
> - I don't have a shortage of IPv4. Maybe my ISP or my VPN host do, I don't know. I have a roomy 10.0.0.0/8 to work with.Remember, mate, with a /64 you can host your own ISP. You can finally have real Internet access! (Oh, wait -- it's not actually your /64 and your local ISP[s] wouldn't route it to you if it were, so you really can't.)> - Every host routable from anywhere on the Internet? No thanks. Maybe I've been irreparably corrupt
TLS SNI routing has fixed the multiple authorities listening on one IPv4 address port 443.Most ISP’s implement IPv6 by using the single IPv4 address as a v6 prefix. This results in the entire LAN needing to change local addresses every time the public IP changes. In practice this means a single brief power outage causes hundreds of devices to break instead of none.Generally speaking ipv6 is useless for most home network users.Overlapping 10/8 with corporate networks is not a probl
Yes. And it's not just multiple IPv6. I don't know iOS, but Windows, OS X and Debian all use only "privacy-friendly" (RFC 4941) IPv6 with remote devices. And they change frequently. That gets to be a pain when you're pushing static routes. NAT was so easy.
Nating in the context of ipv6 is not a common thing. It is the exception, while it's the rule for ipv4
IPv6 has link-local, v4 doesn't. That is a huge configuration win.
The reassingment of ipv6 networks is annoying. My provider gives me an new 64 network on each reconnection, so i have to use the equivalent of the private adresses in my homenetwork.
How does it work with IPv6, where there is no (need for) LAN (unless maybe if you're a huge company) ?