Janusz: Please try with oneiric-proposed added as described above.
Indeed, you should be using bond-master on a slave interface instead of
listing the slaves on the bond, at least in 802.3ad configuration, some
other modes may require an explicit list of master and slaves.
--
You received this b
Had the same problem on 11.10 x86_64, but this can be easily solved by
changing network configuration a bit.
One has to use:
iface ethX ...
bond-master bondX
instead of
iface bondX ...
slaves ethX
Either manuals/howtos should be updated or the 'slaves' functionality should be
restored
I
The patch for this bug breaks the use of bond_primary in
/etc/network/interfaces. See Bug #823366.
The following piece of code from the "setup_master()" function in
/etc/network/if-pre-up.d/ifenslave will only setup a primary if the
primary is listed as a slave (which will not be the case with th
** Changed in: ifenslave-2.6 (Debian)
Status: Unknown => 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/482419
Title:
802.3ad interface bonding fails if started too early
To mana
Oh, and output from /proc/net/bonding/bond0:
Ethernet Channel Bonding Driver: v3.5.0 (November 4, 2008)
Bonding Mode: adaptive load balancing
Primary Slave: None
Currently Active Slave: eth0
MII Status: up
MII Polling Interval (ms): 100
Up Delay (ms): 200
Down Delay (ms): 200
Slave Interface: e
Hmm, I don't seem to be able to reproduce your problem.
I currently use:
stgraber@halla:~$ cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The loopback network interface
auto
Can you confirm that downgrading ifenslave to the older version fixes it
for you?
I'm going to setup an identical server (2x e1000e with bond_mode 6) this
afternoon and see if I can reproduce the same regression.
--
You received this bug notification because you are a member of Ubuntu
Bugs, whic
After applying the update on my servers, I got massive problems in the
stability of my network connections. I was running bond in mode 6, which
now seems not to work anymore.
auto bond0
iface bond0 inet static
hwaddress ether 00:30:88:88:88:88
address 192.168.111.5
netmask 255.255.254
This bug was fixed in the package ifenslave-2.6 - 1.1.0-14ubuntu2.2
---
ifenslave-2.6 (1.1.0-14ubuntu2.2) lucid-proposed; urgency=low
* Fix pre-up script to first setup the master and only
then setup the slaves. (LP: #482419)
-- Stephane GraberTue, 07 Jun 2011 13:41:43 -040
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/482419
Title:
802.3ad interface bonding fails if started too early
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubun
The package from proposed works here.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/482419
Title:
802.3ad interface bonding fails if started too early
--
ubuntu-bugs mailing list
ubuntu-bugs@lists
I enabled proposed on my test server and made sure that my upload indeed
works (as in, that the patch didn't vanish for some reason).
It works great here, but I want at least someone else to confirm that
the proposed package also works for them (and I'm sure the SRU team
wants that too).
--
You
** Branch linked: lp:ubuntu/lucid-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/482419
Title:
802.3ad interface bonding fails if started too early
--
ubuntu-bugs mailing lis
Accepted into lucid-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 advance!
** Changed in: ifenslave-2.6 (Ubuntu Lucid)
Above patch has now been uploaded to lucid-proposed waiting for a SRU team
member to review and let it through.
Once it's through, I'd recommend anyone with a similar setup to run the test.
The above /etc/network/interfaces and switch configuration should consistently
reproduce the issue with cu
The only applied change is the following:
--- ../../../orig/ifenslave-2.6-1.1.0/debian/pre-up 2011-06-07
14:03:19.0 -0400
+++ pre-up 2011-06-07 14:26:30.449289528 -0400
@@ -125,5 +125,5 @@ fi
[ -z "$BOND_MASTER$BOND_SLAVES" ] && exit
add_master
-enslave_slaves
setup_master
+
With the fix applied, I now get:
Switch:
sw06# show lacp port-channel 4
Port-Channel ch4
Port Type Gigabit Ethernet
Attached Lag id:
Actor
System Priority:1
MAC Address:00:14:22:66:25:10
Admin Key: 28
Oper K
With the current package, I get the issue described in this bug report,
with the following output:
Switch:
sw06# show lacp port-channel 4
Port-Channel ch4
Port Type Gigabit Ethernet
Attached Lag id:
Actor
System Priority:1
MAC Address:00:14:22
I'm having a look at this bug now.
I used a spare DELL PowerEdge 750 with two Intel Gigabit NICs connected to a
DELL managed switch with LACP setup.
My /etc/network/interfaces looks like:
auto bond0
iface bond0 inet static
address 10.145.15.20
netmask 255.255.255.0
gateway 10.145
** Changed in: ifenslave-2.6 (Ubuntu Lucid)
Assignee: Steve Langasek (vorlon) => Stéphane Graber (stgraber)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/482419
Title:
802.3ad interface bonding
Short followup to my previous comment #54. The workaround is
functioning well for me now. I think I had a typo in my first round of
testing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/482419
Titl
Unfortunately this workaround isn't as reliable as adding (the sloppier)
"/etc/init.d/networking restart" to my /etc/rc.local.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/482419
Title:
802.3ad int
speed/duplex auto-negotiation was not the source of the problem in my
experience (not saying that it couldn't potentially cause some problem).
Relying on auto-negotiation is not a good idea when using ether-channel.
What I found was that problem is originating from the udev (hotplug)
ethernet sys
@Pete Ashdown yes, there is a workaround.
First one of the things that goes wrong is that ethernet media
autoconfiguration takes up time and causes network interfaces to take so
long to come up there is the possibility that that will interfere with
bonding configuring. You can hardcode the media
Is there a workaround for this on 10.04.2? I'd rather that the bond
came up the first time so the subsequent network dependent daemons could
run properly rather than having to do a "/etc/init.d/networking restart"
in rc.local as suggested by the forum thread.
--
You received this bug notificatio
On Sat, Apr 23, 2011 at 01:23:30PM -, nutznboltz wrote:
> @Mark Favas - dude, it's not about fixing things, it's about declaring
> them fixed. Fiat bug fixes are what Canonical and the other
> Ubuntunistas do best.
Such false and slanderous comments have no place in bug reports. Take it
some
@Mark Favas - dude, it's not about fixing things, it's about declaring
them fixed. Fiat bug fixes are what Canonical and the other
Ubuntunistas do best.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/4
I can confirm that this bug still occurs. Although I've been using this
configuration for ~6 months, it bit me today. This is on a box running
Ubuntu server, with two bonded interfaces. Bond0 failed to come up after
a reboot, while bond1 did come up. After I got onto the box via bond1, a
reboot wor
Just confirming Neil Wilson's findings. I had the "no bond connection
upon reboot" issue and was using the non hot-plug configuration method.
I switched to hot-plug and the problem was sorted.
Description:Ubuntu 10.04.2 LTS
--- current config
# bond/trunk eth0-1
auto bond0
iface bond0 i
My symptoms are that interfaces are not brought up at boot. I have to manually:
1. stop networking
2. rmmod bonding
3. modprobe bonding
4. start networking
5. bring up all vlans one by one (ifup bond0.150x)
Once interfaces are up I do not have any problems with the network.
The history is that it
re #44, Michal, you're bridging together two VLANs -- beware, this will
cause most VLAN-aware switches to break down (as VLANs share one
forwarding database, and a MAC address can't appear on two ports; in my
experience this leads to intermittent very high packet loss as the
forwarding database sta
My configuration does not work - note that there is also a bridge set up
on two vlan interfaces.
# The loopback network interface
auto lo
iface lo inet loopback
auto bond0
iface bond0 inet manual
bond-slaves none
bond-mode 4
bond-miimon 100
# Internet
auto bond0.1501
ifac
Can you demonstrate the configuration to make it fail then.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/482419
Title:
802.3ad interface bonding fails if started too early
--
ubuntu-bugs mailing
The proposed patch from Bhavani is incorrect, but the bug as originally
described is real, is present even when using the hotplug configuration,
and should be backported to lucid. Setting this as 'triaged' again.
** Changed in: ifenslave-2.6 (Ubuntu Lucid)
Status: Incomplete => Triaged
**
As per current status, unsubscribing Ubuntu sponsors team. Please free
free to re-subscribe the team when the patch is ready for review and
upload. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
Setting to incomplete, see comment 35.
** Changed in: ifenslave-2.6 (Ubuntu Lucid)
Status: Triaged => Incomplete
--
802.3ad interface bonding fails if started too early
https://bugs.launchpad.net/bugs/482419
You received this bug notification because you are a member of Ubuntu
Bugs, which
I had the problem. I was going to sort the SRU.
Changing the configuration to the hotplug configuration fixed the
problem using the standard package.
Can you tell me what status I should use to get that checked by
everybody else?
On 15 November 2010 08:07, Steve Langasek wrote:
> I am sure this
I am sure this is a bug in the package. That's why it was marked
triaged.
** Changed in: ifenslave-2.6 (Ubuntu Lucid)
Status: Incomplete => Triaged
--
802.3ad interface bonding fails if started too early
https://bugs.launchpad.net/bugs/482419
You received this bug notification because yo
I'm no longer sure this is a bug in the package and may instead be more
of a duplicate of #559090. I cannot get the fault to replicate if I use
the correct hotplug configurations for the bonding system on a fresh
install of lucid with the vanilla lucid ifenslave-2.6 package.
All the posted configs
** Changed in: ifenslave-2.6 (Ubuntu Lucid)
Assignee: Neil Wilson (neil-aldur) => (unassigned)
** Changed in: ifenslave-2.6 (Ubuntu Lucid)
Status: Triaged => Incomplete
--
802.3ad interface bonding fails if started too early
https://bugs.launchpad.net/bugs/482419
You received this bu
** Changed in: ifenslave-2.6 (Ubuntu Lucid)
Assignee: (unassigned) => Neil Wilson (neil-aldur)
--
802.3ad interface bonding fails if started too early
https://bugs.launchpad.net/bugs/482419
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
Any chance we'll see this fix as part of the January 10.04.2 iso?
(Any chance Ubuntu LTS will have this fixed before CentOS 6 is out?)
(*ducks*)
--
802.3ad interface bonding fails if started too early
https://bugs.launchpad.net/bugs/482419
You received this bug notification because you are a mem
Bhavani,
this patch looks a bit weird. It not just changes the order of the
function calls, it also introduces a new function call "setup_slaves",
without any further changes. However, in the original Debian patch
(still visible at
http://launchpadlibrarian.net/49642996/ifenslave-2.6_1.1.0-14ubunt
** Description changed:
- 802.3ad bonding configurations that formerly worked on jaunty are now
- failing on startup under karmic. After the system has started,
- restarting networking will bring the bond up correctly. This only
- applies to bond_mode 4 / 802.3ad, I've tested that switching to
- b
I was hit by this bug, on multiple machines and architectures (x86,
x86_64). I installed the provisional version 1.1.0-15ubuntu1, from
comment #16, and the problems went away.
--
802.3ad interface bonding fails if started too early
https://bugs.launchpad.net/bugs/482419
You received this bug not
Somebody to execute the SRU process I'd imagine.
On 5 September 2010 05:49, Ryan Tandy <482...@bugs.launchpad.net> wrote:
> The patch supplied by Steve in comment #28 worked for me in a virtual
> machine and I will test it on a physical one when I get the chance. Is
> there anything holding up th
The patch supplied by Steve in comment #28 worked for me in a virtual
machine and I will test it on a physical one when I get the chance. Is
there anything holding up the release of this fixed package?
--
802.3ad interface bonding fails if started too early
https://bugs.launchpad.net/bugs/482419
Any chance we'll see this as part of the 10.04.1 iso?
--
802.3ad interface bonding fails if started too early
https://bugs.launchpad.net/bugs/482419
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs
here is the shortened patch
regards
** Patch added: "the lucid sru debdiff"
http://launchpadlibrarian.net/51964534/ifenslave-2.6-sru.diff
--
802.3ad interface bonding fails if started too early
https://bugs.launchpad.net/bugs/482419
You received this bug notification because you are a member
Okay steve!
Shortening the patch !
regards
On Thu, Jul 15, 2010 at 1:18 AM, Steve Langasek
wrote:
> Hi Bhavani,
>
> What dpkg trigger error are you trying to fix? The changes to the
> maintainer scripts should have no effect on dpkg triggers. In fact,
> they should have no effect in Ubuntu at
Hi Bhavani,
What dpkg trigger error are you trying to fix? The changes to the
maintainer scripts should have no effect on dpkg triggers. In fact,
they should have no effect in Ubuntu at all because the change only
applies to upgrades from version 1.1.0-6 or before, which is the version
that was
Hello steve, ubuntu-sru and others
Attached is the lucid SRU diff
Please test out the patch
regards
** Patch added: "the lucid SRU debdiff"
http://launchpadlibrarian.net/51917382/ifenslave-2.6-sru.diff
--
802.3ad interface bonding fails if started too early
https://bugs.launchpad.net/bugs/
yeah steve on it now
--
802.3ad interface bonding fails if started too early
https://bugs.launchpad.net/bugs/482419
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.u
unsubscribing ubuntu-sponsors. Please resubscribe the team once you have
a debdiff prepared.
--
802.3ad interface bonding fails if started too early
https://bugs.launchpad.net/bugs/482419
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
-
For an SRU we need a targeted backport of just the bugfix, without
taking changes that entirely redo the packaging. Bhavani, can you
prepare this or should I?
** Package changed: linux (Ubuntu) => ifenslave-2.6 (Ubuntu)
** Changed in: ifenslave-2.6 (Ubuntu)
Status: Confirmed => Fix Releas
This is confirmed as a failure within 10.04 LTS on boot.
I feel this is a critical bug that shouldn't be in an LTS and the
ifenslave package should be updated with the patch above.
I've added the ifenslave package above to my release archive at ppa
:neil-aldur/ppa
Please SRU Lucid, and look at S
Same isssue here on 10.04LTS.
Installed the package of Bhavani
(ifenslave-2.6_1.1.0-15ubuntu1_amd64.deb)
Bonding of 4 NICs (802.3ad) now works like a charm, even after a
restart. +1 for SRU!
--
802.3ad interface bonding fails if started too early
https://bugs.launchpad.net/bugs/482419
You recei
Maybe it's about the language. I'm testing to see if it makes a
difference if it's worded like LP: #552017
--
802.3ad interface bonding fails if started too early
https://bugs.launchpad.net/bugs/482419
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
Affected by this bug too.
With bhavi package the problem was negated. Please do SRU!
Thank you.
--
802.3ad interface bonding fails if started too early
https://bugs.launchpad.net/bugs/482419
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
Is this bug/fix eligible for an SRU?
https://wiki.ubuntu.com/StableReleaseUpdates
--
802.3ad interface bonding fails if started too early
https://bugs.launchpad.net/bugs/482419
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-
This package fixes things for me too... I've got two e1000's and two
bnx2's, they all work properly with this package.
--
802.3ad interface bonding fails if started too early
https://bugs.launchpad.net/bugs/482419
You received this bug notification because you are a member of Ubuntu
Bugs, which i
ifenslave-2.6_1.1.0-15ubuntu1_amd64.deb is working for me on this box:
$ sudo dmidecode | grep Prod
Product Name: SUN FIRE X4450
$ sudo dmidecode | grep Desc.*LAN
Description: LAN 1 of Gilgal (Intel 82563EB)
Description: LAN 2 of Gilgal (Intel 82563EB)
Descriptio
here is the built package
https://edge.launchpad.net/~bhavi/+archive/crickinfo/+build/1472211/+files/ifenslave-2.6_1.1.0-15ubuntu1_amd64.deb
https://edge.launchpad.net/~bhavi/+archive/crickinfo/+build/1472212/+files/ifenslave-2.6_1.1.0-15ubuntu1_i386.deb
and attached is the diff
** Patch added:
Thanks I ll prepare a diff against latest version in debian
Regards
** Changed in: linux (Ubuntu)
Status: Confirmed => In Progress
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Bhavani Shankar (bhavi)
--
802.3ad interface bonding fails if started too early
https://bugs.la
Some links about the ifenslave in Lucid vs. Karmic vs. Debian Sid
http://changelogs.ubuntu.com/changelogs/pool/main/i/ifenslave-2.6/ifenslave-2.6_1.1.0-14ubuntu1/changelog
Current package versions
Karmic 1.1.0-13ubuntu1 08-Jun-2009
Lucid 1.1.0-14ubuntu1 06-Nov-2009
Debian Sid 1.1.0-15 18-Dec-2009
Direct link to Debian ifenslave bug
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=558097
** Bug watch added: Debian Bug tracker #558097
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=558097
--
802.3ad interface bonding fails if started too early
https://bugs.launchpad.net/bugs/482419
Yo
that debug output looks the same, so i'd say yes.
2010/1/26 Scott Call :
> Is this possible same/related as Debian bug 588097 related to ifenslave-2.6?
> http://groups.google.com/group/linux.debian.bugs.dist/browse_thread/thread/9f05eea3b27339a6
>
> --
> 802.3ad interface bonding fails if started
Is this possible same/related as Debian bug 588097 related to ifenslave-2.6?
http://groups.google.com/group/linux.debian.bugs.dist/browse_thread/thread/9f05eea3b27339a6
--
802.3ad interface bonding fails if started too early
https://bugs.launchpad.net/bugs/482419
You received this bug notificat
i'm seeing this on karmic with 2.6.31-16-server with Broadcom
Corporation NetXtreme BCM5721 cards. Is a blocker for me, i can't
restart networking on each server after booting..
--
802.3ad interface bonding fails if started too early
https://bugs.launchpad.net/bugs/482419
You received this bug no
** Tags added: karmic
** Tags removed: kernel-series-unknown
--
802.3ad interface bonding fails if started too early
https://bugs.launchpad.net/bugs/482419
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubun
Ahhh yes, that shows "active-backup 1", which is what I'd expect for
configuring with mode 1.
--
802.3ad interface bonding fails if started too early
https://bugs.launchpad.net/bugs/482419
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
On Fri, Dec 4, 2009 at 2:49 PM, Graeme Humphries wrote:
> Oh, you're right, this might be a different issue.
> /sys/class/net/bond0/link_mode shows "0", even though the device in
> /etc/network/interfaces is configured with "bond-mode 1". And I'm not
> seeing the "unintialized port" errors anymore
Oh, you're right, this might be a different issue.
/sys/class/net/bond0/link_mode shows "0", even though the device in
/etc/network/interfaces is configured with "bond-mode 1". And I'm not
seeing the "unintialized port" errors anymore, but it still fails to
come up when initially started, I have to
On Fri, Dec 4, 2009 at 11:28 AM, Graeme Humphries wrote:
> Just switched my karmic config to "mode 1", and I'm still seeing this
> issue, so it isn't limited to strict 802.3ad mode (4).
Are you sure the system is using bonding mode 1? What does 'cat
/sys/class/net/bond0/link_mode' display?
The "
Just switched my karmic config to "mode 1", and I'm still seeing this
issue, so it isn't limited to strict 802.3ad mode (4).
--
802.3ad interface bonding fails if started too early
https://bugs.launchpad.net/bugs/482419
You received this bug notification because you are a member of Ubuntu
Bugs, w
I'm also seeing this running On a Penguin Relion 2612, using the
forcedeth gigabit ethernet driver, bonding eth0 and eth1 with bond-mode
4. Also, I'm running a vlan setup on top of the bonded driver.
I can generally get the setup to work by hand, although seemingly not
with a mere "/etc/init.d/ne
** Tags added: kernel-series-unknown
--
802.3ad interface bonding fails if started too early
https://bugs.launchpad.net/bugs/482419
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Seeing this on a Supermicro server system, motherboard X8STi, with dual
e1000e NICs.
--
802.3ad interface bonding fails if started too early
https://bugs.launchpad.net/bugs/482419
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubunt
Marking medium. While there is a function workaround, it requires access
to the console on startup. Since this configuration is most often see in
a server environment, this is makes the workaround less practical and
thus more severe.
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
I'm also seeing this with e1000e driver on an intel s5000psl motherboard
iface bond0 inet dhcp
slaves eth0 eth1
bond-mode 4
bond-miimon 10
bond-lacp-rate fast
bond-xmit_hash_policy layer2+3
after boot up
/proc/net/bonding/bond0 has
MII Status: down
i can
80 matches
Mail list logo
