Hello,
After an upgrade from 10.04 to 12.04, our interfaces files stopped working for
the 802.3ad interfaces. After converting the interfaces file to the new
format, the configuration seems to be correct, but I seem to be running into
a timing issue or race condition again. I implemented most
Hello,
After an upgrade from 10.04 to 12.04, our interfaces files stopped working for
the 802.3ad interfaces. After converting the interfaces file to the new
format, the configuration seems to be correct, but I seem to be running into
a timing issue or race condition again. I implemented most
On a fully updated Ubuntu 12.04
I have dropped packets on the bonded interface:
bond0 Link encap:Ethernet HWaddr 00:10:18:e0:5e:a4
inet6 addr: fe80::210:18ff:fee0:5ea4/64 Scope:Link
UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1
RX packets:315
On a fully updated Ubuntu 12.04
I have dropped packets on the bonded interface:
bond0 Link encap:Ethernet HWaddr 00:10:18:e0:5e:a4
inet6 addr: fe80::210:18ff:fee0:5ea4/64 Scope:Link
UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1
RX packets:315
This bug was fixed in the package vlan - 1.9-3ubuntu3.1
---
vlan (1.9-3ubuntu3.1) oneiric-proposed; urgency=low
* Add a udev trigger similar to bridge-utils' so vlan interfaces are
created when the parent appears (this will then trigger upstart and
ifupdown to configure the
This bug was fixed in the package ifenslave-2.6 - 1.1.0-19ubuntu1.1
---
ifenslave-2.6 (1.1.0-19ubuntu1.1) oneiric-proposed; urgency=low
* Update ifenslave scripts to work with event based boot (LP: #889423):
- Create the master interface whenever a slave comes online
- Make
This bug was fixed in the package bridge-utils - 1.5-2ubuntu1.1
---
bridge-utils (1.5-2ubuntu1.1) oneiric-proposed; urgency=low
* debian/bridge-network-interface.sh: If the interface doesn't exist,
then call the vlan hook and check if the interface appears then.
(LP:
This bug was fixed in the package bridge-utils - 1.5-2ubuntu1.1
---
bridge-utils (1.5-2ubuntu1.1) oneiric-proposed; urgency=low
* debian/bridge-network-interface.sh: If the interface doesn't exist,
then call the vlan hook and check if the interface appears then.
(LP:
This bug was fixed in the package vlan - 1.9-3ubuntu3.1
---
vlan (1.9-3ubuntu3.1) oneiric-proposed; urgency=low
* Add a udev trigger similar to bridge-utils' so vlan interfaces are
created when the parent appears (this will then trigger upstart and
ifupdown to configure the
This bug was fixed in the package ifenslave-2.6 - 1.1.0-19ubuntu1.1
---
ifenslave-2.6 (1.1.0-19ubuntu1.1) oneiric-proposed; urgency=low
* Update ifenslave scripts to work with event based boot (LP: #889423):
- Create the master interface whenever a slave comes online
- Make
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
Server Team, which is
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
Bugs, which is subscribed
** Description changed:
- Configuring an 802.3ad bond doesn't appear to work correctly. The following
entry in /etc/network/interfaces should configure an 802.3ad bond between
interfaces eth2 and eth3:
- #auto bond0
- iface bond0 inet static
- address 10.191.62.2
- netmask 255.255.255.0
-
** Description changed:
- Configuring an 802.3ad bond doesn't appear to work correctly. The following
entry in /etc/network/interfaces should configure an 802.3ad bond between
interfaces eth2 and eth3:
- #auto bond0
- iface bond0 inet static
- address 10.191.62.2
- netmask 255.255.255.0
-
** Branch linked: lp:ubuntu/oneiric-proposed/vlan
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bridge-utils in Ubuntu.
https://bugs.launchpad.net/bugs/889423
Title:
802.3ad bonding not configured correctly
To manage
@Stéphane: I'm not sure that /var/run → /run is a good idea as an SRU,
and it doesn't look like it would be terribly difficult to revert that
change. What documentation points to /run rather than /var/run?
--
You received this bug notification because you are a member of Ubuntu
Server Team,
03:52 stgraber RAOF: hey there
03:53 stgraber RAOF: thanks for accepting the vlan package
03:54 stgraber RAOF: as for the extra delta in the ifenslave-2.6 SRU (one
line change for /run + documentation), the idea was that reverting these just
for the sake of having
a smaller
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
** Branch linked: lp:ubuntu/oneiric-proposed/ifenslave-2.6
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bridge-utils in Ubuntu.
https://bugs.launchpad.net/bugs/889423
Title:
802.3ad bonding not configured correctly
To manage
** Branch linked: lp:ubuntu/oneiric-proposed/vlan
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/889423
Title:
802.3ad bonding not configured correctly
To manage notifications about this bug go to:
@Stéphane: I'm not sure that /var/run → /run is a good idea as an SRU,
and it doesn't look like it would be terribly difficult to revert that
change. What documentation points to /run rather than /var/run?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
03:52 stgraber RAOF: hey there
03:53 stgraber RAOF: thanks for accepting the vlan package
03:54 stgraber RAOF: as for the extra delta in the ifenslave-2.6 SRU (one
line change for /run + documentation), the idea was that reverting these just
for the sake of having
a smaller
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
** Branch linked: lp:ubuntu/oneiric-proposed/ifenslave-2.6
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/889423
Title:
802.3ad bonding not configured correctly
To manage notifications about this
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
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
Hello Albert, or anyone else affected,
Accepted bridge-utils into oneiric-proposed, the package will build now
and be available in a few hours. Please test and give feedback here. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in
** Branch linked: lp:ubuntu/oneiric-proposed/bridge-utils
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bridge-utils in Ubuntu.
https://bugs.launchpad.net/bugs/889423
Title:
802.3ad bonding not configured correctly
To manage
Hello Albert, or anyone else affected,
Accepted bridge-utils into oneiric-proposed, the package will build now
and be available in a few hours. Please test and give feedback here. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in
** Branch linked: lp:ubuntu/oneiric-proposed/bridge-utils
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/889423
Title:
802.3ad bonding not configured correctly
To manage notifications about this
Now that everything seems to be working in Precise, I'll start uploading the
SRUs for Oneiric.
The affected packages are vlan, bridge-utils and ifenslave-2.6.
I added a task for each of them and will be uploading packages to
oneiric-proposed shorly.
** Also affects: ifenslave-2.6 (Ubuntu
** Changed in: vlan (Ubuntu Oneiric)
Status: In Progress = Fix Committed
** Changed in: bridge-utils (Ubuntu Oneiric)
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bridge-utils in
Just a quick note for the SRU team :)
The ifenslave-2.6 upload makes a pretty big diff, including a documentation
update.
I could have stripped it down to the absolutely necessary changes but that'd
still have been all of debian/pre-up which is by far the biggest change in the
package. As the
Now that everything seems to be working in Precise, I'll start uploading the
SRUs for Oneiric.
The affected packages are vlan, bridge-utils and ifenslave-2.6.
I added a task for each of them and will be uploading packages to
oneiric-proposed shorly.
** Also affects: ifenslave-2.6 (Ubuntu
** Changed in: vlan (Ubuntu Oneiric)
Status: In Progress = Fix Committed
** Changed in: bridge-utils (Ubuntu Oneiric)
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Just a quick note for the SRU team :)
The ifenslave-2.6 upload makes a pretty big diff, including a documentation
update.
I could have stripped it down to the absolutely necessary changes but that'd
still have been all of debian/pre-up which is by far the biggest change in the
package. As the
** Package changed: ifupdown (Ubuntu) = ifenslave-2.6 (Ubuntu)
** Changed in: ifenslave-2.6 (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/889423
** Branch linked: lp:ubuntu/ifenslave-2.6
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/889423
Title:
802.3ad bonding not configured correctly
To manage notifications about this bug go to:
Great to hear!
I'll be pushing that into Precise then and then look at the SRU, some of
the changes I had to do change the behaviour of bonding quite a lot, so
it may take a while to discuss and prepare the SRU for lucid and above.
--
You received this bug notification because you are a member
Hi Albert, I just uploaded one more ifenslave to the PPA.
This one should fix the bridging issues by calling the bridging udev hook once
the bond is ready.
Please note that I haven't tested this particular change at all as I
don't have my test hardware around at the moment.
Let me know if that
Just finished testign the new ifenslave. Rebooted three times and bond0,
br0, and bond1 came up successfully every time!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/889423
Title:
802.3ad bonding
And one more version pushed to my PPA.
This one should also fix some race conditions when using the bond
interface in a bridge, with vlans or doing dhcp on it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I've updated to ifenslave-2.6_1.1.0-19ubuntu2~ppa3_amd64.deb and no longer need
the following in auto bond0:
post-up ip link set dev bond0 up
For auto br0, I still need:
up brctl addif br0 bond0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Hmm, ok, I'm a bit surprised that bond0 still doesn't get added to the
bridge.
What's supposed to happen with that new ifenslave at boot time is:
1) One of the network card gets detected and sends a udev event
2) Upstart picks up the event and brings up the interface
3) As the interface is part
Looking at the boot sequence:
Begin: Running /[ 40.126206] EXT4-fs (dm-1): mounted filesystem with
ordered data mode. Opts: (null)
scripts/local-bottom ... done.
done.
Begin: Running /scripts/init-bottom ... done.
[about 1 minute delay]
fsck from util-linux 2.19.1
fsck from
** Attachment added: Kernel log
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/889423/+attachment/2615445/+files/kern.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/889423
Title:
Wow, that's quite a lot of things happening on that system :)
So indeed looking at the number of CPUs, network cards and disks showing up,
it's enough to flood udev and upstart and likely make things start a bit slower
than usual and so out of order.
Essentially, the fallback networking script
The pre-up sleep 2 didn't work. But, pre-up sleep 5 did.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/889423
Title:
802.3ad bonding not configured correctly
To manage notifications about this bug
A new test ifenslave is available in my ppa:
https://launchpad.net/~stgraber/+archive/experimental/+packages
The package is built for Precise but I'd expect it to work just as well
on Oneiric (without the need for rebuild).
Some other users are testing it now and if I don't get negative
Tried adding the bond0 interface to a bridge but it's not in the RUNNING
state:
# cat /etc/network/interfaces
...
auto bond0
iface bond0 inet manual
bond-mode 802.3ad
bond-lacp_rate slow
bond-miimon 100
bond-updelay 200
bond-slaves none
post-up ip link set dev
You shouldn't have to, but it may be a case where devices aren't brought
up in the right order.
On your system, can you try to do:
- ifdown -a
- ifup lo
- ifup eth2
- ifup eth3
- ifup bond0
- ifup br0
And see if that brings everything online properly?
With that test ifenslave in my PPA, I
After ifdown -a, neither bond0 nor br0 are show in ifconfig -a. However,
after ifup eth2, bond0 and br0 are brought up:
# ifdown -a
# ifup lo
# ifup eth2
...
# ifconfig -a
...
bond0 Link encap:Ethernet HWaddr 00:1b:21:d3:f6:0a
UP BROADCAST RUNNING MASTER MULTICAST MTU:1500
I now have the following in /etc/network/interfaces:
auto bond0
iface bond0 inet manual
bond-slaves none
bond-mode 802.3ad
bond-lacp_rate slow
bond-miimon 100
bond-updelay 200
auto eth2
iface eth2 inet manual
bond-master bond0
auto eth3
iface eth3 inet manual
bond-master bond0
Ok, that looks good, the slaves are down because the master itself is down.
Bringing the master up and giving it an IP address should bring the slaves up
and hopefully negotiate LACP with your switch.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This bonded interface will not have an IP. It will be added to a bridge
for KVM. My expectation is that even without an IP, bond0 should be up
after the system boots with the above config.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I'm not sure if ifupdown guarantees that an interface marked as manual
is to be brought up but that's an interesting point thing to test.
For now, can you try adding a:
post-up ip link set dev bond0 up
And see if that indeed brings up the slaves and negociates LACP?
--
You received this bug
Added post-up ip link set dev bond0 up and that appears to work:
$ ifconfig bond0
bond0 Link encap:Ethernet HWaddr 00:1b:21:d3:f6:0b
inet6 addr: fe80::21b:21ff:fed3:f60b/64 Scope:Link
UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1
RX packets:15
Yep, that looks good.
I'll make sure we won't get any weird bug by setting the link up by default and
if I don't see anything exploding, I'll change that in my branch.
Thanks for the tests.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Oh, odd. It comes up fine on a cold boot for me.
Out of interest, how is your switch configured? is LACP in active or
passive?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/889423
Title:
802.3ad
I'm also going to copy/paste an answer I posted somewhere else:
Also, as noted on IRC, bond-primary seems to be limited to active-backup only.
For reference: http://www.kernel.org/doc/Documentation/networking/bonding.txt
Here's a minimal 802.3ad config:
# This file describes the network
I've been testing an experimental patched ifupdown by stgraber
https://launchpad.net/~stgraber/+archive/experimental/+build/2931666 which
should get around any race conditions.
This installs fine onto oneiric too even though the target is precise.
I've had more success with this but still
I tried this version of ifenslave and didn't see any change:
$ cat /etc/network/interfaces
...
auto bond0
iface bond0 inet manual
bond-slaves none
bond-primary eth4 eth5
bond-mode 802.3ad
bond-lacp_rate fast
bond-miimon 100
bond-updelay 200
auto eth4
iface eth4
What's more, if I comment auto bond0, auto eth4, and auto eth5 and
manuall start up the interfaces with:
# ifup bond0
# ifup eth4
# ifup eth5
the bond0 interface does not come up correctly. With the previous
ifenslave-2.6, this worked to bring up bond0. So, the latest ifenslave-2.6
you're
I don't see the drop packets at all, maybe it's driver related. So yeah,
perhaps it'll be better to open another issue for that.
I tested ifupdown 0.7~beta2 from debian experimental and the problem
still persists. The package uses sysvinit scripts instead of the Ubuntu
upstart delta but the
I created bug #890475 for the dropped packets. Tom, I'm using the igb
driver for my Intel E1G42ET Gigabit ET Dual Port Server Adapter. I've
also tried using the latest igb driver from intel with no difference.
However, considering that I get no dropped packets on either RHEL6 or
11.10 with a
With lacp_rate=fast, the number of dropped packets increases faster than
with lacp_rate=slow (the default).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/889423
Title:
802.3ad bonding not
Another datapoint. I installed the 2.6.39-3.10 kernel from
https://launchpad.net/ubuntu/oneiric/+source/linux/2.6.39-3.10. I
configured bonding in this version of the kernel the same way that I
configured it for the 3.0.0-12-server kernel. For the 2.6.39-3.10
kernel, there are *NO* dropped
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ifupdown (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/889423
Title:
I'm also seeing this and have carried out some tests.
The following interfaces config works across Lucid, Maverick Natty but fails
on Oneiric:
==
auto bond0
iface bond0 inet static
bond-slaves none
bond-mode 802.3ad
bond-miimon 100
address 10.153.107.22
Tom, can you also confirm the dropped packets I'm seeing on bond0?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/889423
Title:
802.3ad bonding not configured correctly
To manage notifications
Looking at my original post and the ifconfig output of bond0:
# ifconfig -a
bond0 Link encap:Ethernet HWaddr 00:1b:21:b7:21:ea
inet addr:10.191.62.2 Bcast:10.191.62.255 Mask:255.255.255.0
inet6 addr: fe80::21b:21ff:feb7:21ea/64 Scope:Link
UP BROADCAST MASTER
** Attachment added: ifconfig-802.3ad
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/889423/+attachment/2595910/+files/ifconfig-802.3ad
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I do not see any dropped packets.
In syslog I have a lot of these:
[10292.612017] bonding: bond0: Warning: Found an uninitialized port
Attaching my /proc/net/bonding/bond0 ifconfig outputs
** Description changed:
Configuring an 802.3ad bond doesn't appear to work correctly. The following
Consider the following entries in /etc/network/interfaces:
#auto bond0
iface bond0 inet static
address 10.191.62.2
netmask 255.255.255.0
broadcast 10.191.62.255
bond-slaves none
bond-primary eth2 eth3
bond-mode 802.3ad
bond-lacp_rate fast
bond-miimon 100
#auto eth2
iface eth2 inet
This is against Ubuntu Server 11.10.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/889423
Title:
802.3ad bonding not configured correctly
To manage notifications about this bug go to:
75 matches
Mail list logo
