gnome-system-tools network-admin does not play nicely with resolvconf

Bug #60518 reported by Søren Boll Overgaard
6
Affects Status Importance Assigned to Milestone
gnome-system-tools (Ubuntu)
Medium
Unassigned

Bug Description

Binary package hint: gnome-system-tools

I have two network interfaces, eth0 a wireless interface and eth1 a wired ethernet interface.

In network-admin I've configured the eth1 interface via DHCP. I then select the interface and click the "Activate". All is well, the interface gets configured and /etc/resolv.conf contains the stuff received from the dhcp server. If I then click the "OK" button to exit network-admin, /etc/resolv.conf reverts back to containing no configuration data (only the boilerplate info about it being a dynamically generated file).

For the record, I have no entries in the DNS tab in network-admin.

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thanks for your bug. What version of Ubuntu do you use?

Changed in gnome-system-tools:
assignee: nobody → desktop-bugs
status: Unconfirmed → Needs Info
Revision history for this message
Søren Boll Overgaard (boll) wrote : Re: [Bug 60518] Re: /etc/resolv.conf gets clobbered when the OK button is pressed

On Fri, Sep 15, 2006 at 07:31:27AM -0000, Sebastien Bacher wrote:
> Thanks for your bug. What version of Ubuntu do you use?

Dapper.
If you need additional info, please let me know.

--
Søren O.

"Oh, bother" said the Borg, "we've assimilated Pooh".

Revision history for this message
Sebastien Bacher (seb128) wrote : Re: [network-admin] /etc/resolv.conf gets clobbered when the OK button is pressed

You wrote "only the boilerplate info about it being a dynamically generated file", resolv.conf has no such comment on a default installation. Do you use the "resolvconf" package?

Revision history for this message
Søren Boll Overgaard (boll) wrote : Re: [Bug 60518] Re: [network-admin] /etc/resolv.conf gets clobbered when the OK button is pressed

Hi,

On Mon, Sep 18, 2006 at 11:54:19AM -0000, Sebastien Bacher wrote:
> You wrote "only the boilerplate info about it being a dynamically
> generated file", resolv.conf has no such comment on a default
> installation. Do you use the "resolvconf" package?

[boll@andariel ~]$ dpkg -l|grep resolvconf [18:23]
ii resolvconf 1.34ubuntu2
nameserver information handler
[boll@andariel ~]$

I obviously don't use it directly, I assume the network-admin gui uses it
behind the scenes.

--
Søren O.

"Oh, bother" said the Borg, "we've assimilated Pooh".

Revision history for this message
Sebastien Bacher (seb128) wrote : Re: [network-admin] /etc/resolv.conf gets clobbered when the OK button is pressed

it's rather breaking the config than being used by g-s-t, reassigning the bug to resolvconf, that's an universe package and not part of the stock Ubuntu installation

Changed in gnome-system-tools:
assignee: desktop-bugs → nobody
status: Needs Info → Unconfirmed
Revision history for this message
Norbert (norbert79) wrote :

I can confirm this as an existing problem. In my case, I used DNS Suffixes because of special circumtances. When I use Gnome-Network, it updates the /etc/resolv.conf file. Now, in my case I use DHCP and the DNS Suffixes. So, when Gnome-Network reconnects, it updates /etc/resolv.conf automatically, making my DNS Suffixes disappear. The problem lies in the fact, that Gnome-Network works together with dhcp3, where the configuration is stored in /etc/dhcp3/dhclient.conf.
So the main problem is, that if I want to make the Gnome-Network remember my DNS Suffix settings, I have to manually update /etc/dhcp3/dhclient.conf, and add the following : "prepend domain-name "something.com hu.something.com blog.something.com "; (the space is at the end neccessary, otherwise the DHCP client will give the current DNS Suffix extracted from the DHCP server wrong)
The solution would be, that gnome-network would update /etc/dhcp3/dhclient.conf in case of DHCP, and not resolv.conf. This way changes can be stored for a longer period, and would not go lost after each reconnection.

Daniel T Chen (crimsun)
Changed in resolvconf:
importance: Undecided → Medium
status: New → Confirmed
Revision history for this message
Simon Huerlimann (huerlisi) wrote : Re: resolvconf does not play nicely with dhclient.conf customisations

Does Gnome-Network still break /etc/resolv.conf managed by resolvconf in Jaunty or Lucid? I'm a KDE user, but AFAIK newer GNOME versions use a frontent to network-manager. network-manager is aware of resolvconf and should not produce this problem, anymore.

If the problem still exists, the proper fix would probably be to make Gnome-Network aware of resolvconf.

Revision history for this message
Thomas Hood (jdthood) wrote :

Possibly the same issue as http://bugs.debian.org/258553 -- gnome-system-tools incompatible with resolvconf

Revision history for this message
Thomas Hood (jdthood) wrote :

Elaborating...

gnome-system-tools is incompatible with resolvconf and repeated attempts in the past to modify g-s-t to make it resolvconf-compatible led nowhere.

And last time I checked, g-s-t's manner of network configuration was also incompatible with ifupdown if logical interfaces are given names different from physical interfaces. Basically, g-s-t does not play well with Debian network configuration tools.

So either don't use resolvconf or don't use the network configuration feature of g-s-t.
--
Thomas Hood
Debian resolvconf maintainers

Thomas Hood (jdthood)
summary: - resolvconf does not play nicely with dhclient.conf customisations
+ gnome-system-tools network-admin does not play nicely with resolvconf
Revision history for this message
Stéphane Graber (stgraber) wrote :

Moving back to gnome-system-tools as there isn't much we can do in resolvconf to deal with packages directly poking /etc/resolv.conf.

affects: resolvconf (Ubuntu) → gnome-system-tools (Ubuntu)
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.