http://bugzilla.novell.com/show_bug.cgi?id=550706 http://bugzilla.novell.com/show_bug.cgi?id=550706#c27 --- Comment #27 from Marius Tomaschewski <mt@novell.com> 2009-12-07 19:39:46 UTC --- (In reply to comment #23)
Marius,
I build the new sysconfig package with the patch in Comment #18, then install it, it can't modify the DNS with below command when I delete a server(192.168.1.3) from the dnscfg file.
It is exactly as I've described in comment #13 - it works in ifup mode, but: When NetworkManager is in use, only the NetworkManager is allowed to provide settings to netconfig by default (NETCONFIG_DNS_POLICY="auto" means then "STATIC_FALLBACK NetworkManager") and the NetworkManager is responsible to provide the nameservers in desired order. This exclusivity has been requested by the NetworkManager maintainer in order to ensure correct behavior of the NetworkManager. To workaround the limitation in either the NetworkManager, that it does not provide a way for NM plugins to provide settings to NM or in the vpn plugin that it does not provide them to NetworkManager, you can change the default netconfig policy to allow the plugin to provide its settings. The netconfig policy: NETCONFIG_DNS_POLICY='STATIC_FALLBACK NetworkManager *' should do the job, because the vpn settings have higher prio than NM settings -- because of the ranking. You can document this or of course, you can also ask the NetworkManager maintainer to ACK a change the default netconfig policy in NM mode and resolve "auto" as above instead. (In reply to comment #25)
Is there another solution without that feature mentioned in comment #19?
Well, beside of disabling netconfig by policy and manual configuration, there is a hack that the user can do -- change to a policy to: NETCONFIG_DNS_POLICY='STATIC_FALLBACK * NetworkManager' or NETCONFIG_DNS_POLICY='STATIC_FALLBACK eth1 NetworkManager' This will work also without the ranking feature in netconfig, __but__ it will _very_ fast break the NetworkManager (it prefers any another services from any / specified interface, also from e.g. avahi) and is not a workaround that we can use/propose as a general workaround. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.