[Bug 889423] Re: 802.3ad bonding not configured correctly

Tom Ellis tom.ellis at canonical.com
Mon Feb 20 14:58:17 UTC 2012


The updated vlan, bridge-utils and ifenslave packages from oneiric-
proposed have fixed the issues I had with 802.3ad. Thanks!

** Tags removed: verification-needed
** Tags added: verification-done

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to bridge-utils in Ubuntu.
https://bugs.launchpad.net/bugs/889423

Title:
  802.3ad bonding not configured correctly

Status in “bridge-utils” package in Ubuntu:
  Fix Released
Status in “ifenslave-2.6” package in Ubuntu:
  Fix Released
Status in “vlan” package in Ubuntu:
  Fix Released
Status in “bridge-utils” source package in Oneiric:
  Fix Committed
Status in “ifenslave-2.6” source package in Oneiric:
  Fix Committed
Status in “vlan” source package in Oneiric:
  Fix Committed

Bug description:
  SRU instructions (from comment 41 and 46):
  === bridge-utils ===
  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 at 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 at 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.

  === vlan ===
  Here's a quick example of how to test the new vlan package:

   - Make sure uml-utilities and vlan are installed
   - Add the following entry to /etc/network/interfaces:
  auto eth9.1010
  iface eth9.1010 inet static
      address 192.168.1.1
      netmask 255.255.255.0
   - Create the tap device: tunctl -t eth9
   - Check that the vlan interface has been created and configured correctly: ifconfig eth9.1010
  eth9.1010 Link encap:Ethernet HWaddr ce:51:62:98:16:78
            inet addr:192.168.1.1 Bcast:0.0.0.0 Mask:255.255.255.0
            UP BROADCAST MULTICAST MTU:1500 Metric:1
            RX packets:0 errors:0 dropped:0 overruns:0 frame:0
            TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
            collisions:0 txqueuelen:0
            RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

  Prior to this update, vlan interface creation would be racy as it'd
  depend on the catch all networking.conf job to initialise eth9.1010
  with the race being that this job would be triggered before eth9
  actually exists.

  === ifenslave-2.6 ===
  TODO: Using setup from original description before/after should work but I'll comment with a simplified testcase when I have a minute.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bridge-utils/+bug/889423/+subscriptions




More information about the foundations-bugs mailing list