Bugzilla – Bug 159524
NetworkManager conflicts with YaST2 name server settings
Last modified: 2006-03-22 09:59:18 UTC
When selecting NetworkManager as configuration tool in YaST2 I am getting to a page where I can specify hostname and name server. There I specify: DHCP should NOT set my nameserver, I specify my own name server. DHCP sets the IP address. After finishing YaST2, NetworkManager comes up and owerwrites /etc/resolv.conf with a another name server address. So outside connections become impossible. I have good technical reasons not use another IP for the name server than for the DHCP server. So NetworkManager should obey that I do not want to have /etc/resolv.conf changed. Workaround: Disable NetworkManager and use traditional style of setup. Suggestion: YaST2 should never allow unselecting DHCP for the nameserver when NetworkManager is enabled until NetworkManager behaves as being told.
I don't have that check-box currently in fornt of me, but doesn't it talk about allowness to change the hostname, and not about nameserver? Btw. nice collection of cc:'s. Reduced it.
The check-box (retranslated from German) says: update name server and search list via DHCP There is another check-box above saying: change hostname via DHCP
Problem for me that might be related: At work we have a wireless network without a NIS. When connecting to the wireless we (should) get an IP nr via DHCP and then we connect to the companies network via VPN. This works when I use the traditional network setup in Yast, but when using network manager instead, I get an invalid ip address (169.254.102.133). In /var/log/messages I see "DHCPOFFER from 192.168.100.254: no domain-name-servers option." Mar 21 13:36:58 alfafa dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 3 Mar 21 13:36:58 alfafa dhclient: DHCPOFFER from 192.168.100.254: no domain-name-servers option. Mar 21 13:37:01 alfafa dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 5 Mar 21 13:37:01 alfafa dhclient: DHCPOFFER from 192.168.100.254: no domain-name-servers option. Mar 21 13:37:02 alfafa kernel: eth1: no IPv6 routers present Mar 21 13:37:06 alfafa dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 11 Mar 21 13:37:06 alfafa dhclient: DHCPOFFER from 192.168.100.254: no domain-name-servers option. Mar 21 13:37:17 alfafa dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 14 Mar 21 13:37:17 alfafa dhclient: DHCPOFFER from 192.168.100.254: no domain-name-servers option. Mar 21 13:37:22 alfafa dhclient: caught deadly SIGTERM Mar 21 13:37:22 alfafa dhclient: could not restore resolv.conf: No such file or directory Mar 21 13:37:22 alfafa dhclient: DHCPRELEASE on eth1 to 192.168.10.1 port 67 Mar 21 13:37:22 alfafa dhclient: send_packet: Network is unreachable Mar 21 13:37:22 alfafa dhclient: send_packet: please consult README file regarding broadcast address.
I suspect this is a problem with NetworkManager rather than with YaST2, however, Frank-Michael: Attach the /etc/sysconfig/network directory as created by yast and /var/log/NetworkManager here.
No, NM will not support this option for Code10. So YaST should not expose the configuration when NM is enabled. This is probably related to bug #156830.
I really do not appreciate mentioning bugs here, e.g. bug #156830, I am not entitled to look at. Either you open it up to me as a reporter, when mentioning it, or you copy and paste the corresponding text here. Or you do not even mention this bug. A little bit of etiquette is needed, when dealing with beta testers who invest their private time and money to improve your product. As long as I am "kept in the dark" as it already did happen with bug 148210, which was declared fixed without submitting a fix, you might as well just delete the bug.
As requested.
Mentioning bugs is o.k. I do not understand your reaction. I think Robert is right with bug 156830.
To comment 3: Winfried, I think that's a different bug, but I am not sure. Can you please put this in a new bug? I think there's somewhere a 'copy to new bug'-button in bugzilla to do this in an easy fashion, but I do not find it at the moment.
Done, new bug is: 159812
Thanks.