[Bug 192566] Re: dhclient updates resolv.conf behind network-manager's back

[Steinar Bang]

>>>>> Paul Smith <psmith at gnu.org>:

> This might be a problem but I don't see how it proposes to fix bug
> #90681

I didn't say anything about this bug report proposing to fix #90681.

I said that what is described in this bug report is probably the root
cause of that bug, and several other similar bugs.

> unless we can modify every application, including 3rd party VPN tools,
> that want to change /etc/resolv.conf to use NetworkManager to do it
> instead of modifying the file directly.

This bug report isn't about about every application wanting to change
/etc/resolv.conf.

It is about a concrete DHCP client, the DHCP client installed by a
standard Ubuntu install, modifying the /etc/resolv.conf file behind
NetworkManager's back.

What this means, is that you need to install by default a DHCP client
that works well with NetworkManager (does NetworkManager need one?  Does
it have its own?  It's very hard to find documentation on
NetworkManager, unfortunately...).

If you're using NetworkManager, it should be the only application
touching the /etc/resolv.conf file.  If it isn't, things will break.

Note1: the /etc/resolv.conf file from the initial DHCP lease, is
obviously written by NetworkManager, so either it's using its own DHCP
client, or it does interoperate with the existing DHCP client

Note2: the VPN client mentioned in the bug report plays well with
NetworkManager.  The VPN client doesn't change the /etc/resolv.conf
file, NetworkManager does.

-- 
dhclient updates resolv.conf behind network-manager's back
https://bugs.launchpad.net/bugs/192566
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dhcp3 in ubuntu.