It turns out that both
dhclient are running at the same time and that both daemons were operating on the same file.
- dhclient updated
- systemd-networkd processed same DHCP RESPONSE packets as well and sent packets of which
dhclient received as well.
systemd-networkd set its T1 timer much earlier, so it reported 'DHCP lease lost' to
syslog(), replaced IP address with a different one, leaving dhclientd confused.
If you want ISC DHCP client (and not systemd), then turn off DHCP in systemd by editing
If you want systemd (over ISC DHCP client), then uninstall dhclient package:
apt-get remove isc-dhcp-client
== RESOLUTION ==
In my case, Verizon FiOS runs a Juniper Network DHCP server and likes to see dhclient reporting
Wireless_Broadband_Router as the host-name and domain-name as
home which is what the Actiontec Cablemodem router does anyway. They also prefers handle broadcast DHCP REBIND message, and not unicast DHCP REBIND message.
Furthermore, DHCP option isn't supported in
systemd-networkd, so ISC DHCP remains as king.
Also, posted my entire code base related to
systemd and ISC DHCP client at GitHub.