On 2026-09-21 21:56:18 +0100, [email protected] wrote: > Marco Moock <[email protected]> wrote: > > Am 21.09.26 um 18:30 schrieb CGS: > > > IPv6 seems to be the future, so I guess these problems will > > > eventually fade away, although the OP has been struggling since > > > 2015 (!), apparently, which is a testament to something. > > > > Some people actually do not want to fix problems, like here with the > > RAs that come from some machines that must not send them. > > > > Then they try to "fix" that by disabling IPv6. > > As I understand it, Vincent is a user of a large academic network run > by ENS-Lyon. He doesn't have any administrative capabilities or > responsibilities for that network. So there's no way he can fix > problems on some other host belonging to somebody else on that network. > He can only change things on his own systems, and can send requests to > network managers he doesn't have any direct dealings with.
Exactly. Of course, at that time, I asked the admins to take measures to filter RAs. They answered me something like this was not possible with their old routers (which might be the same reason why we still do not have IPv6 here: old material, but also too few admins to take care of the problems). I don't know whether things have improved since 2015, but a few months ago (in March), on one of my machines, a "nameserver fe80::a4cf:99ff:fe46:c64%enp0s25" line appeared in /etc/resolv.conf (generated by NetworkManager), apparently due to some rogue RA. -- Vincent Lefèvre <[email protected]> - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / Pascaline project (LIP, ENS-Lyon)
