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

Jean-Michel Hautbois jhautbois at gmail.com
Wed Jan 13 09:21:40 PST 2010


2010/1/13 Stephen Hemminger <shemminger at vyatta.com>:
> On Wed, 13 Jan 2010 17:53:10 +0100
> Jean-Michel Hautbois <jhautbois at gmail.com> wrote:
>
>> 2010/1/13 Stephen Hemminger <shemminger at vyatta.com>:
>> > On Wed, 13 Jan 2010 16:47:14 +0000
>> > jhautbois at gmail.com wrote:
>> >
>> >> (snip)
>> >> > I meant they get processed locally, before that they were dropped.
>> >>
>> >> > The best solution is to write an ebtables rule to forward them.
>> >>
>> >> Mmh, I can understand that, but I can't see which kind of rule would do
>> >> that.
>> >> Something like :
>> >> ebtables -A FORWARDING -p 0x8809 -j ACCEPT ??
>> >>
>> >> But I think this will not do anything, because it is forwarding by default.
>> >> Or there is something I can't see :-).
>> >>
>> >
>> > You need to put the rule on the local input not forwarding chain.
>> >
>>
>> You mean :
>> ebtables -A INPUT -p 0x8809 -j ACCEPT ?
>>
>> According to my understanding of this graph :
>> http://ebtables.sourceforge.net/br_fw_ia/PacketFlow.png
>> I can't understand why it has to be in the INPUT...
>
> Because bridge input processing puts all link local packets to
> the local input path.
>

It is not working.
I am sending LACP packets through a link, it arrives on my first
interface, I can see it (with wireshark) in my bridge, but when I am
just adding the rule (ebtables -A INPUT -p 0x8809 -j ACCEPT) it is not
going to my second interface...

JM


More information about the Bridge mailing list