From: Jean-Michel Hautbois <jhautbois@gmail.com>
To: Stephen Hemminger <shemminger@vyatta.com>
Cc: bridge@lists.linux-foundation.org
Subject: Re: [Bridge] Re :Re: Re :Re: Re :Re: Bridging LACP (802.3ad) frames not working
Date: Wed, 13 Jan 2010 17:53:10 +0100 [thread overview]
Message-ID: <8cad0aa1001130853i38d35b5ft7cd23b749ae891ce@mail.gmail.com> (raw)
2010/1/13 Stephen Hemminger <shemminger@vyatta.com>:
> 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...
JM
next reply other threads:[~2010-01-13 16:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-13 16:53 Jean-Michel Hautbois [this message]
2010-01-13 16:55 ` [Bridge] Re :Re: Re :Re: Re :Re: Bridging LACP (802.3ad) frames not working Stephen Hemminger
2010-01-13 17:21 ` Jean-Michel Hautbois
2010-01-13 17:42 ` Jean-Michel Hautbois
-- strict thread matches above, loose matches on Subject: below --
2010-01-19 19:44 yavetskiy
2010-01-20 16:31 ` Yavetskiy Yuriy
2010-01-20 17:54 ` Stephen Hemminger
2010-01-20 18:14 ` Jean-Michel Hautbois
2010-03-18 9:06 ` Phil Karn
2010-01-13 16:30 [Bridge] " Stephen Hemminger
2010-01-13 16:47 ` [Bridge] Re :Re: " jhautbois
2010-01-13 16:49 ` Stephen Hemminger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8cad0aa1001130853i38d35b5ft7cd23b749ae891ce@mail.gmail.com \
--to=jhautbois@gmail.com \
--cc=bridge@lists.linux-foundation.org \
--cc=shemminger@vyatta.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).