Additional note for this bug: this has been "fixed" upstream by adding a --dad-wait-time parameter to dhclient. However, that param defaults to 0, and also requires an update to the dhclient-script.linux that isc-dhcp provides. Debian has its own modified dhclient-script.linux, slightly different than upstream, which is what we modified to fix this bug.
I don't personally recommend using the upstream isc-dhcp "fix" for this; our change to the dhclient-script.linux maintained by debian/ubuntu is a better fix, at least for the SRU releases; and our change doesn't require tooling that uses dhclient to add a new --dad-wait-time parameter.
Additional note for this bug: this has been "fixed" upstream by adding a --dad-wait-time parameter to dhclient. However, that param defaults to 0, and also requires an update to the dhclient- script. linux that isc-dhcp provides. Debian has its own modified dhclient- script. linux, slightly different than upstream, which is what we modified to fix this bug.
The upstream bug is: /bugs.isc. org/Public/ Bug/Display. html?id= 36169
https:/
I don't personally recommend using the upstream isc-dhcp "fix" for this; our change to the dhclient- script. linux maintained by debian/ubuntu is a better fix, at least for the SRU releases; and our change doesn't require tooling that uses dhclient to add a new --dad-wait-time parameter.