[Bridge] Re :Re: Re :Re: Bridging LACP (802.3ad) frames not working
shemminger at vyatta.com
Tue Jan 12 16:40:53 PST 2010
On Tue, 12 Jan 2010 17:04:48 -0500
Ross Vandegrift <ross at kallisti.us> wrote:
> On Tue, Jan 12, 2010 at 09:40:30PM +0000, jhautbois at 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
Author: Stephen Hemminger <shemminger at vyatta.com> 2009-05-14 23:10:13
Committer: David S. Miller <davem at davemloft.net> 2009-05-17 21:12:54
Parent: 43aa1920117801fe9ae3d1fad886b62511e09bee (bridge: handle process all link-local frames)
Branches: master, remotes/origin/master
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 at vyatta.com>
Signed-off-by: David S. Miller <davem at davemloft.net>
More information about the Bridge