touch-packages team mailing list archive

[Julian Alarcon <alarconj@xxxxxxxxx>]

Hi

I got the same problem in Ubuntu 14.04.

I used KVM on Ubuntu 14.04 with network using bridge, modifying the
/etc/network/interfaces but today I tried to set the bridge using
Network  Manager.

After setting the bridge on network manager, I used the brctl show and
the eth0 card were not linked to the bridge, but taking the advice of
opening the Network Manager configuration file
(/etc/NetworkManager/NetworkManager.conf) and saving it without editing
it, I got the bridge up.

So this problem is still there in Ubuntu 14.04, can somebody set the
affect release to Ubuntu 14.04 Trusty Tahr?

Also, when I set this bridge, I got an error in the network, my PC is
connected to a Cisco Switch 2960-S, my port become err-disable status.
Because of this I removed all the NM configuration and used the old
method and the bridged network worked again.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1273201

Title:
  bridge_ignore_without_connections.patch breaks NM created bridge at
  boot

Status in network-manager package in Ubuntu:
  Fix Released

Bug description:
  I've created a bridge with network-manager-gnome, the bridge slave
  physical device is eth0. After a reboot the bridge is brought up, but
  eth0 isn't attached.

  First test-case:
  Created a bridge with network-manager-gnome with the bridge slave physical device is eth0 and remove all other connections. After a reboot the bridge is brought up, but eth0 isn't attached. When I open /etc/NetworkManager/NetworkManager.conf and save it without any modification, eth0 is instantly added to my bridge. Strange!

  Second test-case:
  Created a bridge with network-manager-gnome with the bridge slave physical device is eth0. Disable the "autoconnect" of the default wired network. After a reboot the bridge is brought up, but eth0 isn't  attached. Instead eth0 is brought up and full configured.

  After compiling and testing different upstream versions, i could track
  the problem down to bridge_ignore_without_connections.patch.  A
  network-manager package without this specific patch, brings my bridge
  up at boot and adds eth0 to the bridge in both test-cases.

  I've checked the behaviour on my ubuntu 13.10 box with network-manager
  (0.9.8.0-0ubuntu22)  and the trusty version network-manager
  (0.9.8.8-0ubuntu1) .

  Till now i couldn't  encounter any sideeffects of removing this patch
  with the bridge created by libvirt.

  Regards
  Mathias Kresin

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1273201/+subscriptions