https://bugzilla.novell.com/show_bug.cgi?id=434575 User ben.kevan@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=434575#c1 --- Comment #1 from Ben Kevan 2008-10-12 08:54:35 MDT --- Here are relevant things in /var/log/messages messages:Oct 11 12:07:33 HCSUSE01007250 dhclient: could not restore resolv.conf: No such file or directory messages:Oct 11 14:52:28 HCSUSE01007250 dhclient: could not restore resolv.conf: No such file or directory messages:Oct 11 22:09:22 HCSUSE01007250 dhclient: could not restore resolv.conf: No such file or directory messages:Oct 11 22:14:03 HCSUSE01007250 dns-resolver: ATTENTION: You have modified /etc/resolv.conf. Leaving it untouched... messages:Oct 11 22:14:03 HCSUSE01007250 dns-resolver: You can find my version in /etc/resolv.conf.netconfig The first being without my changes, and obviously the second being with the changes. cat /etc/resolv.conf.netconfig ### /etc/resolv.conf file autogenerated by netconfig! # # Before you change this file manually, consider to define the # static DNS configuration using the following variables in the # /etc/sysconfig/network/config file: # NETCONFIG_DNS_STATIC_SEARCHLIST # NETCONFIG_DNS_STATIC_SERVERS # NETCONFIG_DNS_FORWARDER # or disable DNS configuration updates via netconfig by setting: # NETCONFIG_DNS_POLICY='' # # See also the netconfig(8) manual page and other documentation. # # Note: Manual change of this file disables netconfig too, but # may get lost when this file contains comments or empty lines # only, the netconfig settings are same with settings in this # file and in case of a "netconfig update -f" call. # ### Please remove (at least) this line when you modify the file! ll /etc/resolv.conf -rw-r--r-- 1 root root 98 2008-10-11 22:27 /etc/resolv.conf cat /etc/resolv.conf # generated by NetworkManager, do not edit! search hsd1.ca.comcast.net nameserver 68.87.76.178 Note, those were staticly entered. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=434575 User ben.kevan@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=434575#c3 --- Comment #3 from Ben Kevan 2008-10-13 09:04:25 MDT --- So I'm supposed to log in, with no network because I haven't defined an eth0 device? if so, that's a horrible way of handling it. for wlan I can understand, but not for onboard nic's. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=434575 User ben.kevan@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=434575#c5 Ben Kevan changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|INVALID | --- Comment #5 from Ben Kevan 2008-10-13 11:40:08 MDT --- Forgot to reopen.. But what I seem to see is that netconfig doesn't set the settings as it should. ll /etc/resolv.conf* -rw-r--r-- 1 root root 148 2008-10-13 09:56 /etc/resolv.conf -rw-r--r-- 1 root root 795 2008-10-13 07:53 /etc/resolv.conf.netconfig Attached is my /etc/sysconfig/network/config This was an upgrade from 11.0 to 11.1 Beta 2 On another machine I have all is working as it should, but not on this one. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=434575 User ben.kevan@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=434575#c7 Ben Kevan changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |INVALID --- Comment #7 from Ben Kevan 2008-10-13 14:41:59 MDT --- closing.. I'll enter another bug that shows that "yast" is not required. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=434575 User ben.kevan@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=434575#c9 --- Comment #9 from Ben Kevan 2008-10-16 10:37:23 MDT --- (In reply to comment #8 from Stephan Binner)

...

even though I get dhcp addresses, dns is not written to /etc/resolv.conf

How is this bug solved? I encounter the same on an installed Beta 3 Live-CD.

Stephan, I feel your pain. What I had to do to get it to work was actually KILL the /etc/resolv.conf and restart the network daemon. Only after this did NetworkManager write to /etc/resolv.conf (do I agree with it? Hell no). I obviously want to do more testing.. IE: change to ifup modify manually /etc/resolv.conf change back to networkmanager see what I get in /etc/resolv.conf, see if dhcp takes over and adds the correct nameservers and search suffixes. More tests also should be done with how netconfig works, and if netconfig doesn't work with what YaST has configured when NetworkManager is set then it should be a disabled field (should be easy enough). I still have not found a way to set static nameservers or search suffixes to be written to resolv.conf (as I did previously with netconfig). Using network manager to make everything static is obviously not a comparible "feature". -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=434575 User jpr@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=434575#c11 --- Comment #11 from JP Rosevear 2008-10-16 20:23:47 MDT --- See also bug 436292. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=434575 User ben.kevan@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=434575#c13 Ben Kevan changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jpr@novell.com --- Comment #13 from Ben Kevan 2008-10-16 21:29:48 MDT --- If NetworkManager uses netconfig then why doesn't it handle /etc/sysconfig/network/config ? That's what man netconfig shows to being used. That's what YaST configures and that's what SHOULD be used append static nameservers and search suffixes to the NetworkManager written /etc/resolv.conf. JP Sorry for adding you directly to this bug report CC list.. but wanted to make sure you got these latest comments. Thank you all for your help. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=434575 User ben.kevan@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=434575#c15 --- Comment #15 from Ben Kevan 2008-10-17 09:39:35 MDT --- Hi MT, Glad to hear you're taking the charge of this bug. That is the interesting part the machine it "worked on" (writing of the /etc/resolv.conf) was an upgrade from a clean 11.0 to 11.1 beta 2, WHICH included a automaticlly modified resolv.conf by NetworkManager. Also, like I noted, on my machine it worked after I deleted the resolv.conf (as you would expect). What's the likely hood that this will be fixed by Beta 4 for testing pre RC stages? Let me know what you want me to test, or any test packages.. I'm open to throwing 'em on my other box. Ben -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=434575 User ben.kevan@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=434575#c17 --- Comment #17 from Ben Kevan 2008-10-24 11:20:19 MDT --- Hi MT, I tried 0.71.9-19.2 and 0.71.9-20.1 both did not write input from /etc/sysconfig/network/config to /etc/resolv.conf I also tried killing /etc/resolv.conf and /etc/resolv.conf.netconfig Then tried running netconfig -f -v -i eth0 and still did not write the settings to /etc/resolv.conf. sudo netconfig update -f -v -i eth0 debug: lockfile created (/var/run/netconfig.pid) for PID 8874 debug: lockfile created debug: Module order: dns-resolver dns-bind dns-dnsmasq ntp-runtime nis debug: dns-resolver Plugin called debug: Use NetworkManager policy merged settings debug: exec get_dns_settings: /var/run/netconfig//NetworkManager.netconfig debug: exit get_dns_settings debug: write_resolv_conf: ' domainname.com domainname.com' ' 10.10.10.10 10.10.10.11' debug: Installing new /etc/resolv.conf debug: dns-bind Plugin called debug: dns-dnsmasq Plugin called debug: ntp-runtime Plugin called debug: Use NetworkManager policy merged settings debug: exec get_ntp_settings: /var/run/netconfig//NetworkManager.netconfig debug: exit get_ntp_settings debug: nis Plugin called debug: Use NetworkManager policy merged settings debug: exec get_nis_settings: /var/run/netconfig//NetworkManager.netconfig debug: exit get_nis_settings debug: format_yp_conf called with : debug: current domain is ; given domain is debug: domain matches ... set empty debug: Installing new /etc/yp.conf grep more.domainname.com /etc/sysconfig/network/config NETCONFIG_DNS_STATIC_SEARCHLIST="more.domainname.com" Sorry I replaced the real IP's and real dns suffixes with fake ones.. (should have done in previous posting too). You see I have NETCONFIG_DNS_STATIC_SEARCHLIST defined, within sysconfig/network/config, yet netconfig still is not merging the settings. Ben -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=434575 User mt@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=434575#c19 Marius Tomaschewski changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED --- Comment #19 from Marius Tomaschewski 2008-10-27 04:24:37 MDT --- Well, when the NetworkManager is in use and the NETCONFIG_DNS_POLICY (DNS, NIS, NTP) is set to "auto", the NetworkManager is responsible for the settings. The netconfig scripts are just using settings the NetworkManager provides. (From comment #17 by Ben Kevan)

debug: Use NetworkManager policy merged settings

See also comment #14 and comment #2 from Tambet Ingo:

NetworkManager in 11.1 does not use yast settings anymore. Use the connection editor from (k)nm to define your network settings.

Now you have the choice to: - change the NETCONFIG_DNS_POLICY to something else than "auto" - use NM connection editor to define static settings The current sysconfig package provides hooks to migrate modify_resolvconf and its variables to netconfig as good as reasonable and possible. It does not change the new behavior of the NetworkManager to not to read and merge the NM settings with the static yast2 / sysconfig settings (NETCONFIG_DNS_STATIC_SERVERS/NETCONFIG_DNS_STATIC_SEARCHLIST). When the migration hooks or netconfig with NETCONFIG_DNS_POLICY=!auto does not work correctly, please report as a new bug report. I consider the migration issue as fixed now and the NetworkManager part of this bug as INVALID or WONTFIX (see also comment #2 and #14). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=434575 User mt@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=434575#c21 Marius Tomaschewski changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |NEEDINFO Info Provider| |tambet@novell.com --- Comment #21 from Marius Tomaschewski 2008-10-27 06:53:18 MDT --- Tambet, would it be acceptable for the NetworkManager when we improve the "auto" policy resolving to "STATIC_FALLBACK NetworkManager"? This means, when NM provides some settings we use them, otherwise we fallback to the static settings in sysconfig? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=434575 User mt@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=434575#c23 --- Comment #23 from Marius Tomaschewski 2008-10-27 07:47:16 MDT --- Tambet, what I speak about is this fallback: if [ "$NETCONFIG_DNS_POLICY" = "auto" ]; then if [ "x$NETWORKMANAGER" = "xyes" ] ; then - _NETCONFIG_DNS_POLICY='NetworkManager' + _NETCONFIG_DNS_POLICY='STATIC_FALLBACK NetworkManager' this simply causes, that the static settings (e.g. DNS or NIS) defined in NETCONFIG_XXX_STATIC variables are used when the NetworkManager does not provide anything. Would it make sense / be acceptable from your point of view or should I better let it as it is? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=434575 User tambet@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=434575#c25 Tambet Ingo changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |REOPENED Info Provider|tambet@novell.com | --- Comment #25 from Tambet Ingo 2008-10-27 08:53:39 MDT --- In short, I'm not against it. I did understand what you suggested. Having a safe fallback can not hurt, I just don't want to have people depend on it. If there are bugs in NM where it somehow looses DNS information, I'd like to fix these. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=434575 User ben.kevan@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=434575#c27 --- Comment #27 from Ben Kevan 2008-10-27 09:34:09 MDT --- I guess I should mention when adding: NETCONFIG_DNS_POLICY="STATIC_FALLBACK" (or STATIC) to /etc/sysconfig/network/config, I still do not get the DNS_STATIC_SEARCHLIST config set in /etc/sysconfig/network/config. Adding the fallback sounds like the best choice here also. Also, Setting the policy setting in YaST does not seem to reflect in /etc/sysconfig/network/config (the DNS policy and not the suffixs / addresses themselves. In fact, I had to manually enter the NETCONFIG_DNS_POLICY line, as it was not there. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=434575 User mt@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=434575#c29 Marius Tomaschewski changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |FIXED --- Comment #29 from Marius Tomaschewski 2008-10-27 10:48:29 MDT --- Please reopen or report as new bug when something does not work. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=434575 User stbinner@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=434575#c31 Stephan Binner changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |abittner@stud.fh-heilbronn.de --- Comment #31 from Stephan Binner 2008-10-28 03:06:46 MDT --- *** Bug 439248 has been marked as a duplicate of this bug. *** https://bugzilla.novell.com/show_bug.cgi?id=439248 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.