[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20120824134410.75827e0d@nehalam.linuxnetplumber.net>
Date: Fri, 24 Aug 2012 13:44:10 -0700
From: Stephen Hemminger <shemminger@...tta.com>
To: vyasevic@...hat.com
Cc: Nicolas de Pesloüan
<nicolas.2p.debian@...il.com>, netdev@...r.kernel.org
Subject: Re: [RFC PATCH bridge 0/5] Add basic VLAN support to bridges
On Thu, 23 Aug 2012 22:52:02 -0400
Vlad Yasevich <vyasevic@...hat.com> wrote:
> 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.
The vlan map table would be helpful, but the Spanning Tree implementation
doesn't have a clue about what it means.
--
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