| 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
| ||
|
Message-ID: <loom.20110206T203347-475@post.gmane.org> Date: Sun, 6 Feb 2011 19:37:41 +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 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? regards -- 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
Powered by blists - more mailing lists