A status update for those playing along at home...
So far this bug seems to be a general failure of DHCP to obtain an IP address
during boot; the reason for this is unknown. There doesn't seem to be any
common hardware at fault here and I do not believe it to be a udev/hotplug
problem as the device is plugged and dhclient run.
I can't see any noteworthy changes between 3.0.1 and 3.0.2 or 3.0.2 and 3.0.3
that could fix this; if there's anyone still having problems, could they try:
A status update for those playing along at home...
So far this bug seems to be a general failure of DHCP to obtain an IP address
during boot; the reason for this is unknown. There doesn't seem to be any
common hardware at fault here and I do not believe it to be a udev/hotplug
problem as the device is plugged and dhclient run.
I can't see any noteworthy changes between 3.0.1 and 3.0.2 or 3.0.2 and 3.0.3
that could fix this; if there's anyone still having problems, could they try:
1) downgrading to dhcp3-client_ 3.0.1-1ubuntu4 from archive. ubuntu. com/ubuntu/ pool/main/ d/dhcp3 3.0.3-3 from ftp.debian. org/debian/ pool/main/ d/dhcp3
http://
2) upgrading to dhcp3-client_
http://
And find out whether one, or both, of these fixes the problem. Make sure to
test a few reboots with each one to make sure it's not a fluke.