From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Wed, 13 Jan 2010 08:55:00 -0800 From: Stephen Hemminger Message-ID: <20100113085500.554ba62c@nehalam> In-Reply-To: <8cad0aa1001130853i38d35b5ft7cd23b749ae891ce@mail.gmail.com> References: <8cad0aa1001130853i38d35b5ft7cd23b749ae891ce@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit 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: Jean-Michel Hautbois Cc: bridge@lists.linux-foundation.org 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.