https://bugzilla.novell.com/show_bug.cgi?id=388266
User tambet@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=388266#c8
Tambet Ingo changed:
What |Removed |Added
----------------------------------------------------------------------------
AssignedTo|tambet@novell.com |mzugec@novell.com
--- Comment #8 from Tambet Ingo 2008-05-15 01:39:52 MST ---
I suggest using NetworkManager's connection editor to create a new system
connection (new in beta 3) and fill the static IP configuration there. The
content of /etc/resolv.conf is meant to be dynamic: VPN should be allowed to
add internal servers, dialup connections have their own temporary servers that
only work when the conneciton is estabilished using dialup etc... In suse, it's
not possible to have static IP configuration for a device and dynamic for
another device - The static configuration's DNS information gets overwritten as
soon as a device with dynamic configuration (or even VPN over that static conf)
is used since there's no backup location for the contents of /etc/resolv.conf.
As of this issue here, I'd say it's a yast bug: NM uses
DHCLIENT_MODIFY_RESOLV_CONF variable to allow/disallow updating
/etc/resolv.conf and it's not possible to change the state of this variable
through yast when all devices are configured to use static IP. Also, I'd say
it's not possible to use one device with static and another with dynamic
configuration simulatenously on suse.
--
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.