[Pkg-utopia-maintainers] Bug#530335: network-manager tries to bring up ports of a bridge

[Sebastian Niehaus]

Package: network-manager
Version: 0.6.6-3
Severity: normal

Since installing a bridge interface for the use with VirtualBox I 
noticed the computer loosing sometimes network connection. 


I could not ping hosts in my local net (and not any others of course):
"host unreachable".

/etc/network/interfaces was edited like documented in 
http://wiki.debian.org/VirtualBox#SettingupbridgednetworkingforVirtualBox.28VirtualBox.3C2.1.0.29


========================================================
auto lo
iface lo inet loopback


auto br0
iface br0 inet dhcp
        bridge_ports eth0
        bridge_fd 2.5
========================================================


br0 and eth0 were assigned the same IP address since they appeared
with the same MAC to the DHCP server. Network connectivity broke hours
or even days(!) after starting the system. Restarting network-manager
solved the problem for more hours or days but after some undefined
time connectivity broke again. 


My (possible) work around is a slightly modified /etc/network/interfaces:

========================================================
# The loopback network interface
auto lo
iface lo inet loopback


# <HACK> This is an ugly hack to "blacklist" eth0 from being configured with 
# network-manager:

manual eth0
iface eth0 inet static
# </HACK>


auto br0
iface br0 inet dhcp
        bridge_ports eth0
        bridge_fd 2.5
========================================================


Now eth0 is not assigned an IP. Since this configuration is only few minutes
old I cannot assure it will solve my problem but I am quite confident it 
will do the trick. 

I would like to see any option to blacklist interfaces from being configured
by network-manager or -- even better -- network-manager could detect ports 
of a bridge interface an leave them alone. 


Thanks, 


Sebastian 




-- System Information:
Debian Release: 5.0.1
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 2.6.26-2-686 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages network-manager depends on:
ii  adduser                  3.110           add and remove users and groups
ii  dbus                     1.2.1-5         simple interprocess messaging syst
ii  dhcdbd                   3.0-5           D-Bus interface to the ISC DHCP cl
ii  hal                      0.5.11-8        Hardware Abstraction Layer
ii  ifupdown                 0.6.8+nmu1      high level tools to configure netw
ii  iproute                  20080725-2      networking and traffic control too
ii  libc6                    2.7-18          GNU C Library: Shared libraries
ii  libdbus-1-3              1.2.1-5         simple interprocess messaging syst
ii  libdbus-glib-1-2         0.76-1          simple interprocess messaging syst
ii  libgcrypt11              1.4.1-1         LGPL Crypto library - runtime libr
ii  libglib2.0-0             2.16.6-1+lenny1 The GLib library of C routines
ii  libgpg-error0            1.4-2           library for common error values an
ii  libhal1                  0.5.11-8        Hardware Abstraction Layer - share
ii  libiw29                  29-1.1          Wireless tools - library
ii  libnl1                   1.1-2           library for dealing with netlink s
ii  libnm-util0              0.6.6-3         network management framework (shar
ii  lsb-base                 3.2-20          Linux Standard Base 3.2 init scrip
ii  wpasupplicant            0.6.4-3         Client support for WPA and WPA2 (I

Versions of packages network-manager recommends:
ii  network-manager-gnome         0.6.6-4    network management framework (GNOM

network-manager suggests no packages.

-- debconf-show failed