Description of problem: while in fedora 7 it was working with fedora 8 and networkmanager /etc/dhclient-wlan0.conf: supersede domain-name "example.com"; supersede domain-name-servers 192.168.0.2, 192.168.0.1; no longer works. Version-Release number of selected component (if applicable): How reproducible: just connect to a wireless ap. Steps to Reproduce: 1. 2. 3. Actual results: just the dhcp server provided parameters are set. Expected results: modify the dhcp server provided data with the according to /etc/dhclient-wlan0.conf Additional info:
(Changed component...dhcdbd is not part of F-8.)
Are you sure your wireless interface is called wlan0 in Fedora 8?
I'm seeing something similar here, seems to be a network manager bug, dhclient-iface.conf is used for non-network manager enabled interfaces and ignored for network-manager enabled ones. below is the arguments used to start dhclient from network manager, /sbin/dhclient -d -sf /usr/libexec/nm-dhcp-client.action -pf /var/run/dhclient-wlan0.pid -lf /var/run/dhclient-wlan0.lease wlan0 so it seems network manager needs to be taught about the -cf flags
yes i'm sure i've wlan0 and it works as i do manual ifup wlan0 and it use /etc/dhclient-wlan0.conf in that case, but if i start networkmanager than it no longer use /etc/dhclient-wlan0.conf which is imho a bug! since currently there is no any other way (or at least i don't know) how to force some kind of options like: supersede domain-name "example.com"; supersede domain-name-servers 192.168.0.2, 192.168.0.1;
I have found something similar in NetworkManager-0.7.0-0.9.1.svn3549.fc9 My /etc/dhclient.conf contains: prepend domain-name-servers 127.0.0.1; This was respected under the F8 version of NetworkManager, but is now ignored since I upgraded. However, if I copy the same file as /etc/dhclient-wlan0.conf then it *does* work. It correctly prepends the nameserver 127.0.0.1 to /etc/resolv.conf on connection.
please close this bug since it's been already solved
Closing per comment #6