dhcpcd-discuss

> I don't see anything wrong with either config.
> I'm going to guess that dhcpcd expired the lease?
> If you look at the logs (for debugging purposes it's good to add debug
> to dhcpcd.conf) you should see dhcpcd attempting to renew and then
> rebind it's existing lease before it fails.
> 
> If you see this then I would run tcpdump on the host to ensure packets
> are going out and maybe a reply coming in dhcpcd misses and tcpdump on
> the server to ensure packets are coming in and going out.
> 
> I see that your host has many subnets which implies many interfaces.
> Could it be that the host has many interfaces too and is receiving the
> DHCP reply on the wrong interface? dhcpcd-7 has code to handle that, but
> no prior versions do. What version are you running?
> 
> Roy
> 

The (non-debug) log just said "Deleting IP" and "Deleting Route".
I will enable debugging (and massively reduce the lease-time to a few
minutes) and see what it prints.

The dhcp host has only two interfaces, but the external interface is
getting a bunch of other networks relayed to it.
The internal interface is a bridge with the two nodes on it, which both
just have a single interface and network.

The clients are running dhcpcd 7.0.1.

The dhcp server had no log entries when the dhcpcd clients deleted their
IPs.

With the massively reduced lease-time, everything seems to look good for
now:
https://paste.pound-python.org/show/Fi2uL0sJhTqJluszzovt/

systemd-networkds DHCP client is now also happy with the interface and
no longer stuck configuring it forever. Maybe the times I had set
previously were somehow invalid?

Times are now set to:
default-lease-time 120;
max-lease-time 300;

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature