On Sat, 28 Jan 2023 20:55:18 +0000 Andy Smith <a...@strugglers.net> wrote:
> Hi, > > On Sun, Jan 22, 2023 at 11:42:18PM -0500, Celejar wrote: > > Shouldn't this be included somewhere prominently in the Debian > > documentation, in the form of a Big Fat Warning that the standard > > dual-stack condiguration used by Debian can cause serious breakage if > > one's ISP doesn't support IPv6? > > Not having IPv6 is not the problem. As you discovered later in this > thread, your ISP is providing just enough IPv6 for your router to > think it has a v6 block to hand out, but not enough that it actually > works. It's a misconfiguration by your ISP and not something that > any operating system's documentation needs to point out. They could > also let you connect to them but make IPv4 not work, it's just that > you'd notice that very quickly! Understood. There's apparently even a quasi-official name for this: "IPv6 brokenness": https://en.wikipedia.org/wiki/IPv6_brokenness_and_DNS_whitelisting > In the field of IPv6 deployment, IPv6 brokenness was bad behavior seen > in early tunneled or dual stack IPv6 deployments where unreliable or > bogus IPv6 connectivity is chosen in preference to working IPv4 > connectivity. This often resulted in long delays in web page loading, > where the user had to wait for each attempted IPv6 connection to time > out before the IPv4 connection was tried. These timeouts ranged from > being near-instantaneous in the best cases, to taking anywhere between > four seconds to three minutes. The article proceeds to assure the reader that: > IPv6 brokenness is now generally regarded as a solved problem for > almost all practical purposes, following improvements at both the > transport and application layers. But I guess I've managed to encounter a "practical" instance of current IPv6 brokenness :| ... > Anyway, if the ISP can't fix the IPv6 and can't be convinced to stop > advertising it even when it doesn't work, I think you'd be best Makes sense - I think I've seen other users of my ISP stating in online forums that that's what they had to do at some point. > off trying to disable radvd on the router. Failing that, disabling > IPv6 on all your clients (check your phones too, as they will try Thank you. -- Celejar
