[Bridge] Re :Re: Re :Re: Bridging LACP (802.3ad) frames not working

Stephen Hemminger shemminger at vyatta.com
Wed Jan 13 08:30:58 PST 2010


On Wed, 13 Jan 2010 11:29:55 +0100
Jean-Michel Hautbois <jhautbois at gmail.com> wrote:

> 2010/1/13 Stephen Hemminger <shemminger at vyatta.com>:
> > 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
> > control plane.
> 
> Well, I have a 2.6.31 kernel. And LACP is not forwarded, even when STP
> is disabled.
> I don't understand what you mean ?

I meant they get processed locally, before that they were dropped.

The best solution is to write an ebtables rule to forward them.


More information about the Bridge mailing list