network-manager ignoring dhclient.conf

[tyler]

When using a modified dhclient.conf (attached), where the hostname is sent and ntp servers are accepted from the server, network-manager ignores these settings.

 -> I've attached the wireshark dump of the dhcp procedure when using network-manager and one using dhlcient from the commandline.

 -> They both have different options set.

 -> It is impossible to let network manager honor the settings provided for dhclient by dhclient.conf (at least as far as I was able to find out)

[Jonathan Hudson (jh+lpd)]

Very annoying, as it breaks integrated DHCP/DNS (e.g. dnsmasq) and means a laptop that alternates wired / wireless ends up with different addresses.

I note that NM runs dhclient with -cf pointing to an empty file.

[Jonathan Hudson (jh+lpd)]

As mentioned in some earlier report, it appears than NM ignores /etc/dhcp3/dhclient.conf and instead looks for /etc/dhclient-$IFNAME.conf (e.g. /etc/dhclient-eth0.conf). If this exists (e.g. as a symlink to /etc/dhcp3/dhclient.conf) then NM uses that as the -cf parameter.

* It would be nice if NM used the system wide file we all know and love (even via a 'use system DHCP settings' checkbox;

* It would be nice if these "so simple they need no documentation" did in fact have some obvious documentation, in order to solve the more difficult cases with days of googling.

[Alexander Sack (asac)]

this is a known issue and i posted a patch attempt to bug 210095 ... please test that.

[tyler (durdon-tyler)]

Creating symlinks for my network devices worked for network manager.

Now the correct options are used for dhclient, but I found another time server related error, which I reported here https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/267891

[Alexander Sack (asac)]

i submitted a fix for this upstream, which landed and is now fixed in 0.7~~svn20080908t183521+eni0-0ubuntu1 package