All of
 help / color / mirror / Atom feed
From: Nikolay Aleksandrov <>
	Nikolay Aleksandrov <>
Subject: [PATCH iproute2-next 0/2] bridge: vlan: add support for mcast_router option
Date: Wed,  1 Sep 2021 13:38:14 +0300	[thread overview]
Message-ID: <> (raw)

From: Nikolay Aleksandrov <>

This set adds support for vlan port/bridge multicast router option. It is
similar to the already existing bridge-wide mcast_router control. Patch 01
moves attribute adding and parsing together for vlan option setting,
similar to global vlan option setting. It simplifies adding new options
because we can avoid reserved values and additional checks. Patch 02
adds the new mcast_router option and updates the related man page.

 # mark port ens16 as a permanent mcast router for vlan 100
 $ bridge vlan set dev ens16 vid 100 mcast_router 2
 # disable mcast router for port ens16 and vlan 200
 $ bridge vlan set dev ens16 vid 200 mcast_router 0
 $ bridge -d vlan show
 port              vlan-id
 ens16             1 PVID Egress Untagged
                     state forwarding mcast_router 1
                     state forwarding mcast_router 2
                     state forwarding mcast_router 0

Note that this set depends on the latest kernel uapi headers.


Nikolay Aleksandrov (2):
  bridge: vlan: set vlan option attributes while parsing
  bridge: vlan: add support for mcast_router option

 bridge/vlan.c     | 70 +++++++++++++++++++++++++++++------------------
 man/man8/bridge.8 | 29 +++++++++++++++++++-
 2 files changed, 71 insertions(+), 28 deletions(-)


             reply	other threads:[~2021-09-01 10:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-01 10:38 Nikolay Aleksandrov [this message]
2021-09-01 10:38 ` [PATCH iproute2-next 1/2] bridge: vlan: set vlan option attributes while parsing Nikolay Aleksandrov
2021-09-01 10:38 ` [PATCH iproute2-next 2/2] bridge: vlan: add support for mcast_router option Nikolay Aleksandrov
2021-09-06 23:04 ` [PATCH iproute2-next 0/2] " David Ahern

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \

* 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.