Yes, turning on ipv6 should not break the net. Let me introduce you to the concept of ”shitty modems from shitty isps”.
Yes, turning on ipv6 should not break the net. Let me introduce you to the concept of ”shitty modems from shitty isps”.
eg, when Netflix started blocking IPv6 tunnel brokers in their VPN crackdown, my house was affected and Netflix was broken. As a "short term" fix, I blocked traffic towards the v6 tunnel at the firewall, but was too lazy to disable v6 prefix advertisement or actually take the tunnel down. I intended to revisit the whole situation, but forgot.
Despite all the devices on my home network having global v6 addresses, you'd never know that anything is broken because Happy Eyeballs is working as intended across everything - Mac OS, Linux, iOS, Android, Windows.
If you want me to debug why this happens, we have some papers to sign and retainers to pay ;)
Also, not every protocol is compatible with Happy Eyeballs, because there's no guarantee that opening a connection is harmless. It's perfectly valid for me to e.g. implement a smart lightbulb protocol by having it toggle off/on when it receives a connection from a trusted network interface without actually requiring data to be sent. If you used Happy Eyeballs in this case and both IPv4 and IPv6 worked, you wouldn't be able to turn on your lights. This is of course a contrived example, but the authors of generic libraries like your libc have to worry about contrived examples.
So it has to be implemented by application software or at least a library for the specific protocol like HTTP (layer 5 or up), which means that in practice, lots of apps won't have it implemented. And therefore in practice, broken or degraded IPv6 is very end-user visible.