On Thu, 26 Oct 2017 12:16:05 -0700
Roopa Prabhu <ro...@cumulusnetworks.com> wrote:
> From: Roopa Prabhu <ro...@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 <ro...@cumulusnetworks.com>
>
> Roopa Prabhu (2):
> iplink: bridge: support bridge port vlan_tunnel attribute
> bridge: vlan: support for per vlan tunnel info
>
> 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(-)
>
These patches are fine, but conflict with current net-next tree
where I merged some other vlan info patches.
Please rebase.
