dhclient fails to be run during boot of Intrepid

[Russel Winder]

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.localdomain.

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

[Paul Dufresne (paulduf)]

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.
I uncommented (removed the #) the following line from /etc/network/intefaces:
iface eth0 inet dhcp

Then I renamed /etc/rc2.d/S28NetworkManager to /etc/rc2.d/K72NetworkManager 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?

[Chuck Short (zulcss)]

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks!

[Russel Winder (russel)]

I am now using Jaunty, so can't comment on anything Intrepid any more. Sorry.

Network Manager has been a real pain generally disrupting all DHCP, NIS, DNS, etc. Having changed Network Managers' start number to something big most of the problems go away, which is why I haven't been hassling -- solving the NIS issues seems to solve this one. Actually as Paul says removing Network Manager seems to be the best solution on all machines other than laptops. Given that static machines are, well, static the whole idea of dynamically managing a network seems fairly redundant. I would like a way of having laptops with Network Manager and workstations without it as the default.

cf. 50430, 224828, 303072, etc., etc.

Sorry to be less than constructive.

[Chuck Short (zulcss)]

Closing user cant reproduce the error.

Regards
chuck