Description of problem: After update to version 0.3.3-1.cvs20050112.1.fc3 of NetworkManager I cannot resolve any hostname. After start of network manager it replaces /etc/resolv.conf with its own version which points to to local named daemon. Problem is that named cannot find forwarders. I have attached output from /var/log/messages. Previous version worked ok. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1.start NetworkManager 2.nslookup hostname 3.stop NetworkManager Actual results: host <hostname> ; connection timed out; no servers could be reached Expected results: host <hostname> hostname is <ip> Additional info: Moreover, after stopping of NetworkManager it does not restore last version of resolv.conf file.
Created attachment 109960 [details] output of /var/log/messages This is output form /var/log/messages while starting and stoppping NetworkManager
Created attachment 109961 [details] content of /etc/resolv.conf this is /etc/resolv.conf file after stopping of NetworkManager
I have the same problem here....
After upgrade to NetworkManager-0.3.3-1.cvs20050119.2.fc3 the situation is partialy resolved: only fully qualified hostnames can be resolved. This is because now NetworkManager removes "search" option from /etc/resolv.conf. When network services are started without starting NetworkManager file /etc/resolv.conf contains "nameserver" option as well as "search" option. After start of network manager "search option" is being removed.
After further investigation it occured that my previous post does not describe the problem correctly:-(. After reboot of the system, during network services start, ip address is acquired through dhcp client. Also suitable /etc/resolv.conf file is generated: ; generated by /sbin/dhclient-script search orzeszkowej.gdynia.mpsz.pl nameserver 10.47.0.1 Then when I start NetworkManager, file /etc/resolv.conf is changed to: ; generated by NetworkManager, do not edit! (yes, it has only one line!!!) Stopping NetworkManager does not correct the problem, restart of network services is needed.
Can you post the debug output in /var/log/messages where the DHCP server replies with the DHCP data? Thanks, Dan
Created attachment 110329 [details] attachement with contents of /var/log/messages and /etc/resolv.conf
Hi Dan, I have created an attachement with six sections: 1. contents of /var/log/messages after command "service network start" has been issued 2. contents of /etc/resolv.conf after command "service network start" has been issued 3. contents of /var/log/messages after command "service NetworkManager start" has been issued 4. contents of /etc/resolv.conf after command "service NetworkManager start" has been issued 5. contents of /var/log/messages after ethernet cable was unplugged and plugged again 6. contents of /etc/resolv.conf after ethernet cable was unplugged and plugged again Some messages are in Polish and if it is a problem please let me know and I will change system locales. I hope it helps Pawel
This bug has been fixed in CVS (the one with wired networks), I'm not sure if it made it to the latest FC3 update though. I'll be pushing another FC3 update soon however.
Hi Dan, I've prepared package which is based on the 20050202 NetworkManager version and it seems to work ok now. Regards Pawel PS. There were some problems running autoconf.sh --prefix=/usr --sysconfdir=/etc: - it required gnome-common package for running /usr/bin/gnome-autogen.sh - it required libtoolize before running ./autogen.sh otherwise it finished with an error "config.status: error: cannot find input file: Makefile.in "
closing since its fixed...
where is it fixed? It still happens on an updated FC3 box: NetworkManager-0.3.4-1.1.0.fc3