Not a popular idea here, but IPv6 folks. Even for k8s, even for your internal stuff.
Why is IPv6 not a popular idea here?
Did AS8003 just disappear?
71–75 of 75 posts
Re: Did AS8003 just disappear?
#72Not a popular idea here, but IPv6 folks. Even for k8s, even for your internal stuff.
offtopic: ipv6 is fine, but the ipv6 internet is just broken few days ago I had ipv6 enabled on my pi4 and was trying to update it, turns out that the ipv6 address of archive.raspberrypi.org was returning 404 (its fixed now) but it took me like 3 seconds to just net.ipv6.conf.all.disable_ipv6 = 1, and i am not gonna enable it until something on ipv4 does not work (and by ipv6 i mean native ipv6 from my ISP) it has be…
Happy Eyeballs (RFC 8305) is the typically touted solution, but even that doesn't help in the scenario you describe: IPv6 connectivity wasn't broken.
The problem is simply that we now have twice as many things that can go wrong and no plausible route away from dual stack in sight.
Re: Did AS8003 just disappear?
#73Earlier quoted context omitted.
That is one of the most disappointing aspects of ipv6. Even if you implement it perfectly you are still stuck with having to deal with ipv4 with no end in sight. Had backward compatibility been a primary goal, is there any doubt we would have made vastly more progress at this point 20+ years later?
It's an address space expansion. You were always going to need hacky stuff for legacy clients, and for any service that wants to be reachable by said clients.
Exactly this. There is no "backwards compatible" way to have more addresses in a protocol that's wedded to 32-bit addresses. That's just how numbers work. The protocol with a larger address space will be incompatible, and so anybody who seems surprised/ disappointed hasn't even really thought about the problem.
Re: Did AS8003 just disappear?
#74Entire comment thread is irrelevant bikeshedding.