| 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
| ||
|
Date: Sun, 6 Feb 2011 10:09:57 -0800 From: Jesse Gross <jesse@...ira.com> To: chriss <mail_to_chriss@....net> Cc: netdev@...r.kernel.org Subject: Re: 2.6.37 regression: adding main interface to a bridge breaks vlan interface RX On Sat, Feb 5, 2011 at 7:34 AM, chriss <mail_to_chriss@....net> wrote: > Maciej Rutecki <maciej.rutecki <at> gmail.com> writes: > >> >> On niedziela, 23 stycznia 2011 o 22:29:02 Jesse Gross wrote: >> > On Sun, Jan 23, 2011 at 9:45 AM, Maciej Rutecki >> > >> > <maciej.rutecki <at> gmail.com> wrote: >> > > I created a Bugzilla entry at >> > > https://bugzilla.kernel.org/show_bug.cgi?id=27432 >> > > for your bug report, please add your address to the CC list in there, >> > > thanks! >> > >> > This isn't a bug - the change resolved behavior that varied depending >> > on what NIC was in use. >> >> Thanks for the update. Closing. >> >> Regards > > > Hi > > How am i supposed to put my eth to a bridge and have a seprate vlan besides that > bridge? 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@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists