My ISP gives red0 a 1200s lease, which is not renewed and thus expires. After that happens, logging in as root and executing “/sbin/dhcpcd -d red0” produces
#/sbin/dhcpcd -d red0
dhcpcd-10.0.4 starting
chrooting as dhcpcd to /run/dhcpcd/chroot
sandbox: seccomp
spawned manager process on PID 8723
spawned privileged proxy on PID 8724
spawned controller proxy on PID 8725
DUID 00:01:00:01:2c:ef:c8:22:02:45:53:7e:d1:6e
red0: executing: /var/ipfire/dhcpc/dhcpcd-run-hooks PREINIT
red0: executing: /var/ipfire/dhcpc/dhcpcd-run-hooks CARRIER
red0: IAID ff:00:00:02
red0: delaying IPv4 for 1.4 seconds
red0: reading lease: /var/ipfire/dhcpc/red0.lease
red0: discarding expired lease
red0: soliciting a DHCP lease
red0: sending DISCOVER (xid 0xf3122286), next in 4.5 seconds
red0: spawned BPF BOOTP on PID 8762
red0: sending DISCOVER (xid 0xf3122286), next in 8.3 seconds
red0: process BPF BOOTP already started on pid 8762
red0: sending DISCOVER (xid 0xf3122286), next in 15.1 seconds
red0: process BPF BOOTP already started on pid 8762
red0: offered www.xxx.yyy.zzz from www.xxx.yyy.1
red0: sending REQUEST (xid 0xf3122286), next in 3.5 seconds
red0: process BPF BOOTP already started on pid 8762
red0: acknowledged www.xxx.yyy.zzz from www.xxx.yyy.1
red0: probing address www.xxx.yyy.zzz/24
red0: spawned BPF ARP www.xxx.yyy.zzz on PID 8770
red0: probing for www.xxx.yyy.zzz
red0: ARP probing www.xxx.yyy.zzz (1 of 3), next in 1.7 seconds
red0: ARP probing www.xxx.yyy.zzz (2 of 3), next in 1.6 seconds
red0: ARP probing www.xxx.yyy.zzz (3 of 3), next in 2.0 seconds
red0: DAD completed for www.xxx.yyy.zzz
red0: leased www.xxx.yyy.zzz for 1200 seconds
red0: renew in 600 seconds, rebind in 1050 seconds
red0: writing lease: /var/ipfire/dhcpc/red0.lease
red0: adding IP address www.xxx.yyy.zzz/24 broadcast www.xxx.yyy.255
red0: adding route to www.xxx.yyy.0/24
red0: adding default route via www.xxx.yyy.1
red0: ARP announcing www.xxx.yyy.zzz (1 of 2), next in 2.0 seconds
red0: executing: /var/ipfire/dhcpc/dhcpcd-run-hooks BOUND
conntrack v1.4.7 (conntrack-tools): 0 flow entries have been deleted.
conntrack v1.4.7 (conntrack-tools): 0 flow entries have been deleted.
conntrack v1.4.7 (conntrack-tools): 0 flow entries have been deleted.
conntrack v1.4.7 (conntrack-tools): 0 flow entries have been deleted.
Adding [ OK ]outes…
Reloadi[ OK **]**all
forked to background, child pid 8723
dhcpcd_fork_cb: truncated read 0 (expected 4)
Just after the lease is acquired “ps -ef | grep dhcpcd” doesn’t show any processes running.
On the other hand, when a lease is active on red0 with 181, “ps -ef | grep dhcpcd” shows
dhcpcd 2565 1 0 16:52 ? 00:00:00 dhcpcd: red0 [ip4]
root 2566 2565 0 16:52 ? 00:00:00 dhcpcd: [privileged proxy] red0 [ip4]
dhcpcd 2567 2565 0 16:52 ? 00:00:00 dhcpcd: [control proxy] red0 [ip4]
dhcpcd 2604 2566 0 16:52 ? 00:00:00 dhcpcd: [BPF ARP] red0 www.xxx.yyy.zzz
dhcpcd 3427 2566 0 16:53 ? 00:00:00 dhcpcd: [BOOTP proxy] www.xxx.yyy.zzz
I suppose one or more of those are responsible for renewing the lease and they are missing for 182.
I guess I’ll do some more digging to try to figure out what dhcpcd_fork_cb is supposed to do.
FWIW, /var/log/messages has no additional information and /var/log/dhcpcd.log is completely empty.