This has been fixed in Precise.
** Changed in: network-manager (Ubuntu)
Status: Triaged = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/324233
Title:
Network Manager 0.7
Thanks to Paul Smith for explaining (#27) how resolvconf is supposed to
work. For a more detailed explanation please read the README file in
the resolvconf package.
When resolvconf and NM are both installed the current behavior is this:
The Ubuntu version of resolvconf immediately returns an
natty and kubuntu, no resolvconf
Network Manager broke nameserving when I used it to change the host's
ipaddress
In order to configure a couple of access points I needed to change host's net
address to 192.168.2.x for a while
and then revert to the a static ipaddress instead of the dhcp
** Changed in: network-manager (Ubuntu)
Assignee: Alexander Sack (asac) = (unassigned)
** Changed in: network-manager (Ubuntu)
Status: In Progress = Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thanks for responding and reminding me about this bug. I've recently
discovered most of my grief with respect to VPN connections and network-
manager is caused by incomplete support in network-manager for vpnc. Or
perhaps I should word it that the workarounds could be much more user
friendly if
I don't think it's correct for NetworkManager to write directly to the
file managed by resolvconf. The entire point of resolvconf is that IT'S
supposed to manage the resolv.conf file. Resolvconf is very useful if
you (like I do!) have one or more VPN solutions (sometimes I have to
connect to two
I'm seeing this on Lucid:
NetworkManager: info (eth0): writing resolv.conf to /sbin/resolvconf
resolvconf: Error: /etc/resolv.conf must be a symlink
--
Network Manager 0.7 doesn't use resolvconf to remove nameserver info if it
didn't use resolvconf for adding its nameserver info - wipes
I've been running with a patched version of nm-named-manager for a few
months now; the patch just removes the ability for network-manager to
directly write to /etc/resolv.conf completely, and it's been completely
stable. Every single time I start up, resolvconf is still in use as
expected.
--
In the case I outlined, the only way I could catch it happening was to
shut down and then boot the system off of a Live USB installation, so I
could mount the root filesystem and inspect it before NetworkManager was
started up again (using the GRUB 'recovery console' and 'drop to a root
shell'
I don't think is a correct fix; NetworkManager should *not* overwrite
the file pointed to by the /etc/resolv.conf symlink.
I've got two systems here running Kubuntu Karmic Koala, with
NetworkManager (and kdenetworkmanager), dhclient, dnsmasq, resolvconf
and openvpn installed. If boot in single
That actually sounds like there might be TWO separate cases where NM breaks
resolvconf and only one has been fixed.
--
Network Manager 0.7 doesn't use resolvconf to remove nameserver info if it
didn't use resolvconf for adding its nameserver info - wipes /etc/resolv.conf
link
ok. i think this was supposed to work already, but the fix was not good
enough. preparing a prepared fix.
** Changed in: network-manager (Ubuntu)
Status: Triaged = In Progress
--
Network Manager 0.7 doesn't use resolvconf to remove nameserver info if it
didn't use resolvconf for adding
here a first patch that should fix this.
** Attachment added: lp324233.patch
http://launchpadlibrarian.net/33523413/lp324233.patch
--
Network Manager 0.7 doesn't use resolvconf to remove nameserver info if it
didn't use resolvconf for adding its nameserver info - wipes /etc/resolv.conf
Confirming the solution provided by hashstat. The issue were
/etc/resolv.conf was being set as a file and not a symlink was being
experienced. After adding the dummy postfix conf file the resolv.conf
could be set as a symlink and crucially stayed as a symlink after
reboot.
Here are the exact
(you could just uninstall postfix instead of making fake config)
--
Network Manager 0.7 doesn't use resolvconf to remove nameserver info if it
didn't use resolvconf for adding its nameserver info - wipes /etc/resolv.conf
link
https://bugs.launchpad.net/bugs/324233
You received this bug
As added information, I did not install postfix directly; it was
installed as a dependency to the Linux Standards Base package lsb: lsb
depends on lsb-core, lsb-core depends on postfix.
--
Network Manager 0.7 doesn't use resolvconf to remove nameserver info if it
didn't use resolvconf for
Depends or Recommends? If Recommends, removing it won't harm anything. I had
it installed accidentally too because some development metapackage pulls it in
as a Recommends.
--
Network Manager 0.7 doesn't use resolvconf to remove nameserver info if it
didn't use resolvconf for adding its
After playing with resolvconf and Network Manager, I noticed that
running resolvconf directly always resulted in an error due to a missing
postfix configuration file (/etc/postfix/main.cf). Because resolvconf
was always returning an error, Network Manager always moved on to the
default behavior:
I believe I have found the cause of this bug within nm-named-manager.c.
Should Network Manager fail to update the resolver via the resolvconf
script, then it will fall through to the default behaviour (ie write
details to a temp file and then overwrites /etc/resolv.conf). The code
treats
Patch - If /etc/resolv.conf is a SYMLINK, then overwrite the target
file, not the SYMLINK.
Possibly fixes another bug: NM checks if tmp_resolv_conf is a SYMLINK,
and if so writes to the file pointed to by the symlink. However, when it
replaces resolv.conf, it will do so with the symlink, so
Patch - If resolvconf update fails, and /etc/resolv.conf is a SYMLINK
then do nothing.
If we find /sbin/resolvconf, but the execution of it fails, then check
if /etc/resolv.conf is a SYMLINK. If it is, then report success, and do
not overwrite resolv.conf.
** Attachment added: Ignore
dpkg-reconfigure resolvconf did not help me with this problem, but I
think I have worked it out. Here are the exact steps I took:
sudo /etc/init.d/NetworkManager stop
sudo aptitude remove resolvconf
sudo aptitude purge resolvconf
sudo aptitude install resolvconf
sudo /etc/init.d/NetworkManager
ok hope the title is now good :-P - sorry for the noise.
--
Network Manager 0.7 doesn't use resolvconf to remove nameserver info if it
didn't use resolvconf for adding its nameserver info - wipes /etc/resolv.conf
link
https://bugs.launchpad.net/bugs/324233
You received this bug notification
23 matches
Mail list logo
