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]

Message-ID: <loom.20110214T141934-88@post.gmane.org>
Date:	Mon, 14 Feb 2011 13:22:55 +0000 (UTC)
From:	chriss <mail_to_chriss@....net>
To:	netdev@...r.kernel.org
Subject: Re: 2.6.37 regression: adding main interface to a bridge breaks vlan interface RX

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?!

Thanks nicolas

regards//chriss

--
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