The ignored DHCPACK packets look very much like a defect I have been looking at recently.
I have seen multiple DHCPREQUEST packets coming from dhclient 3.1.1-3, (and other versions). They keep repeating from the RENEW timeout until the REBIND timeout. I tracked down the cause in one system running dhclient 3.1.1-3. The problem occured when DHCPACK packets are consumed by a second dhclient process that is supposed to be handling a different NIC. All of the dhclient processes are reading from sockets that are bound to UDP port 68 and address 0.0.0.0. The sockets have no association with a particular NIC or IP. There is a race to determine which process will read each DHCPACK packet. And it is very common for one of the other dhclient processes to read and discard every DHCPACK intended for a particular dhclient handling a particular NIC. This problem could be avoided by having a single dhclient handling all of the NICs. But the trend has been toward having one dhclient per NIC for flexible handling of NICs that are enabled after dhclient is started. If there will be multiple dhclient processes then they will need to start sharing the data that they read from their port 68 sockets. -- Mike Stroyan, [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
