netdev - Re: [PATCH iproute2 net-next v2 0/3] support for vxlan vni filtering

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <7da08a10-7d2d-4b58-821c-bec68bc55c87@gmail.com>
Date:   Sun, 8 May 2022 09:53:04 -0600
From:   David Ahern <dsahern@...il.com>
To:     Roopa Prabhu <roopa@...dia.com>
Cc:     netdev@...r.kernel.org, stephen@...workplumber.org,
        razor@...ckwall.org
Subject: Re: [PATCH iproute2 net-next v2 0/3] support for vxlan vni filtering

On 5/7/22 10:53 PM, Roopa Prabhu wrote:
> This series adds bridge command to manage
> recently added vnifilter on a collect metadata
> vxlan (external) device. Also includes per vni stats
> support.
> 
> examples:
> $bridge vni add dev vxlan0 vni 400
> 
> $bridge vni add dev vxlan0 vni 200 group 239.1.1.101
> 
> $bridge vni del dev vxlan0 vni 400
> 
> $bridge vni show
> 
> $bridge -s vni show
> 
> Nikolay Aleksandrov (1):
>   bridge: vni: add support for stats dumping
> 
> Roopa Prabhu (2):
>   bridge: vxlan device vnifilter support
>   ip: iplink_vxlan: add support to set vnifiltering flag on vxlan device
> 
> v2 : replace matches by strcmp in bridge/vni.c. v2 still uses matches
> in iplink_vxlan.c to match the rest of the code
> 

fixed those as well and applied to iproute2-next. We are not taking any
more uses of matches(), even for legacy commands.