From: Stephen Hemminger <stephen@networkplumber.org>
To: Roopa Prabhu <roopa@cumulusnetworks.com>
Cc: netdev@vger.kernel.org, nikolay@cumulusnetworks.com
Subject: Re: [PATCH iproute2 net-next v2 0/2] bridge: support for vlan to tunnel mapping
Date: Tue, 31 Oct 2017 18:06:30 +0100 [thread overview]
Message-ID: <20171031180630.3939fba7@shemminger-XPS-13-9360> (raw)
In-Reply-To: <1509167630-9869-1-git-send-email-roopa@cumulusnetworks.com>
On Fri, 27 Oct 2017 22:13:48 -0700
Roopa Prabhu <roopa@cumulusnetworks.com> wrote:
> From: Roopa Prabhu <roopa@cumulusnetworks.com>
>
> This series adds the required options to iplink and bridge commands
> to enable per vlan tunnel info on a bridge port provided by
> netlink attributes IFLA_BRPORT_VLAN_TUNNEL (flag) and
> IFLA_BRIDGE_VLAN_TUNNEL_INFO
>
> enable vlan-tunnel mapping on a bridge port:
> $ip link set dev vxlan0 type bridge_slave vlan_tunnel on
> $ip link set dev vxlan0 type bridge_slave vlan_tunnel off
>
> or
>
> $bridge link set dev vxlan0 vlan_tunnel on
> $bridge link set dev vxlan0 vlan_tunnel off
>
> add vlan tunnel mapping (expects vlans to have been already
> configured on the port):
> $bridge vlan add dev vxlan0 vid 2000 tunnel_info id 2000
> $bridge vlan add dev vxlan0 vid 1000-1001 tunnel_info id 2000-2001
>
> $bridge vlan tunnelshow
> port vlan ids tunnel id
> vxlan0 1000-1001 1000-1001
> 2000 2000
>
> $bridge -j vlan tunnelshow
> {
> "dummy0": [],
> "dummy1": [],
> "bridge": [],
> "vxlan0": [{
> "vlan": 1000,
> "vlanEnd": 1001,
> "tunid": 1000,
> "tunidEnd": 1001
> },{
> "vlan": 2000,
> "tunid": 2000
> }
> ]
> }
>
> Signed-off-by: Roopa Prabhu <roopa@cumulusnetworks.com>
>
> Roopa Prabhu (2):
> iplink: bridge: support bridge port vlan_tunnel attribute
> bridge: vlan: support for per vlan tunnel info
>
> v2 - rebase to latest net-next
>
> bridge/link.c | 12 ++
> bridge/vlan.c | 305 ++++++++++++++++++++++++++++++++++++++++++-----
> ip/iplink_bridge_slave.c | 9 ++
> man/man8/bridge.8 | 12 +-
> man/man8/ip-link.8.in | 5 +
> 5 files changed, 315 insertions(+), 28 deletions(-)
>
Applied to net-next
prev parent reply other threads:[~2017-10-31 17:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-28 5:13 [PATCH iproute2 net-next v2 0/2] bridge: support for vlan to tunnel mapping Roopa Prabhu
2017-10-28 5:13 ` [PATCH iproute2 net-next v2 1/2] iplink: bridge: support bridge port vlan_tunnel attribute Roopa Prabhu
2017-10-28 5:13 ` [PATCH iproute2 net-next v2 2/2] bridge: vlan: support for per vlan tunnel info Roopa Prabhu
2017-10-31 17:06 ` Stephen Hemminger [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=20171031180630.3939fba7@shemminger-XPS-13-9360 \
--to=stephen@networkplumber.org \
--cc=netdev@vger.kernel.org \
--cc=nikolay@cumulusnetworks.com \
--cc=roopa@cumulusnetworks.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).