On 6/28/25 4:45 AM, Ralph Corderoy wrote:
Hi David,
the update tonight (an hour ago), failed to start dhcpd4. I can't
ping the box, I have to log in locally and I find the network
interface enp5s0 'down' - that's not happened since Arch was
installed.
Did it reboot because of that update?
If so, could the damage have been caused by some other change made since
the previous boot which only took effect on booting?
Thanks Ralf,
No, this was just a normal pacman -Syu and then a manual reboot
because of the kernel update. Nothing strange. I watch the rss feed for
kernel updates in core and always update for each new kernel and then
manually reboot.
There is something that definitely changed in how the network
interface is being handled. It is brought up fine, but then is taken down???
See last post for details and config files, but the crux of it from
the journal is:
# journalctl -b --no-pager --full | grep enp5 | head -n50
Jun 28 02:17:05 valkyrie systemd[1]: Expecting device
/sys/subsystem/net/devices/enp5s0...
Jun 28 02:17:08 valkyrie kernel: r8169 0000:05:00.0 enp5s0: renamed from
eth0
Jun 28 02:17:12 valkyrie kernel: r8169 0000:05:00.0 enp5s0: Link is Down
Jun 28 02:17:15 valkyrie kernel: r8169 0000:05:00.0 enp5s0: Link is Up -
1Gbps/Full - flow control rx/tx
************************************************************************
Jun 28 02:17:15 valkyrie avahi-daemon[711]: Joining mDNS multicast group
on interface enp5s0.IPv4 with address 192.168.6.14.
Jun 28 02:17:15 valkyrie avahi-daemon[711]: New relevant interface
enp5s0.IPv4 for mDNS.
Jun 28 02:17:15 valkyrie avahi-daemon[711]: Registering new address
record for 192.168.6.14 on enp5s0.IPv4.
Jun 28 02:17:15 valkyrie kernel: r8169 0000:05:00.0 enp5s0: Link is Down
************************************************************************
Jun 28 02:17:15 valkyrie avahi-daemon[711]: Interface enp5s0.IPv4 no
longer relevant for mDNS.
Jun 28 02:17:15 valkyrie avahi-daemon[711]: Leaving mDNS multicast group
on interface enp5s0.IPv4 with address 192.168.6.14.
Jun 28 02:17:15 valkyrie avahi-daemon[711]: Withdrawing address record
for 192.168.6.14 on enp5s0.
Jun 28 02:17:18 valkyrie named[801]: listening on IPv4 interface enp5s0,
192.168.6.14#53
Jun 28 02:40:10 valkyrie avahi-daemon[711]: Joining mDNS multicast group
on interface enp5s0.IPv4 with address 192.168.6.14.
Jun 28 02:40:10 valkyrie avahi-daemon[711]: New relevant interface
enp5s0.IPv4 for mDNS.
Jun 28 02:40:10 valkyrie avahi-daemon[711]: Registering new address
record for 192.168.6.14 on enp5s0.IPv4.
Jun 28 02:40:10 valkyrie kernel: r8169 0000:05:00.0 enp5s0: Link is Down
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?
--
David C. Rankin, J.D.,P.E.
