[Pkg-utopia-maintainers] Bug#642013: network-manager: managed=true/false still rewrites resolv.conf, unable to network regardless

[Moshe Yudkowsky]

Package: network-manager
Version: 0.9.0-2
Severity: important

Each time my system starts up, the file /etc/resolv.conf is overwritten 
by NetworkManager.  As as  result, DNS stops working.

I've tried managed=true and managed=false. I have the appropriate 
configuration in /etc/network/interfaces -- at least one that worked 
until Network Manager
starting overwriting resolv.conf.

To be more clear, /etc/resolv.conf contains:

nameserver xx.xx.xx.xx
nameserver yy.yy.yy.yy

and /etc/network/interfaces contains

allow-hotplug eth4
  iface eth4 inet static
  address zz.zz.zz.zz
  netmask zzz.zz.zz.zz
  gateway zz.zz.zz.zz
  mtu 1492

Prior to the latest update I took from Debian, this combination worked. 
As of the latest update, the resovl.conf is overwritten by 
NetworkManager and DNS fails.

I then disabled eth4 in /etc/network/interfaces and created a connection 
using network-manager-gnome. With some luck I've managed to get that 
configuration working.

A look at http://live.gnome.org/NetworkManager/SystemSettings shows _no 
information at all_ about
where nameserver settings are supposed to co-exist with NetworkManager 
for Debian installations if I do not want NM to manage the settings -- 
where is this information supposed to go? Regardless, according to
the manual, if managed=false, eth4 with its entry in 
/etc/network/interfaces should not be affected by NetworkManager, but it is.

The counter-argument is that nameserver is now set globally by 
NetworkManager, which is great, but how does that happen?

Until I figured out how to co-exist and use NM, as a result of the 
managed=false not working as expected, in this release after a reboot I 
had to physically copy the prior
of resolv.conf to overwrite the NetworkManager version, and I have to 
restart services such as stunnel that
failed due to the NetworkManager rewrite.


-- System Information:
Debian Release: wheezy/sid
   APT prefers unstable
   APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.39-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages network-manager depends on:
ii  adduser                3.113
ii  dbus                   1.2.20-2
ii  isc-dhcp-client        4.1.1-P1-17
ii  libc6                  2.13-21
ii  libdbus-1-3            1.4.14-1
ii  libdbus-glib-1-2       0.94-4
ii  libgcrypt11            1.5.0-3
ii  libglib2.0-0           2.28.6-1
ii  libgnutls26            2.12.10-2
ii  libgudev-1.0-0         172-1
ii  libnl1                 1.1-7
ii  libnm-glib4            0.9.0-2
ii  libnm-util2            0.9.0-2
ii  libpolkit-gobject-1-0  0.102-1
ii  libuuid1               2.19.1-5
ii  lsb-base               3.2-28
ii  udev                   172-1
ii  wpasupplicant          0.7.3-3.1

Versions of packages network-manager recommends:
ii  dnsmasq-base  2.58-3
ii  iptables      1.4.12-1
ii  modemmanager  0.5-1
ii  policykit-1   0.102-1
ii  ppp           2.4.5-5

Versions of packages network-manager suggests:
pn  avahi-autoipd  <none>

-- Configuration Files:
/etc/NetworkManager/NetworkManager.conf changed:
[main]
plugins=ifupdown,keyfile
[ifupdown]
managed=false


-- no debconf information


-- 
Moshe Yudkowsky * moshe at pobox.com * www.pobox.com/~moshe