From: David Miller <davem@davemloft.net>
To: makita.toshiaki@lab.ntt.co.jp
Cc: stephen@networkplumber.org, vyasevic@redhat.com,
netdev@vger.kernel.org, bridge@lists.linux-foundation.org
Subject: Re: [PATCH v2 net-next 0/4] bridge: 802.1ad vlan protocol support
Date: Wed, 11 Jun 2014 15:23:21 -0700 (PDT) [thread overview]
Message-ID: <20140611.152321.799416344244730112.davem@davemloft.net> (raw)
In-Reply-To: <1402401565-15423-1-git-send-email-makita.toshiaki@lab.ntt.co.jp>
From: Toshiaki Makita <makita.toshiaki@lab.ntt.co.jp>
Date: Tue, 10 Jun 2014 20:59:21 +0900
> Currently bridge vlan filtering doesn't work fine with 802.1ad protocol.
> Only if a bridge is configured without pvid, the bridge receives only
> 802.1ad tagged frames and no STP is used, it will work.
> Otherwise:
> - If pvid is configured, it can put only 802.1Q tags but cannot put 802.1ad
> tags.
> - If 802.1Q and 802.1ad tagged frames arrive in mixture, it applies filtering
> regardless of their protocols.
> - While an 802.1ad bridge should use another mac address for STP BPDU and
> should forward customer's BPDU frames, it can't.
> Thus, we can't properly handle frames once 802.1ad is used.
>
> Handling 802.1ad is useful if we want to allow stacked vlans to be used,
> e.g., guest VMs wants to use vlan tags and the host also wants to segregate
> guest's traffic from other guests' by vlan tags.
>
> Here is the image describing how to configure a bridge to filter VMs traffic.
>
> +-------+p/u +-----+ +---------+
> +----+ | |------|vnet0|--|User A VM|
> |eth0|--|802.1ad| +-----+ +---------+
> +----+ |bridge |p/u +-----+ +---------+
> | |------|vnet1|--|User B VM|
> +-------+ +-----+ +---------+
> p/u: pvid/untagged
>
> This patch set enables us to set vlan protocols per bridge.
> This tries to implement a bridge like S-VLAN component in IEEE 802.1Q-2011
> spec.
Series applied, thanks.
prev parent reply other threads:[~2014-06-11 22:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-10 11:59 [PATCH v2 net-next 0/4] bridge: 802.1ad vlan protocol support Toshiaki Makita
2014-06-10 11:59 ` [PATCH v2 net-next 1/4] bridge: Add 802.1ad tx vlan acceleration Toshiaki Makita
2014-06-10 11:59 ` [PATCH v2 net-next 2/4] bridge: Prepare for 802.1ad vlan filtering support Toshiaki Makita
2014-06-10 11:59 ` [PATCH v2 net-next 3/4] bridge: Prepare for forwarding another bridge group addresses Toshiaki Makita
2014-06-10 11:59 ` [PATCH v2 net-next 4/4] bridge: Support 802.1ad vlan filtering Toshiaki Makita
2014-06-11 22:23 ` David Miller [this message]
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=20140611.152321.799416344244730112.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=bridge@lists.linux-foundation.org \
--cc=makita.toshiaki@lab.ntt.co.jp \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).