From: Stephen Hemminger <stephen@networkplumber.org>
To: Vlad Yasevich <vyasevic@redhat.com>
Cc: netdev@vger.kernel.org, bridge@lists.linux-foundation.org,
davem@davemloft.net
Subject: Re: [Bridge] [PATCH v9 net-next 00/12] Add basic VLAN support to bridges
Date: Mon, 4 Feb 2013 08:24:09 -0800 [thread overview]
Message-ID: <20130204082409.422ba135@nehalam.linuxnetplumber.net> (raw)
In-Reply-To: <1359748930-31475-1-git-send-email-vyasevic@redhat.com>
One thing I am not clear about is whether is supposed to be just
a simple filter of VLAN traffic, or a full VLAN aware bridge.
The change to make FDB entries per-VLAN seems to be the biggest tipping
point into a full VLAN bridge. I am concerned that might break existing
API's and Spanning Tree (internal and external).
WARNING: multiple messages have this Message-ID (diff)
From: Stephen Hemminger <stephen@networkplumber.org>
To: Vlad Yasevich <vyasevic@redhat.com>
Cc: bridge@lists.linux-foundation.org, davem@davemloft.net,
netdev@vger.kernel.org
Subject: Re: [PATCH v9 net-next 00/12] Add basic VLAN support to bridges
Date: Mon, 4 Feb 2013 08:24:09 -0800 [thread overview]
Message-ID: <20130204082409.422ba135@nehalam.linuxnetplumber.net> (raw)
In-Reply-To: <1359748930-31475-1-git-send-email-vyasevic@redhat.com>
One thing I am not clear about is whether is supposed to be just
a simple filter of VLAN traffic, or a full VLAN aware bridge.
The change to make FDB entries per-VLAN seems to be the biggest tipping
point into a full VLAN bridge. I am concerned that might break existing
API's and Spanning Tree (internal and external).
next prev parent reply other threads:[~2013-02-04 16:24 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-01 20:01 [Bridge] [PATCH v9 net-next 00/12] Add basic VLAN support to bridges Vlad Yasevich
2013-02-01 20:01 ` Vlad Yasevich
2013-02-01 20:01 ` [Bridge] [PATCH v9 net-next 01/12] bridge: Add vlan filtering infrastructure Vlad Yasevich
2013-02-01 20:01 ` Vlad Yasevich
2013-02-02 1:04 ` [Bridge] " Michał Mirosław
2013-02-02 1:04 ` Michał Mirosław
2013-02-02 2:11 ` [Bridge] " Vlad Yasevich
2013-02-02 2:11 ` Vlad Yasevich
2013-02-01 20:02 ` [Bridge] [PATCH v9 net-next 02/12] bridge: Validate that vlan is permitted on ingress Vlad Yasevich
2013-02-01 20:02 ` Vlad Yasevich
2013-02-02 1:04 ` [Bridge] " Michał Mirosław
2013-02-02 1:04 ` Michał Mirosław
2013-02-02 2:13 ` [Bridge] " Vlad Yasevich
2013-02-02 2:13 ` Vlad Yasevich
2013-02-01 20:02 ` [Bridge] [PATCH v9 net-next 03/12] bridge: Verify that a vlan is allowed to egress on give port Vlad Yasevich
2013-02-01 20:02 ` Vlad Yasevich
2013-02-01 20:02 ` [Bridge] [PATCH v9 net-next 04/12] bridge: Add netlink interface to configure vlans on bridge ports Vlad Yasevich
2013-02-01 20:02 ` Vlad Yasevich
2013-02-01 20:02 ` [Bridge] [PATCH v9 net-next 05/12] bridge: Add the ability to configure pvid Vlad Yasevich
2013-02-01 20:02 ` Vlad Yasevich
2013-02-02 1:04 ` [Bridge] " Michał Mirosław
2013-02-02 1:04 ` Michał Mirosław
2013-02-02 1:15 ` [Bridge] " Michał Mirosław
2013-02-02 1:15 ` Michał Mirosław
2013-02-02 2:22 ` [Bridge] " Vlad Yasevich
2013-02-02 2:22 ` Vlad Yasevich
2013-02-03 14:49 ` [Bridge] " Michał Mirosław
2013-02-03 14:49 ` Michał Mirosław
2013-02-03 15:20 ` [Bridge] " Michał Mirosław
2013-02-03 15:20 ` Michał Mirosław
2013-02-04 16:59 ` [Bridge] " Vlad Yasevich
2013-02-04 16:59 ` Vlad Yasevich
2013-02-01 20:02 ` [Bridge] [PATCH v9 net-next 06/12] bridge: Implement vlan ingress/egress policy Vlad Yasevich
2013-02-01 20:02 ` Vlad Yasevich
2013-02-01 20:02 ` [Bridge] [PATCH v9 net-next 07/12] bridge: Add vlan to unicast fdb entries Vlad Yasevich
2013-02-01 20:02 ` Vlad Yasevich
2013-02-01 20:02 ` [Bridge] [PATCH v9 net-next 08/12] bridge: Add vlan id to multicast groups Vlad Yasevich
2013-02-01 20:02 ` Vlad Yasevich
2013-02-01 20:02 ` [Bridge] [PATCH v9 net-next 09/12] bridge: Add vlan support to static neighbors Vlad Yasevich
2013-02-01 20:02 ` Vlad Yasevich
2013-02-01 20:02 ` [Bridge] [PATCH v9 net-next 10/12] bridge: Add vlan support for local fdb entries Vlad Yasevich
2013-02-01 20:02 ` Vlad Yasevich
2013-02-01 20:02 ` [Bridge] [PATCH v9 net-next 11/12] bridge: Dump vlan information from a bridge port Vlad Yasevich
2013-02-01 20:02 ` Vlad Yasevich
2013-02-01 20:02 ` [Bridge] [PATCH v9 net-next 12/12] bridge: Separate egress policy bitmap Vlad Yasevich
2013-02-01 20:02 ` Vlad Yasevich
2013-02-04 16:24 ` Stephen Hemminger [this message]
2013-02-04 16:24 ` [PATCH v9 net-next 00/12] Add basic VLAN support to bridges Stephen Hemminger
2013-02-04 16:58 ` [Bridge] " Vlad Yasevich
2013-02-04 16:58 ` Vlad Yasevich
2013-02-07 22:48 ` [Bridge] " Vlad Yasevich
2013-02-07 22:48 ` Vlad Yasevich
2013-02-07 22:57 ` [Bridge] " Stephen Hemminger
2013-02-07 22:57 ` Stephen Hemminger
2013-02-07 23:00 ` [Bridge] " Vlad Yasevich
2013-02-07 23:00 ` Vlad Yasevich
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130204082409.422ba135@nehalam.linuxnetplumber.net \
--to=stephen@networkplumber.org \
--cc=bridge@lists.linux-foundation.org \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=vyasevic@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.