netdev - Re: [RFC PATCH bridge 0/5] Add basic VLAN support to bridges

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:	Thu, 23 Aug 2012 22:52:02 -0400
From:	Vlad Yasevich <vyasevic@...hat.com>
To:	Nicolas de Pesloüan 
	<nicolas.2p.debian@...il.com>
CC:	netdev@...r.kernel.org, Stephen Hemminger <shemminger@...tta.com>
Subject: Re: [RFC PATCH bridge 0/5] Add basic VLAN support to bridges

On 08/23/2012 05:03 PM, Nicolas de Pesloüan wrote:
> Le 23/08/2012 21:29, Vlad Yasevich a écrit :
>> This series of patches provides an ability to add VLAN IDs to the bridge
>> ports.  This is similar to what can be found in most switches.  The
>> bridge
>> port may have any number of VLANs added to it including vlan 0 for
>> untagged
>> traffic.  When vlans are added to the port, only traffic tagged with
>> particular
>> vlan will forwarded over this port.  Additionally, vlan ids are added
>> to FDB
>> entries and become part of the lookup.  This way we correctly identify
>> the FDB
>> entry.
>>
>> There are still pieces missing.  I don't yet support adding a static
>> fdb entry
>> with a particular vlan.  There is no netlink support for carrying a
>> vlan id.
>>
>> I'd like to hear thoughts of whether this is usufull and something we
>> should
>> persue.
>>
>
> Do you think this might allow for per VLAN spanning tree (having ports
> in forwarding state or blocking state depending on the VLAN) in the future?
>
>      Nicolas.

sure, why not.

-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