After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 511581 - Retry connecting to DHCP server in future if unable to get IP address
Retry connecting to DHCP server in future if unable to get IP address
Status: RESOLVED FIXED
Product: NetworkManager
Classification: Platform
Component: general
unspecified
Other Linux
: Normal enhancement
: ---
Assigned To: Dan Williams
Dan Williams
: 575482 595361 602734 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2008-01-23 17:19 UTC by Philip Culver
Modified: 2011-07-19 19:13 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Philip Culver 2008-01-23 17:19:55 UTC 
When unable to get an IP address from the DHCP server, keep contacting the DHCP server at some interval to try and acquire an IP in the future instead of giving up.



Note: Filed RFE per Dan Williams recommendation on networkmanager mailing list.
Comment 1 Dan Williams 2009-04-08 21:54:56 UTC 
*** Bug 575482 has been marked as a duplicate of this bug. ***
Comment 2 Dan Williams 2009-04-08 21:58:16 UTC 
We might want to broadent this [enh] to include static IP connections as well.  

Two behaviors here:

1) Should clear wired connections from the invalid list if the carrier drops

2) if the carrier hasn't dropped, should periodically retry DHCP connections with a suitable backoff interval
Comment 3 Dan Williams 2009-09-18 17:07:24 UTC 
*** Bug 595066 has been marked as a duplicate of this bug. ***
Comment 4 Dan Williams 2009-09-18 17:09:16 UTC 
*** Bug 595361 has been marked as a duplicate of this bug. ***
Comment 5 Dan Williams 2010-02-01 22:59:14 UTC 
*** Bug 602734 has been marked as a duplicate of this bug. ***
Comment 6 Brian J. Murrell 2010-02-01 23:51:16 UTC 
Yes, an important detail here is not to just ignore carrier/link status and just implement a backoff-and-retry, but to also work intelligently with somebody plugging in the ethernet cable, if the hardware and driver support it.

When I plug in a cable, I should (more or less) immediately get an address, not have to sit waiting for the backoff/timeout to expire.
Comment 7 AmenophisIII 2010-06-20 20:17:23 UTC 
a similar approach is needed for 3g+ connections, where the problem is somewhat deeper. often the modems/sticks can't find the carrier fast enough and modemmanager gives up and nm marks the connection as invalid. after some (upto 15 or so in my case) retries nm finally connects.

i have something like a "keep trying" checkbox as logical child of the "connect automatically" checkbox in mind. under the hood nm should keep trying to connect as long as a matching device is present (with backing off as described above).
(if someone has an idea for a workaround, id be happy to try it :)
Comment 8 Sandro Bonazzola 2011-07-14 12:27:30 UTC 
Is someone working on this?
Comment 9 Dan Williams 2011-07-19 19:13:51 UTC 
jklimes did a patch to clear the invalid marker on failed connections after a few minutes, which should handle the wired DHCP failure case.  Commit fdfbe00aac3f17b19bb8d84cba1c8f210d90e8a0 from Jun 17th.