From: Stephen Hemminger <shemminger@vyatta.com>
To: Ross Vandegrift <ross@kallisti.us>
Cc: bridge@lists.linux-foundation.org
Subject: Re: [Bridge] Re :Re: Re :Re: Bridging LACP (802.3ad) frames not working
Date: Tue, 12 Jan 2010 16:40:53 -0800 [thread overview]
Message-ID: <20100112164053.2447c8f2@nehalam> (raw)
In-Reply-To: <20100112220448.GF23219@kallisti.us>
On Tue, 12 Jan 2010 17:04:48 -0500
Ross Vandegrift <ross@kallisti.us> wrote:
> On Tue, Jan 12, 2010 at 09:40:30PM +0000, jhautbois@gmail.com wrote:
> > This is exactly the problem.
> > But, sounds like it is not possible... ?
>
> You could run a custom version of the bridge driver to enable bridging
> of frames sent to the bridge-management MAC addresses. Some folks
> have talked about doing similar things to enable bridging of STP.
>
> Doing that with STP makes a bit more sense to me (since there are
> valid networks that could be constructed that way). But you'll be
> breaking a pretty fundamental assumption of LACP....
Recent kernels will forward link local frames as long as STP is disabled.
Older kernels will not.
The assumption is that if STP is enabled, then it will be managing
control plane.
Author: Stephen Hemminger <shemminger@vyatta.com> 2009-05-14 23:10:13
Committer: David S. Miller <davem@davemloft.net> 2009-05-17 21:12:54
Parent: 43aa1920117801fe9ae3d1fad886b62511e09bee (bridge: handle process all link-local frames)
Branches: master, remotes/origin/master
Follows: v2.6.30-rc6
Precedes: v2.6.30-rc7
bridge: relay bridge multicast pkgs if !STP
Currently the bridge catches all STP packets; even if STP is turned
off. This prevents other systems (which do have STP turned on)
from being able to detect loops in the network.
With this patch, if STP is off, then any packet sent to the STP
multicast group address is forwarded to all ports.
Based on earlier patch by Joakim Tjernlund with changes
to go through forwarding (not local chain), and optimization
that only last octet needs to be checked.
Signed-off-by: Stephen Hemminger <shemminger@vyatta.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
--
next prev parent reply other threads:[~2010-01-13 0:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-12 15:13 [Bridge] Bridging LACP (802.3ad) frames not working Jean-Michel Hautbois
2010-01-12 15:23 ` Ross Vandegrift
2010-01-12 15:28 ` [Bridge] Re :Re: " jhautbois
2010-01-12 21:32 ` Ross Vandegrift
2010-01-12 21:40 ` [Bridge] Re :Re: " jhautbois
2010-01-12 22:04 ` Ross Vandegrift
2010-01-13 0:40 ` Stephen Hemminger [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-01-12 22:58 richardvoigt
2010-01-13 9:26 ` Jean-Michel Hautbois
2010-01-13 10:29 Jean-Michel Hautbois
2010-01-13 16:30 ` Stephen Hemminger
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=20100112164053.2447c8f2@nehalam \
--to=shemminger@vyatta.com \
--cc=bridge@lists.linux-foundation.org \
--cc=ross@kallisti.us \
/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