RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2165029 - No ipv6 link local address for a nmcli created bridge when it has ipv4 address and STP on
Summary: No ipv6 link local address for a nmcli created bridge when it has ipv4 addres...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: NetworkManager
Version: 8.7
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Beniamino Galvani
QA Contact: David Jaša
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-01-27 12:50 UTC by Michal Tesar
Modified: 2023-05-16 11:04 UTC (History)
9 users (show)

Fixed In Version: NetworkManager-1.40.14-1.el8
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-05-16 09:05:03 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker NMT-198 0 None None None 2023-01-27 12:52:59 UTC
Red Hat Issue Tracker RHELPLAN-146693 0 None None None 2023-01-27 12:53:03 UTC
Red Hat Product Errata RHBA-2023:2968 0 None None None 2023-05-16 09:05:14 UTC
freedesktop.org Gitlab NetworkManager NetworkManager-ci merge_requests 1335 0 None opened bridge: verify v6ll presence with static v4 and STP on 2023-02-23 19:40:21 UTC
freedesktop.org Gitlab NetworkManager NetworkManager merge_requests 1485 0 None merged device: fix condition for restarting IP config after carrier change 2023-01-27 13:59:33 UTC

Description Michal Tesar 2023-01-27 12:50:19 UTC 
Description of problem:

When a bridge is created via nmcli with ipv4.method manual ipv4.addresses A.B.C.D/24 ipv6.method link-local no link local address is present on the bridge.

Version-Release number of selected component (if applicable):

# rpm -q NetworkManager
NetworkManager-1.40.0-5.el8_7.x86_64

# rpm -qa | grep NetworkManager
NetworkManager-1.40.0-5.el8_7.x86_64
NetworkManager-team-1.40.0-5.el8_7.x86_64
NetworkManager-libnm-1.40.0-5.el8_7.x86_64
NetworkManager-initscripts-updown-1.40.0-5.el8_7.noarch
NetworkManager-tui-1.40.0-5.el8_7.x86_64
NetworkManager-config-server-1.40.0-5.el8_7.noarch

# nmcli --version 
nmcli tool, version 1.40.0-5.el8_7

How reproducible:

ipv4.method manual ipv4.addresses A.B.C.D/X ipv6.method link-local works only for normal ethernet connection as well as for vlan on top of it
but does not work for bridges.
 
# nmcli connection add type ethernet con-name ens10 ifname ens10
# nmcli connection modify ens10 ipv4.method manual ipv4.addresses 10.75.99.1/24 ipv6.method link-local
# nmcli connection up ens10
 
# nmcli connection show
NAME   UUID                                  TYPE      DEVICE
ens10  17f38a69-4334-41ca-aedc-9b8b878d1c7f  ethernet  ens10  
 
ens10: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 52:54:00:25:80:58 brd ff:ff:ff:ff:ff:ff
    altname enp0s10
    inet 10.75.99.1/24 brd 10.75.99.255 scope global noprefixroute ens10
       valid_lft forever preferred_lft forever
    inet6 fe80::b4af:5fd8:a613:53a8/64 scope link noprefixroute
       valid_lft forever preferred_lft forever
 
# nmcli connection add type vlan con-name ens10-vlan ifname ens10.999 id 999 dev ens10
# nmcli connection modify ens10-vlan ipv4.method manual ipv4.addresses 10.75.99.1/24 ipv6.method link-local
# nmcli connection up ens10-vlan
 
# nmcli connection show
NAME        UUID                                  TYPE      DEVICE    
ens10       17f38a69-4334-41ca-aedc-9b8b878d1c7f  ethernet  ens10    
ens10-vlan  f173ee66-3411-4d55-8c3f-393ed9d2929f  vlan      ens10.999
 
ens10.999@ens10: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 52:54:00:25:80:58 brd ff:ff:ff:ff:ff:ff
    inet 10.75.99.1/24 brd 10.75.99.255 scope global noprefixroute ens10.999
       valid_lft forever preferred_lft forever
    inet6 fe80::4ea5:8225:621e:abe8/64 scope link noprefixroute
       valid_lft forever preferred_lft forever
 
# nmcli connection add type bridge con-name br0 ifname br0
# nmcli connection modify br0 ipv4.method manual ipv4.addresses 10.75.99.1/24 ipv6.method link-local
# nmcli connection up br0
 
# nmcli connection show
NAME        UUID                                  TYPE      DEVICE    
 
ens10       17f38a69-4334-41ca-aedc-9b8b878d1c7f  ethernet  ens10    
ens10-vlan  f173ee66-3411-4d55-8c3f-393ed9d2929f  vlan      ens10.999
br0         0d5a7e95-75c5-4660-8a96-ab95d8a0892f  bridge    br0      
 
br0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
    link/ether be:c0:7e:de:c2:ee brd ff:ff:ff:ff:ff:ff
    inet 10.75.99.1/24 brd 10.75.99.255 scope global noprefixroute br0
       valid_lft forever preferred_lft forever
 
But ipv4.method disabled -ipv4.addresses 10.75.99.1/24 ipv6.method link-local works.
 
# nmcli connection modify ens10-vlan ipv4.method disabled -ipv4.addresses 10.75.99.1/24 ipv6.method link-loca
# nmcli connection modify ens10-vlan master br0 slave-type bridge
# nmcli connection modify br0 ipv4.method disable -ipv4.addresses 10.75.99.1/24 ipv6.method link-loca
# nmcli connection up ens10-vlan
# nmcli connection up br0
 
# nmcli connection show
NAME        UUID                                  TYPE      DEVICE    
ens10       17f38a69-4334-41ca-aedc-9b8b878d1c7f  ethernet  ens10    
br0         0d5a7e95-75c5-4660-8a96-ab95d8a0892f  bridge    br0      
ens10-vlan  f173ee66-3411-4d55-8c3f-393ed9d2929f  vlan      ens10.999
 
br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 52:54:00:25:80:58 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::ee46:f187:87c9:d9a9/64 scope link noprefixroute
       valid_lft forever preferred_lft forever

The so-far-known WA is to disable STP for the bridge when ipv4.method manual is present.

Actual results:

Bridge does not get ipv6 link local address when ipv4 addr is present on the bridge + STP is on

Expected results:

Bridge gets an ipv6 link local address when ipv4 address is present on the ridge + STP is on.
Comment 2 Beniamino Galvani 2023-01-27 13:59:34 UTC 
This bug is fixed by the following upstream merge request:

https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/1485

The patch is included NM 1.40.10+.
Comment 10 David Jaša 2023-02-23 19:40:22 UTC 
VERIFIED in NetworkManager-1.40.14-1.el8.x86_64: link-local v6 address is added to the connection once it gets carrier.

Covered in NM CI by a new scenario: bridge_v6ll_present_with_stp_and_static_v4
Comment 12 errata-xmlrpc 2023-05-16 09:05:03 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:2968
Note You need to log in before you can comment on or make changes to this bug.