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.
Description of problem:
In *CoreOS we have seen complaints because in some cloud environments the wrong ipv6 address is shown to the user (the environment is expecting eui64 for address autoconfiguration). This is arguably a bug in the environment, but there are other reasons for wanting to disable `stable-privacy` mode globally for an instance or even at a vendor level (i.e. the Fedora CoreOS OpenStack image).
context: https://github.com/coreos/fedora-coreos-tracker/issues/907
Could we add support for configuring this in the global config?
Additional info:
This ticket came out of a meeting I had with some of the NetworkManager team members. It was requested I open a new ticket for the feature request.
A previous ticket describing a similar feature request is at
https://bugzilla.redhat.com/show_bug.cgi?id=1743161
(In reply to Dusty Mabe from comment #6)
> Thomas,
>
> Did you mean to say "addr-gen-mode is NOW configurable via global connection
> defaults"?
yes.
/etc/NetworkManager/conf.d/95-my.conf
with
[connection-95-my]
ipv6.addr-gen-mode=0
should work (0 is "eui64") -- if `nmcli connection show "$PROFILE"` either prints
ipv6.addr-gen-mode=default
ipv6.addr-gen-mode=default-or-eui64
(only in those two cases the fallback to the default happens)
-- of course, if you create a profile with D-Bus/nmcli it will default to "default", and if you omit the key from keyfile it will default to "default-or-eui64".
With a sufficiently recent nmcli that supports --offline, also test:
$ nmcli --offline connection add type ethernet ipv6.addr-gen-mode 0
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:7680