netdev - Re: [PATCH v2 net 0/3] bridge: Add vlan filtering support for default pvid

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:	Tue, 30 Sep 2014 19:16:19 -0400
From:	Vlad Yasevich <vyasevic@...hat.com>
To:	David Miller <davem@...emloft.net>, vyasevich@...il.com
CC:	netdev@...r.kernel.org, toshiaki.makita1@...il.com,
	stephen@...workplumber.org, bridge@...ts.linux-foundation.org
Subject: Re: [PATCH v2 net 0/3] bridge: Add vlan filtering support for default
 pvid

On 09/30/2014 05:07 PM, David Miller wrote:
> From: Vladislav Yasevich <vyasevich@...il.com>
> Date: Tue, 30 Sep 2014 15:30:59 -0400
> 
>> Version 2 of the series to introduce the default pvid support to
>> vlan filtering in the bridge.  VLAN 1 (as recommended by 802.1q spec)
>> is used as default pvid on ports. 
>> The the user can over-ride this configuration by configuring their
>> own vlan information. 
>> The user can additionally change the default value throught the
>> sysfs interface (netlink comming shortly).
>> The user can turn off default pvid functionality by setting default
>> pvid to 0. 
>> This series changes the default behavior of the bridge when
>> vlan filtering is turned on.  Currently, ports without any vlan
>> filtering configured will not recevie any traffic at all.  This patch
>> changes the behavior of the above ports to receive only untagged traffic.
>>
>> Since v2:
>> - Add ability to turn off default_pvid settings.
>> - Drop the automiatic filtering support based on configured vlan devices (will
>>   be its own series)
> 
> Looks like a new feature to me, thus why is this being targetted at 'net'
> instead of 'net-next'?
> 

goof on my part.  This should be net-next.

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