Thanks! Maybe there is a config that isn't being read properly by NM at the time where the connections are getting matched?
I think this indicates where the problem is: Jan 26 20:12:12 desktop NetworkManager[851]: <debug> [1390763532.45734] [nm-manager.c:2950] nm_manager_activate_connection(): Activation of 'bridge0 Sklave 1' requires master connection 'Brückenverbindung 1' Jan 26 20:12:12 desktop NetworkManager[851]: <info> Connection 'bridge0 Sklave 1' auto-activation failed: (1) No compatible disconnected device found for master connection 9374baaf-ff05-4f4c-9e31-8e4a2b007d9f. The system is looking for a disconnected device; I guess eth0 might not be seen as disconnected in NM (although it does not appear to be if I'm to believe the other lines nearby). It's also expecting eth0 to be a specfic device, which may be configured via a MAC address or via another config entry in the connection for Br?ckenverbindung 1". Is there anyway you could share as much of that connection file as possible? -- 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
