2 ms·
> People still don't think IPv6 first, so it's always a separate project to tack it back on. This is a pretty big problem too because there are many services t
by djsumdog 10y ago
> People still don't think IPv6 first, so it's always a separate project to tack it back on.
This is a pretty big problem too because there are many services that don't take firewalls into account. They're two totally different protocols and have two firewall stacks (iptables/ip6tables). I don't know if Windows Sever is any better at either abstracting both firewall sets or ensuring you are explicitly warned if you leave IPv6 addresses in a different firewall state than IPv4.
Amazon's IPv6 support is pretty horrible, and that's terrible consider just how much of the world runs on Amazon and our total exhaustion of IPv4 addresses.
Without broad scale IPv6 deployment, we're going to get into a split-Internet situation where people will not be able to reach an audience without an expensive legacy IPv4 address.