netdev - Re: [PATCH iproute2-next 0/2] bridge: vlan: add support for mcast

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Mon, 6 Sep 2021 17:04:36 -0600
From:   David Ahern <dsahern@...il.com>
To:     Nikolay Aleksandrov <razor@...ckwall.org>, netdev@...r.kernel.org
Cc:     roopa@...dia.com, dsahern@...il.com, stephen@...workplumber.org,
        Nikolay Aleksandrov <nikolay@...dia.com>
Subject: Re: [PATCH iproute2-next 0/2] bridge: vlan: add support for
 mcast_router option

On 9/1/21 4:38 AM, Nikolay Aleksandrov wrote:
> From: Nikolay Aleksandrov <nikolay@...dia.com>
> 
> Hi,
> 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.
> 
> Example:
>  # 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
>                    100
>                      state forwarding mcast_router 2
>                    200
>                      state forwarding mcast_router 0
> 
> Note that this set depends on the latest kernel uapi headers.
> 

applied to iproute2-next.