On Fri, 17 Jul 2026 13:42:17 +0000
Andy Smith <[email protected]> wrote:
>
> There 100% is a problem with your router. It is most likely sending
> IPv6 autoconfig packets that cause your hosts to autoconfigure an IPv6
> address by SLAAC. If it's not doing that then it is doing DHCPv6, but
> I think SLAAC is more likely.
Yes, you are right, I tracked it down and it was set to 'stateless',
even though the broadband status showed 'IPv6 network' as 'disabled',
without any means of enabling it.
I've turned it off, rebooted the router although it didn't ask for it,
and rebooted my workstation.
>
> There is no other way for your hosts to have global scope IPv6
> addresses unless you statically configured them, which you say you
> did not. We could tell more if you would simply show us the full
> output of "ip addr show", which you have also been asked for several
> times now.
>
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
group default qlen 1000 link/loopback 00:00:00:00:00:00 brd
00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host noprefixroute
valid_lft forever preferred_lft forever
2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel
state UP group default qlen 1000 link/ether 74:46:a0:b2:40:1f brd
ff:ff:ff:ff:ff:ff altname enp0s25
altname enx7446a0b2401f
inet 192.168.71.106/24 brd 192.168.71.255 scope global dynamic
noprefixroute eno1 valid_lft 86338sec preferred_lft 86338sec
inet6 fdda:67d:d74e:4ed1:3ee3:5e26:8a2b:7db4/64 scope global
dynamic noprefixroute valid_lft 1752sec preferred_lft 1752sec
inet6 fe80::edc9:2f64:d118:e10f/64 scope link noprefixroute
valid_lft forever preferred_lft forever
IPv6 addresses still there. It is certainly Debian putting them there,
not me.
--
Joe
