netdev - Re: [PATCH net-next v1 1/1] bonding: Adding limmited support for ARP monitoring with ovs.

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: <773e2881-c9e8-4cd8-a3ef-711a203a449d@redhat.com>
Date: Tue, 15 Apr 2025 15:58:58 +0200
From: Paolo Abeni <pabeni@...hat.com>
To: David J Wilder <wilder@...ibm.com>, netdev@...r.kernel.org
Cc: jv@...sburgh.net, pradeeps@...ux.vnet.ibm.com, pradeep@...ibm.com
Subject: Re: [PATCH net-next v1 1/1] bonding: Adding limmited support for ARP
 monitoring with ovs.

On 4/11/25 7:48 PM, David J Wilder wrote:
> Adding limited support for the ARP Monitoring feature when ovs is
> configured above the bond. When no vlan tags are used in the configuration
> or when the tag is added between the bond interface and the ovs bridge arp
> monitoring will function correctly. The use of tags between the ovs bridge
> and the routed interface are not supported.
> 
> For example:
> 1) bond0 -> ovs-br -> ovs-port (x.x.x.x) is supported
> 2) bond0 -> bond0.100 -> ovs-br -> ovs-port (x.x.x.x) is supported.
> 3) bond0 -> ovs-br -> ovs-port -> ovs-port.100 (x.x.x.x) is not supported.
> 
> Configurations #1 and #2 were tested and verified to function corectly.
> In the second configuration the correct vlan tags were seen in the arp.

If you are adding support for new setup types, you should additionally
implement some test-cases to cover them.

Cheers,

Paolo