netdev - RE: [PATCH net-next v1 0/2] bonding: Extend arp_ip_target format to allow for a list of vlan tags.

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]

Message-ID:
 <MW3PR15MB3913C0A57D113A650B9C5B59FA97A@MW3PR15MB3913.namprd15.prod.outlook.com>
Date: Mon, 12 May 2025 23:54:24 +0000
From: David Wilder <wilder@...ibm.com>
To: Hangbin Liu <liuhangbin@...il.com>
CC: "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
        "jv@...sburgh.net"
	<jv@...sburgh.net>,
        "pradeeps@...ux.vnet.ibm.com"
	<pradeeps@...ux.vnet.ibm.com>,
        Pradeep Satyanarayana <pradeep@...ibm.com>,
        "i.maximets@....org" <i.maximets@....org>,
        Adrian Moreno Zapata
	<amorenoz@...hat.com>,
        Hangbin Liu <haliu@...hat.com>
Subject: RE: [PATCH net-next v1 0/2] bonding: Extend arp_ip_target format to allow
 for a list of vlan tags.

>Hi David,
>> The current implementation of the arp monitor builds a list of vlan-tags by
>> following the chain of net_devices above the bond. See: bond_verify_device_path().
>> Unfortunately with some configurations this is not possible. One example is
>> when an ovs switch is configured above the bond.
>>
>> This change extends the "arp_ip_target" parameter format to allow for a list of
>> vlan tags to be included for each arp target. This new list of tags is optional
>> and may be omitted to preserve the current format and process of gathering tags.
>> When provided the list of tags circumvents the process of gathering tags by
>> using the supplied list. An empty list can be provided to simply skip the the
>> process of gathering tags.
>>
>> The purposed new format for arp_ip_target is:
>> arp_ip_target=ipv4-address[vlan-tag\...],...
>>
>> Examples:
>> arp_ip_target=10.0.0.1,10.0.0.2 (Determine tags automatically for both targets)
>> arp_ip_target=10.0.0.1[]        (Don't add any tags, don't gather tags)
>> arp_ip_target=10.0.0.1[100/200] (Don't gather tags, use supplied list of tags)
>> arp_ip_target=10.0.0.1,10.0.0.2[100] (add vlan 100 tag for 10.0.0.2.
>>                                       Gather tags for 10.0.0.1.)
>
>Thanks for the update. What about the IPv6 NS targets? Will you support it
>or only the arp targets?

Thank you for the input.

My initial plan is to support IPv4, but I will ensure that it won't adversely impact IPv6.

>
>BTW, when add or update the parameter, please also update the bond documents
>and iproute2 cmd.

Will do.

>
>Thanks
>Hangbin

David Wilder (wilder@...ibm.com)