GNOME Bugzilla – Bug 797015
DHCP: NM doesn't check DHCP lease on DHCP timeout
Last modified: 2020-11-12 14:28:08 UTC
If the DHCP server is down and client reboot during the server down time, client won't be able to get a valid ip address, even though the DHCP lease is still valid. But "man dhclient-script" says: > TIMEOUT > The DHCP client has been unable to contact any DHCP servers. However, > an old lease has been identified, and its parameters have been passed in > as with BOUND. The client configuration script should test these > parameters and, if it has reason to believe they are valid, should exit > with a value of zero. If not, it should exit with a nonzero value. NetworkManager needs to better handle the timeout reason instead of just fail it directly.
Created attachment 373670 [details] [review] device: don't fail dhcp directly on timeout This is one of the patches needed for fixing bug. We should also improve the way we consider it's a dhcp timeout. Currently we simply use a timeout function(45 seconds by default) and fail it directly.
Created attachment 373680 [details] [review] dhcp: separate timeout function call with watch call
bugzilla.gnome.org is being shut down in favor of a GitLab instance. We are closing all old bug reports and feature requests in GNOME Bugzilla which have not seen updates for a long time. If you still use NetworkManager and if you still see this bug / want this feature in a recent and supported version of NetworkManager, then please feel free to report it at https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/ Thank you for creating this report and we are sorry it could not be implemented (workforce and time is unfortunately limited).