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: Mon, 7 Feb 2011 18:24:45 -0800 [thread overview]
Message-ID: <AANLkTinJ3ga46FfvPJCnxSH129mSC2TCdPRSXwu+iiJo@mail.gmail.com> (raw)
In-Reply-To: <loom.20110206T203347-475@post.gmane.org>
On Sun, Feb 6, 2011 at 11:37 AM, chriss <mail_to_chriss@gmx.net> wrote:
> Jesse Gross <jesse <at> nicira.com> writes:
>
>>
>> You should either attached a bridge to a vlan device or stack a vlan
>> device on the bridge port depending on what you are trying to achieve.
>>
>> The bridge handler takes all packets of the device that it is attached
>> to, so having a vlan also attached to the same device will not work.
>> You may get different results on older kernels depending on what NIC
>> you were using but that was a bug.
>> --
>> To unsubscribe from this list: send the line "unsubscribe netdev" in
>> the body of a message to majordomo <at> vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>
>>
>
>
> Hi and thanks for your reply
>
> I tried that.
>
> I had under 2.6.36.3 following combination:
>
> eth1 in br0 -> all traffic without vlan id
> eth1.3 -> traffic with vlan 3
>
> with 2.6.37 i should do the following
> eth1 in br0 -> traffic w/o vlans
> and br0.3 -> traffic with vlan id 3
>
> But still there is no rx for vlan 3.
> Any suggestions? Or am i missing something?
That configuration should work (and I've tested it in the past). I
would try running tcpdump on the various interfaces in the path (eth1,
br0, br0.3) to see where traffic is flowing or not.
prev parent reply other threads:[~2011-02-08 2:24 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
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 [this message]
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=AANLkTinJ3ga46FfvPJCnxSH129mSC2TCdPRSXwu+iiJo@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).