| 2006-01-30 15:56:42 |
Scott James Remnant (Canonical) |
dhcp3: status |
Unconfirmed |
Fix Released |
|
| 2006-01-30 15:56:42 |
Scott James Remnant (Canonical) |
dhcp3: statusexplanation |
Bugzilla status=NEW, product=Ubuntu, component=dhcp3-client |
DHCP of your hardware network interfaces is no longer in the critical path of the boot process, so it doesn't matter how long the timeout is. |
|
| 2006-12-22 22:05:31 |
Sebastian Breier |
dhcp3: status |
Fix Released |
Unconfirmed |
|
| 2006-12-22 22:05:31 |
Sebastian Breier |
dhcp3: assignee |
keybuk |
|
|
| 2006-12-22 22:05:31 |
Sebastian Breier |
dhcp3: statusexplanation |
DHCP of your hardware network interfaces is no longer in the critical path of the boot process, so it doesn't matter how long the timeout is. |
I'm reopening this as unconfirmed without assignee, because it's in feisty again. The default dhclient.conf has a "timeout 30" line and makes the boot process stall for a long time. I just wonder if there is a good reason for such a high timeout? |
|
| 2006-12-23 10:39:36 |
Sebastian Breier |
bug |
|
|
assigned to gnome-power-manager (Ubuntu) |
| 2006-12-23 10:41:23 |
Sebastian Breier |
title |
Default dhcp timeout should be shorter |
Network startup stalls boot |
|
| 2006-12-23 10:43:48 |
Sebastian Breier |
bug |
|
|
assigned to gnome-network (Ubuntu) |
| 2007-02-19 16:55:27 |
Martin Pitt |
gnome-network: status |
Unconfirmed |
Rejected |
|
| 2007-02-19 16:55:27 |
Martin Pitt |
gnome-network: statusexplanation |
|
Gnome packages are not related at all to the boot sequence (neither to hibernate/resume; they just trigger it, but not control it) |
|
| 2007-02-19 16:55:53 |
Martin Pitt |
gnome-power-manager: status |
Unconfirmed |
Rejected |
|
| 2007-02-19 16:55:53 |
Martin Pitt |
gnome-power-manager: statusexplanation |
|
Likewise. |
|
| 2007-02-19 16:58:07 |
Martin Pitt |
dhcp3: status |
Unconfirmed |
Fix Released |
|
| 2007-02-19 16:58:07 |
Martin Pitt |
dhcp3: statusexplanation |
I'm reopening this as unconfirmed without assignee, because it's in feisty again. The default dhclient.conf has a "timeout 30" line and makes the boot process stall for a long time. I just wonder if there is a good reason for such a high timeout? |
In Feisty, the DHCP timeout has been lowered to 30 seconds, which is a good balance between working with slow DHCP servers and not getting too annoyed.
Also, if you have a non-permanent internet connection, then you should just use network manager and use the Gnome network tool to disable the static configuration.
I consider this not a problem any more. Please shout out if I misunderstood and you still think that something needs to be changed. Thank you! |
|
