From: Ben Hutchings <ben@decadent.org.uk>
To: netdev <netdev@vger.kernel.org>
Cc: Bastian Blank <waldi@debian.org>,
697357@bugs.debian.org, Peter Palfrader <weasel@debian.org>,
Stephen Hemminger <shemminger@vyatta.com>,
Jay Vosburgh <fubar@us.ibm.com>,
Andy Gospodarek <andy@greyhouse.net>
Subject: Re: Bug#697357: bridging broken over bond interfaces
Date: Mon, 07 Jan 2013 04:58:24 +0000 [thread overview]
Message-ID: <1357534704.26822.6.camel@deadeye.wl.decadent.org.uk> (raw)
In-Reply-To: <20130104124012.GH14827@anguilla.noreply.org>
[-- Attachment #1: Type: text/plain, Size: 2384 bytes --]
Forwarding this to netdev since the bug is still present in Linux 3.7.1.
For those joining us, this thread is archive at
<http://bugs.debian.org/697357>.
On Fri, 2013-01-04 at 13:40 +0100, Peter Palfrader wrote:
> On Fri, 04 Jan 2013, Bastian Blank wrote:
>
> > On Fri, Jan 04, 2013 at 12:17:12PM +0100, Peter Palfrader wrote:
> > > I tried to set up a new KVM host in the usual way:
> > > - have a bond0 interface over all physcial eth* interfaces
> > > - create a br0 over that bond0 and any vnet* interfaces for the
> > > guests.
>
> Also, arp works through the bridge, forgot to mention that.
>
> > > * Manually switching the eth* to promiscious mode makes stuff work.
> >
> > Okay, so a workaround is available.
> >
> > When did it last work? Does it work with the kernel from experimental?
>
> It works nicely on stable, e.g. pasquini.debian.org:
>
> | weasel@pasquini:~$ sudo brctl show
> | bridge name bridge id STP enabled interfaces
> | br0 8000.e83935a9ec10 no bond0
> | tap0
> | tap1
> | tap2
> | br1 8000.e83935a9ec10 no bond0.221
> | br2 8000.da1343affe92 no bond0.3301
> | tap3
>
> And there the bond interface is promisc automatically:
> weasel@pasquini:~$ ip a | grep -i bond
> | 2: eth0: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master bond0 state UP qlen 1000
> | 3: eth1: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master bond0 state UP qlen 1000
> | 4: bond0: <BROADCAST,MULTICAST,PROMISC,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP
> | 7: bond0.221@bond0: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP
> | 9: bond0.3301@bond0: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP
>
> Likewise it works as expected when one does br directly on eth0, without any
> bonding.
>
> It's also broken with linux-image-3.7-trunk-amd64_3.7.1-1~experimental.1_amd64.deb.
--
Ben Hutchings
If you seem to know what you are doing, you'll be given more to do.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next parent reply other threads:[~2013-01-07 4:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20130104111712.25539.62770.reportbug@valiant.palfrader.org>
[not found] ` <20130104114407.GA303@waldi.eu.org>
[not found] ` <20130104124012.GH14827@anguilla.noreply.org>
2013-01-07 4:58 ` Ben Hutchings [this message]
2013-01-22 20:20 ` Bug#697357: bridging broken over bond interfaces Ferenc Wagner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1357534704.26822.6.camel@deadeye.wl.decadent.org.uk \
--to=ben@decadent.org.uk \
--cc=697357@bugs.debian.org \
--cc=andy@greyhouse.net \
--cc=fubar@us.ibm.com \
--cc=netdev@vger.kernel.org \
--cc=shemminger@vyatta.com \
--cc=waldi@debian.org \
--cc=weasel@debian.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox