Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

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.

the router advertisment has two flags: M (managed) and O (otherconf).

if those flags are set, we are supposed to do DHCPv6.
But with otherconf, we are not supposed to actually configure IPv6 addresses.

This broke with 1.36 rework.


Upstream report: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/953#note_1377764
Upstream fix: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/1220


This is reported here, to properly track it and ensure we have CI tests for this.

Fixed upstream by https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/1220

notes for testing:


1) have a IPv6 router that announces a certain prefix. The RA has the "O flag" set, which means to do stateless DHCPv6, that is, not to get an IPv6 lease.

2) configure an NM profile with `ipv6.method=auto`. Note that NM will start DHCPv6 due to the "other config" flag.

3a) In this mode, NM should do DHCPv6, but it should not ask for any addresses. I think usually the DHCPv6 server would see that, and consequently the lease would not have any addresses. The relevant part here is that NM makes a DHCPv6 in a way that requests info-only.

3b) even if NM requests no IPv6 addresses, if the DHCPv6 happens to hand out any IPv6 addresses (which would be a bug), NM should not configure them.

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-2022:8265