Your DHCPREQUEST troubles seem like the signs of an "old temporary solution"; the kind which tend to stick around. For example, if the DHCP server is owned by either a network incumbent or wholesale ISP who offers wholesale or white-label support, unicast renewals could create problems if one of multiple DHCP servers (not running in a proper parallel config) captured a host-client relationship and continued to renew during an attempted customer migration to another ISPs on the same network. Another possibility is they are inspecting and dropping unicast DHCP to prevent a peer (or client) network from accidentally (or intentionally) trying to use the wholesale network as a backchannel for their own unicast. I know it sounds far-fetched, but I've seen far more "creative" solutions. To unsubscribe send a blank message to linux+unsubscribe [ at ] linux-ottawa [ dot ] org To get help send a blank message to linux+help [ at ] linux-ottawa [ dot ] org To visit the archives: https://lists.linux-ottawa.org