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).
Could we add support for configuring this in the global config?
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
This is linked in the github issue but worth mentioning here:
potential solution, on discussion here:
addr-gen-mode is not configurable via global connection defaults.
See upstream commit https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/e6a33c04ebe1ac84e31628911e25bdfd7534dd3c
Did you mean to say "addr-gen-mode is NOW configurable via global connection defaults"?
(In reply to Dusty Mabe from comment #6)
> Did you mean to say "addr-gen-mode is NOW configurable via global connection
should work (0 is "eui64") -- if `nmcli connection show "$PROFILE"` either prints
(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
> "is NOW configurable"
"NOW" being upstream `main` branch.
Btw, we have copr repos from upstream here: https://copr.fedorainfracloud.org/coprs/networkmanager/