4 ms·
Yeah, it's not the network admins, they want IPv6 too. If at all possible our network admins want IPv6 only networks, the sad fact is that it's not possible in
by mrweasel 6y ago
Yeah, it's not the network admins, they want IPv6 too. If at all possible our network admins want IPv6 only networks, the sad fact is that it's not possible in most cases.
We had to return stacks of Cisco equipment, because despite being brand new it had no IPv6 support. We should have checked of cause, but we just didn't imagine that you could buy IPv4 only equipment in 2020.
Software is even worse, we have had software that advertised IPv6 support, so we build an IPv6 only solution, only to find out that the manufacturer has NEVER had a customer using their software on IPv6. They tested it six years ago and never followed up, meaning that IPv6 does actually work in the latest versions.
Docker is another example, who in their right mind designed Docker to be a IPv4 only solution and then attempts to bolt on IPv6 later. It should have been IPv6 and then if you really needed it you could add an IPv4 ingress. Most of the issues we have experience using Docker could have been avoided by using IPv6 and dropping IPv4 all together.
- magicalhippo 6y ago> Software is even worse Indeed. Even stuff like pfSense has only rudimentary IPv6 support. And I guess software support is poor because they're still figuring out how to actually deploy IPv6, churning out new RFC's[1]. [1]: https://tools.ietf.org/html/draft-gont-v6ops-ipv6-addressing-considerations-00 https://tools.ietf.org/html/draft-gont-v6ops-ipv6-addressing... (random example)
- iam-TJ 6y agoWhat is even more incredible in 2020 is that docker.com and hub.docker.com do not host on IPv6 .... and they're on AWS. We discovered this due to operating an IPv6-only network and having to deploy NAT64/DNS64* on the edge specifically for reaching hub.docker.com * NAT64/DNS64 was trivial to set up (Tayga + bind9) - took 2 hours for a networking apprentice