On Sun, 20 Sep 2026 20:41:21 +0200 <[email protected]> wrote: > On Sun, Sep 20, 2026 at 03:18:12PM -0000, CGS wrote: > > On 2026-09-19, Vincent Lefevre <[email protected]> wrote: > > >> > > >> Isn't significant part of this thread is dedicated to arguments > > >> that you should not disable IPv6? > > > > > > No-one has explained why IPv6 should not be disabled. And in any > > > case, > > > > Conversely, have you explained why IPv6 was disabled? I may have > > missed it in this long thread, but it obviously adds a layer of > > complexity to whatever problem you're trying to solve as an > > non-priviledged user. > > Yes, it was explained in this thread. AFAIR, the box receives IPv6 > router advertisements, so it thinks it has IPv6 connectivity, but the > routes lead to nowhere. > > Correct me if I'm wrong, though. >
For completeness, I was also in the thread early with a need to disable it. Short version: my ISP does not (yet) provide IPv6 connectivity, and my router was supplied by the ISP so already had IPv6 disabled. I was having trouble with DNS failures due to bind9 not finding an IPv6 route out of the network and giving up, even though the requested host also had an IPv4 address. I was advised that disabling IPv6 in the kernel was the final fix, so I did that to the two Raspberry Pis which were having the problems, mostly of finding RPi apt repositories. No good. I had to disable it individually in both bind9 and apt to get reliable IPv4 lookups. I left the thread at this point. -- Joe
