From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: <20100113085500.554ba62c@nehalam> References: <8cad0aa1001130853i38d35b5ft7cd23b749ae891ce@mail.gmail.com> <20100113085500.554ba62c@nehalam> Date: Wed, 13 Jan 2010 18:21:40 +0100 Message-ID: <8cad0aa1001130921v7d3b1f90ua3c0491737181a09@mail.gmail.com> From: Jean-Michel Hautbois Content-Type: text/plain; charset=ISO-8859-1 Subject: Re: [Bridge] Re :Re: Re :Re: Re :Re: Bridging LACP (802.3ad) frames not working List-Id: Linux Ethernet Bridging List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Stephen Hemminger Cc: bridge@lists.linux-foundation.org 2010/1/13 Stephen Hemminger : > On Wed, 13 Jan 2010 17:53:10 +0100 > Jean-Michel Hautbois wrote: > >> 2010/1/13 Stephen Hemminger : >> > On Wed, 13 Jan 2010 16:47:14 +0000 >> > jhautbois@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