Comment 9 for bug 1273201

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?