On 6/28/25 10:48 AM, David C Rankin wrote:
Jun 28 02:40:13 valkyrie kernel: r8169 0000:05:00.0 enp5s0: Link is Up -
1Gbps/Full - flow control rx/tx
Jun 28 02:40:14 valkyrie avahi-daemon[711]: Joining mDNS multicast group
on interface enp5s0.IPv6 with address fe80::feaa:14ff:fe9e:3319.
Jun 28 02:40:14 valkyrie avahi-daemon[711]: New relevant interface
enp5s0.IPv6 for mDNS.
Jun 28 02:40:14 valkyrie avahi-daemon[711]: Registering new address
record for fe80::feaa:14ff:fe9e:3319 on enp5s0.*.
Jun 28 02:41:43 valkyrie dhcpd[1781]: Listening on LPF/enp5s0/
fc:aa:14:9e:33:19/192.168.6.0/24
Jun 28 02:41:43 valkyrie dhcpd[1781]: Sending on LPF/enp5s0/
fc:aa:14:9e:33:19/192.168.6.0/24
Huh??? Where did the IPv4 interface go? And why?
For sake of completeness, my network is IPv4. There are a couple of
devices (Amazon firesticks, etc..) that can talk IPv6, but my ISP and my
local LAN are all IPv4.
There has definitely been a change in how (whatever) looks at IPv4 and
IPv6 and chooses the interface to use. Here is the same journal entries
from the last boot of kernel 6.15.3 and IPv4 is configured and stays UP.
So whatever happened, it looks like the logic governing whether to use
IPv4 or IPv6 changed in this last update and that is what is taking my
IPv4 interface down, e.g.
# journalctl -b -3 --no-pager --full | grep enp5 | head -n50
Jun 25 03:49:36 valkyrie systemd[1]: Expecting device
/sys/subsystem/net/devices/enp5s0...
Jun 25 03:49:44 valkyrie kernel: r8169 0000:05:00.0 enp5s0: renamed from
eth0
Jun 25 03:49:48 valkyrie kernel: r8169 0000:05:00.0 enp5s0: Link is Down
Jun 25 03:49:50 valkyrie kernel: r8169 0000:05:00.0 enp5s0: Link is Up -
1Gbps/Full - flow control rx/tx
Jun 25 03:49:50 valkyrie avahi-daemon[729]: Joining mDNS multicast group
on interface enp5s0.IPv4 with address 192.168.6.14.
Jun 25 03:49:50 valkyrie avahi-daemon[729]: New relevant interface
enp5s0.IPv4 for mDNS.
Jun 25 03:49:50 valkyrie avahi-daemon[729]: Registering new address
record for 192.168.6.14 on enp5s0.IPv4.
Jun 25 03:49:52 valkyrie avahi-daemon[729]: Joining mDNS multicast group
on interface enp5s0.IPv6 with address fe80::feaa:14ff:fe9e:3319.
Jun 25 03:49:52 valkyrie avahi-daemon[729]: New relevant interface
enp5s0.IPv6 for mDNS.
Jun 25 03:49:52 valkyrie avahi-daemon[729]: Registering new address
record for fe80::feaa:14ff:fe9e:3319 on enp5s0.*.
Jun 25 03:49:53 valkyrie named[854]: listening on IPv4 interface enp5s0,
192.168.6.14#53
<snip - dhcp starts handing out leases here>
What happened with this IPv4/IPv6 network logic between June 25 and June 28?
--
David C. Rankin, J.D.,P.E.
