DHCP recognizes LAN only minutes after plugging cable
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| dhcp3 (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Bug Description
Hi,
[This is about Dapper - Launchpad confuses me so much]
The logfiles below show that it took 4 minutes to DHCP to eventually enable my network connection after the kernel immediately recognized my plugging in the cable.
Sep 8 10:00:37 localhost kernel: [4294911.988000] eth0: link up, 100Mbps, full-duplex, lpa 0xC3E1
Sep 8 10:04:18 localhost dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6
Sep 8 10:04:24 localhost dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
Sep 8 10:04:24 localhost dhclient: DHCPOFFER from 10.*.*.*
Sep 8 10:04:24 localhost dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
Sep 8 10:04:31 localhost dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
Sep 8 10:04:31 localhost dhclient: DHCPACK from 10.*.*.*
Sep 8 10:04:32 localhost dhclient: bound to 10.*.*.* -- renewal in 19461 seconds.
What I'd expect from a machine is to immediately recognize the new connection (kernel detects it on 10:00:37) and perform appropriate actions, e.g. start DHCP or whatever. Is anything wrong with this expectation (e.g. skip over intermittent failures)?
The observed behaviour is very user unfriendly, and so far I have found no way to speed it up (e.g. the manpage does not document anything like kill -USR1/HUP to have the dhcpclient daemon start a new cycle right now).
Ideally, the system would start different actions depending on what it snoops from the network (e.g. does traffic indicate a 192.168.*, or
DSL, or 10.* network?).
Currently, dhcp wakes up every 7 minutes, so the delay could even be longer. However, reducing this pause does not seem like a good answer. It looks like its integration into the system needs be reconsidered.
It seems to me like DHCP should not sit idle on the eth0 (and superfluously my WLAN eth1 which I have switched off) and better integrate into ifup/ifdown. (In Breezy, Hoary etc. DHCP was not even started for eth1, but that's another story.)
Is there anything I should configure differently in Dapper to have DHCP behave nicely and promptly?
Regards,
Jörg Höhle
| Bryan Quigley (bryanquigley) wrote | #1 |
| Bryan Quigley (bryanquigley) wrote | #2 |
| Changed in dhcp3: | |
| status: | New → Fix Released |
| Jörg Höhle (joerg-cyril-hoehle) wrote | #3 |
| Bryan Quigley (bryanquigley) wrote | #4 |
| Changed in dhcp3: | |
| status: | Fix Released → Incomplete |
| wolfger (wolfger) wrote | #5 |
| Changed in dhcp3: | |
| status: | Incomplete → Invalid |
| Jörg Höhle (joerg-cyril-hoehle) wrote | #6 |
Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with latest Ubuntu release? Thanks in advance.