Bug #45457 for dhcp-public: Zero delay between DHCPDECLINE a DHCPDISCOVER

The client in ISC DHCP 4.3.5 (and probably in older versions) does not wait between sending DHCPDECLINE (bind_lease() in client/dhclient.c) and sending DHCPDISCOVER (state_init() in client/dhclient.c). If the call of script_go() in bind_lease() keeps failing (e.g. when somethings breaks in dhclient-script), the client will spin in a DHCPDISCOVER-DHCPDISCOVER-DHCPDECLINE loop as quickly (and as long) as the server can respond. RFC 2131 says clients should wait at least 10 seconds between DHCPDECLINE and DHCPDISCOVER. See page 16: [...] If the client detects that the address is already in use (e.g., through the use of ARP), the client MUST send a DHCPDECLINE message to the server and restarts the configuration process. The client SHOULD wait a minimum of ten seconds before restarting the configuration process to avoid excessive network traffic in case of looping. -- Pavel Kankovsky aka Peak "Que sçay-je?"

Hello Pavel: Thank you for your submission. We are very close to the end of our release cycle for releases 4.3.6 and 4.1-ESV-R15 due our 7/31/17, so this issue is unlikely to be addressed before then. We will certainly consider it for our next feature release, 4.4.0. It's release date is TBD but is likely to be Q4/17 or Q1/18. You should get notifications as things progress. Again, thank you for your continued interest and support. Sincerely, Thomas Markwalder ISC Software Engineering

On Mon, 27 Nov 2017, Thomas Markwalder via RT wrote: > You'll be pleased to know that we have addressed your issue in dhclient > in our upcoming feature release, 4.4.0, [...] Thank you. > We like to acknowledge our contributors by thanking them in our release > notes. If you wish to recognized in this manner please respond with how > you wish to be identified. To be honest, I do not care. > Thank you for taking the time to report the issue to us. You are welcome. -- Pavel Kankovsky aka Peak "Que sçay-je?"