From mboxrd@z Thu Jan 1 00:00:00 1970 From: Vlad Yasevich Subject: Re: [RFC PATCH bridge 0/5] Add basic VLAN support to bridges Date: Thu, 23 Aug 2012 22:52:02 -0400 Message-ID: <5036EC52.9090406@redhat.com> References: <1345750195-31598-1-git-send-email-vyasevic@redhat.com> <50369A99.2070405@gmail.com> Reply-To: vyasevic@redhat.com Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: netdev@vger.kernel.org, Stephen Hemminger To: =?UTF-8?B?Tmljb2xhcyBkZSBQZXNsb8O8YW4=?= Return-path: Received: from mx1.redhat.com ([209.132.183.28]:2461 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751052Ab2HXCwF (ORCPT ); Thu, 23 Aug 2012 22:52:05 -0400 In-Reply-To: <50369A99.2070405@gmail.com> Sender: netdev-owner@vger.kernel.org List-ID: On 08/23/2012 05:03 PM, Nicolas de Peslo=C3=BCan wrote: > Le 23/08/2012 21:29, Vlad Yasevich a =C3=A9crit : >> This series of patches provides an ability to add VLAN IDs to the br= idge >> 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 adde= d >> to FDB >> entries and become part of the lookup. This way we correctly identi= fy >> 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 w= e >> should >> persue. >> > > Do you think this might allow for per VLAN spanning tree (having port= s > in forwarding state or blocking state depending on the VLAN) in the f= uture? > > Nicolas. sure, why not. -vlad