NetworkManager does not retry DHCP after DHCP timed out once
Bug #387035 reported by
David Tomaschik
This bug report is a duplicate of:
Bug #672562: NetworkManager does not re-enable connection which was disabled because DHCP timed out.
Edit
Remove
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
NetworkManager |
Fix Released
|
Wishlist
|
|||
network-manager (Debian) |
Confirmed
|
Unknown
|
|||
network-manager (Ubuntu) |
Confirmed
|
Wishlist
|
Unassigned |
Bug Description
Binary package hint: network-manager
Source package hint: network-manager
I have a computer with Jaunty on it connected directly to a Linksys home network router running OpenWRT. If the router is rebooted, network-manager times out trying to get a new DHCP address before the DHCP server is back up. This results in network-manager leaving the interface down and the system unreachable. It would be nice if network-manager would retry the connection after, perhaps, 1 minute, then 2 minutes, then 5, and finally 10 before giving up.
Changed in network-manager: | |
status: | Unknown → Confirmed |
Changed in network-manager: | |
importance: | Unknown → Wishlist |
Changed in network-manager (Debian): | |
importance: | Undecided → Unknown |
status: | New → Unknown |
Changed in network-manager (Debian): | |
status: | Unknown → Confirmed |
Changed in network-manager: | |
status: | Confirmed → Fix Released |
summary: |
- Network Manager should retry DHCP + NetworkManager does not retry DHCP after DHCP timed out once |
To post a comment you must log in.
upstream bug: http:// bugzilla. gnome.org/ show_bug. cgi?id= 511581 ... please follow discussion there.