Bug 2069004

Summary: [RFE] NM: please support bond new option ns_ip6_target
Product: Red Hat Enterprise Linux 9 Reporter: Hangbin Liu <haliu>
Component: NetworkManagerAssignee: Fernando F. Mancera <ferferna>
Status: CLOSED ERRATA QA Contact: Matej Berezny <mberezny>
Severity: unspecified Docs Contact: Mayur Patil <maypatil>
Priority: medium    
Version: 9.1CC: bgalvani, ferferna, lrintel, maypatil, mberezny, rkhan, sfaye, sukulkar, till, vbenes
Target Milestone: rcKeywords: FutureFeature, Triaged
Target Release: 9.1Flags: pm-rhel: mirror+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: NetworkManager-1.43.3-1.el9 Doc Type: Enhancement
Doc Text:
.`NetworkManager` now supports configuration of the `ns_ip6_target` option for bond interfaces This enhancement allows setting the `arp_interval` option by specifying a maximum of 16 IPv6 addresses as monitoring peers in `NetworkManager` for configuration of the `ns_i6_target` option for bond interfaces. Previously, it was not possible to specify IPv6 monitoring peers in `NetworkManager`. With this update, you can configure the `ns_ip6_target` option in the `bond.options` parameter by using the `nmcli` utility. `NetworkManager` applies this setting to the bond interface by enabling the specification of a maximum of 16 IPv6 addresses. This enhancement equally applies to IPv4 and IPv6 settings.
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-11-07 08:37:53 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1951910    

Description Hangbin Liu 2022-03-28 04:23:54 UTC
Description of problem:

Please help add bond new option ns_ip6_target for NM. Here is the kernel doc[1]

ns_ip6_target

        Specifies the IPv6 addresses to use as IPv6 monitoring peers when
        arp_interval is > 0.  These are the targets of the NS request
        sent to determine the health of the link to the targets.
        Specify these values in ffff:ffff::ffff:ffff format.  Multiple IPv6
        addresses must be separated by a comma.  At least one IPv6
        address must be given for NS/NA monitoring to function.  The
        maximum number of targets that can be specified is 16.  The
        default value is no IPv6 addresses.


And kernel commit [2], iproute2 commit [3] for reference.

[1] https://www.kernel.org/doc/Documentation/networking/bonding.rst
[2] https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/?id=129e3c1bab24
[3] https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=9831202f

Comment 2 sfaye 2022-11-28 11:10:26 UTC
*** Bug 2148686 has been marked as a duplicate of this bug. ***

Comment 6 Hangbin Liu 2023-03-24 08:48:30 UTC
# uname -r
5.14.0-231.el9.x86_64
# rpm -q NetworkManager
NetworkManager-1.43.4-1.el9.x86_64
# nmcli con add type bond ifname team0 bond.options "mode=active-backup,arp_interval=200,arp_missed_max=15,ns_ip6_target=fe80::210:18ff:feaa:bbcc"
Error: Failed to add 'bond-team0' connection: bond.options: 'arp_interval' option requires 'arp_ip_target' option to be set
# ip link add bond0 type bond mode active-backup arp_interval 1000 arp_missed_max 15 ns_ip6_target fe80::210:18ff:feaa:bbcc
# echo $?
0

Comment 7 Fernando F. Mancera 2023-03-24 09:50:14 UTC
Oh thanks for reporting this. I didn't know ns_ip6_target could satisfy that condition too. Let me fix it, it is simple. Thanks!

Comment 12 Hangbin Liu 2023-04-24 06:43:48 UTC
FYI, it works now:

# rpm -q NetworkManager
NetworkManager-1.43.6-1.el9.x86_64
# nmcli con add type bond ifname bond0 bond.options "mode=active-backup,arp_interval=200,arp_missed_max=15,ns_ip6_target=fe80::210:18ff:feaa:bbcc"
Connection 'bond-bond0' (37c4fae6-5255-4acc-9882-2bd16c77d4ab) successfully added.
# nmcli con show bond-bond0 | grep "bond.options"
bond.options:                           mode=active-backup,arp_interval=200,arp_missed_max=15,ns_ip6_target=fe80::210:18ff:feaa:bbcc

Thanks
Hangbin

Comment 17 errata-xmlrpc 2023-11-07 08:37:53 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (NetworkManager bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2023:6585