netdev - Re: 2.6.37 regression: adding main interface to a bridge breaks vlan interface RX

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 28 Feb 2011 13:37:34 -0800
From:	Jesse Gross <jesse@...ira.com>
To:	chriss <mail_to_chriss@....net>,
	Francois Romieu <romieu@...zoreil.com>
Cc:	netdev@...r.kernel.org
Subject: Re: 2.6.37 regression: adding main interface to a bridge breaks vlan
 interface RX

On Sat, Feb 26, 2011 at 3:51 AM, chriss <mail_to_chriss@....net> wrote:
> Jesse Gross <jesse <at> nicira.com> writes:
>
>>
>> Can you confirm this by running tcpdump -eni br0?  I would expect that
>> you see the correct packets but without vlan tags.
>>
>
> Thats correct. i see the packets in br0 without tags and tagged in eth1. thats
> why i added the brouting rule in ebtables to drop it at eth1 and the it apears
> in eth1.3 (untagged)...

Putting a vlan device on eth1 actually affects the behavior of the
driver, which is why that works.  I suspect that if you put the vlan
device on both the physical interface and the bridge you would see
packets with tags on the bridge.

Regardless, the solution is to remove the dependency on vlan devices
by converting over to the new vlan model.  Francois, any chance that
you might have some time to look at this?
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html