Comment 41 for bug 889423

So there are two things to test with that new bridge-utils:
 1) Bridge interface with bridge-ports set instead of bridge_ports works too
 2) Bridging a non-existing vlan interface will now create it

These two are in the udev hooks, so need to be tested by creating a network interface, like a tap device (using uml-utilities to create it).

Test for 1)
 - Make sure uml-utilities and bridge-utils are both installed
 - Add the following entry to /etc/network/interfaces:
auto br0
iface br0 inet static
    address 192.168.1.1
    netmask 255.255.255.0
    bridge-ports eth9
 - Create the tap device: tunctl -t eth9
 - Check that the bridge has been created and the interface added to it (bridge shouldn't have an IP configuration at this point):
root@castiana:~# brctl show br0
bridge name bridge id STP enabled interfaces
br0 8000.1a6bffdb2551 no eth9

The previous release wouldn't do anything unless you were using bridge_ports.

Test for 2)
 - Make sure uml-utilities, bridge-utils and vlan are all intalled
 - Add the following entry to /etc/network/interfaces:
auto br0
iface br0 inet static
    address 192.168.1.1
    netmask 255.255.255.0
    bridge-ports eth9.1010
 - Create the tap device: tunctl -t eth9
 - Check that the bridge has been created and the interface added to it (bridge shouldn't have an IP configuration at this point):
root@castiana:~# brctl show br0
bridge name bridge id STP enabled interfaces
br0 8000.06c2192d61ab no eth9.1010

The previous release would create the bridge but not add the port to it as the tag interface wouldn't exist.

Between each test, cleanup with:
 - tunctl -d eth9
 - ifconfig br0 down
 - brctl delbr br0

The use of eth9 instead of tap0 is done on purpose as the vlan script explicitly checks for interfaces with eth, bond or wlan in their name.