From: Jesse Gross <jesse@nicira.com>
To: chriss <mail_to_chriss@gmx.net>
Cc: netdev@vger.kernel.org
Subject: Re: 2.6.37 regression: adding main interface to a bridge breaks vlan interface RX
Date: Fri, 25 Feb 2011 14:57:04 -0800 [thread overview]
Message-ID: <AANLkTimFC5drwt44C7Hpn4YJU-Njksr8Zkiv_RXK_oSL@mail.gmail.com> (raw)
In-Reply-To: <loom.20110214T141934-88@post.gmane.org>
On Mon, Feb 14, 2011 at 5:22 AM, chriss <mail_to_chriss@gmx.net> wrote:
> Nicolas de Pesloüan <nicolas.2p.debian <at> gmail.com> writes:
>
>> I think you should have a look at ebtables command, in particular, the
> BROUTING chain of broute
>> table. If this chain ask the packet to be dropped, then bridge will ignore it
> and give a chance to
>> the upper layer to use it. Upper layer might be IP, or in your particular
> setup, VLAN.
>>
>> HTH,
>>
>> Nicolas.
>
> Thank you very much for the ebtables hint.
>
> I also tried to add the vlan to my bridge device but only droping the vlan
> tagged paket with ebtables got it working.
>
> I'm not sure if this is the wanted behavior for bridging vlan actions.
> ..or my network setup is just to ..f%%%'ed up?!
What driver is in use with the NIC you are seeing this on?
next prev parent reply other threads:[~2011-02-25 22:57 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-16 14:09 2.6.37 regression: adding main interface to a bridge breaks vlan interface RX Simon Arlott
2011-01-17 16:00 ` Ben Hutchings
2011-01-17 18:17 ` Simon Arlott
2011-01-19 16:26 ` Jesse Gross
2011-01-23 17:45 ` Maciej Rutecki
2011-01-23 21:29 ` Jesse Gross
2011-01-24 15:25 ` Maciej Rutecki
2011-02-05 15:34 ` chriss
2011-02-06 18:09 ` Jesse Gross
2011-02-06 19:37 ` chriss
2011-02-07 12:09 ` Nicolas de Pesloüan
2011-02-14 13:22 ` chriss
2011-02-23 1:35 ` Jesse Gross
2011-02-25 22:57 ` Jesse Gross [this message]
2011-02-26 0:16 ` chriss
2011-02-26 1:08 ` Jesse Gross
2011-02-26 11:51 ` chriss
2011-02-28 21:37 ` Jesse Gross
2011-03-01 10:16 ` Francois Romieu
2011-03-01 20:04 ` Jesse Gross
2011-03-01 21:52 ` Francois Romieu
2011-03-04 19:32 ` chriss
2011-03-04 22:41 ` Francois Romieu
2011-03-05 10:53 ` chriss
2011-02-08 2:24 ` Jesse Gross
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=AANLkTimFC5drwt44C7Hpn4YJU-Njksr8Zkiv_RXK_oSL@mail.gmail.com \
--to=jesse@nicira.com \
--cc=mail_to_chriss@gmx.net \
--cc=netdev@vger.kernel.org \
/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).