dhclient fails to be run during boot of Intrepid
Bug #308647 reported by
Russel Winder
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
dhcp3 (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Since upgrading from Hardy to Intrepid, the network on my workstation fails to come up during boot.
The boot completes but with no network and the machine thinking it is localhost.
Logging in and running dhclient manually gets the network working and running hostname gives the machine the right name.
This is new behaviour brought in by the upgrade to Intrepid
Changed in dhcp3 (Ubuntu): | |
status: | New → Incomplete |
To post a comment you must log in.
Well, suppose I forget the hostname part (Alt-FN shows localhost. localdomain, even if a meaninfull value is in /etc/hostname, and seems to stay that after dhclient).
Was having same problem after upgrading to Intrepid from Hardy. intefaces:
I uncommented (removed the #) the following line from /etc/network/
iface eth0 inet dhcp
Then I renamed /etc/rc2. d/S28NetworkMan ager to /etc/rc2. d/K72NetworkMan ager to disable the NetworkManager.
After that, Internet works fine again.
I suppose the line was commented out of /etc/network/ interfaces because NetworkManager should call dhcpclient itself when it is not configured but it does not?
Anyway, the bug seems to be with NetworkManager not dhcp3 client.
Russel, can you confirm that this workaround works for you?