Hi Mathieu, I've done a few more tests. All tests are done in an english Ubuntu 13.10 qemu/kvm virtual machine, just to be sure that neither my host hardware nor my language settings are the problems.
As usual i've created a bridge via the network-manager-gnome applet, attached the only physical network device, enabled autoconnection and disabled "Automatically connect to this when it is available" for the "Wired connection 1" finally. After a reboot the following could be seen: 0.9.8.0-0ubuntu22: eth0 up, bridge0 down, no device configured 0.9.8.0-0ubuntu22 minus bridge_ignore_without_connections.patch: eth0 up, bridge0 up, eth0 attached to bridge, bridge0 configured Furthermore i've checked the behaviour with the upstream version e78c3e83d2e0b49641c9d484e0b35b3c6ff9f0db which is - according to the debain changelog - the version this patches was developed for. e78c3e8: eth0 up, bridge0 up, eth0 attached to bridge, bridge0 configured e78c3e8 plus bridge_ignore_without_connections.patch: eth0 up, bridge0 down, no device configured May i do s.th. horribly wrong, but _for me_ it looks like the host bridge functionality is broken since the introduction of the patch. As I stated in my initial post, i could not encounter any problems with additional libvirt bridges when i rollback the patch. Is it possible that the bug which this patch was written for, is fixed with the upstream commit 17338069e332bb73e4d9e7332b67b7853fbe83b7? -- You received this bug notification because you are a member of Desktop 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: Incomplete 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 -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
