[Pkg-utopia-maintainers] Bug#642191: Bug#642191: network-manager: On upgrade/restart, resolv.conf is overwritten with empty file

[Hilko Bengen]

* Michael Biebl:

> Is this behaviour reproducable?

Yes. *Stopping* network-manager via the init script reproduces the
behavior.

>> isc-dhcp-client is installed. When ifup is called, the DNS information
>> from the DHCP server is correctly written to /etc/resolv.conf (At the
>> moment, I am not entirely sure what component is responsible for this on
>> my system, but I have been able to reproduce it by calling ifdown eth1;
>> ifup eth1.)
>
> What's the output of (ifconfig / ifconfig -a) and nm-tool.

,----[ /sbin/ifconfig -a ]
| eth1      Link encap:Ethernet  HWaddr 00:25:11:7c:1c:81  
|           inet addr:192.168.1.52  Bcast:192.168.1.255  Mask:255.255.255.0
|           inet6 addr: 2a01:198:3e6:4242:225:11ff:fe7c:1c81/64 Scope:Global
|           inet6 addr: fe80::225:11ff:fe7c:1c81/64 Scope:Link
|           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
|           RX packets:29927523 errors:0 dropped:0 overruns:0 frame:0
|           TX packets:19382631 errors:0 dropped:0 overruns:0 carrier:6
|           collisions:0 txqueuelen:1000 
|           RX bytes:35950333780 (33.4 GiB)  TX bytes:2060924308 (1.9 GiB)
|           Interrupt:41 
| 
| lo        Link encap:Local Loopback  
|           inet addr:127.0.0.1  Mask:255.0.0.0
|           inet6 addr: ::1/128 Scope:Host
|           UP LOOPBACK RUNNING  MTU:16436  Metric:1
|           RX packets:929531 errors:0 dropped:0 overruns:0 frame:0
|           TX packets:929531 errors:0 dropped:0 overruns:0 carrier:0
|           collisions:0 txqueuelen:0 
|           RX bytes:887146940 (846.0 MiB)  TX bytes:887146940 (846.0 MiB)
| 
| virbr0    Link encap:Ethernet  HWaddr 00:00:00:00:00:00  
|           inet addr:192.168.122.1  Bcast:192.168.122.255  Mask:255.255.255.0
|           UP BROADCAST MULTICAST  MTU:1500  Metric:1
|           RX packets:60719 errors:0 dropped:0 overruns:0 frame:0
|           TX packets:103916 errors:0 dropped:0 overruns:0 carrier:0
|           collisions:0 txqueuelen:0 
|           RX bytes:3064976 (2.9 MiB)  TX bytes:150418077 (143.4 MiB)
`----

,----[ nm-tool ]
| 
| NetworkManager Tool
| 
| State: disconnected
| 
| - Device: eth1 -----------------------------------------------------------------
|   Type:              Wired
|   Driver:            ATL1E
|   State:             unmanaged
|   Default:           no
|   HW Address:        00:25:11:7C:1C:81
| 
|   Capabilities:
|     Carrier Detect:  yes
|     Speed:           100 Mb/s
| 
|   Wired Properties
|     Carrier:         on
`----

> It is possible that network-manager gets confused by the tap0 and vde0
> intefaces, which it tries to manage and as it doesn't get a connection
> for them, it creates an empty resolv.conf.

There *are* entries in /e/n/i for tap0 and vde0 which I didn't mention
earlier, but they do not exist because there's no "auto" entry for them.

This is my NetworkManager.conf:

,----
| [main]
| plugins=ifupdown,keyfile
| 
| [ifupdown]
| managed=false
`----

Unless I am missing something in the NetworkManager.conf(5) manpage, the
interfaces listed in /e/n/i should have been ignored alltogether.

Cheers,
-Hilko