Bug 1779389 - nm-initrd-generator force ipv6 addr-gen-mode to stable-privacy
Summary: nm-initrd-generator force ipv6 addr-gen-mode to stable-privacy
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: NetworkManager
Version: 31
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
Assignee: Lubomir Rintel
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-12-03 21:36 UTC by fabien.redhat
Modified: 2020-11-24 20:17 UTC (History)
11 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2020-11-24 20:17:54 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description fabien.redhat 2019-12-03 21:36:01 UTC
Description of problem:
Enabling ip= option in dracut call nm-initrd-generator trough /usr/lib/dracut/modules.d/35network-manager/nm-config.sh
At each boot the system get a new local link IPv6 address.

Version-Release number of selected component (if applicable):
NetworkManager-1.20.8-1.fc31.x86_64

How reproducible:
$ /usr/libexec/nm-initrd-generator -s ip=exampleiface:on

Actual results:
- the output configuration always set addr-gen-mode=stable-privacy (if ipv6 is allowed)
- the local link IPv6 address is not stable though reboot


Expected results:
- respect the IPV6_ADDR_GEN_MODE parameter set in /etc/sysconfig/network-scripts/ifcfg-exampleiface
- OR add dracut option that can set the addr-gen-mode


Additional info:
A workaround is to replace the value just after nm-initrd-generator run. Add the following line at the end of /usr/lib/dracut/modules.d/35network-manager/nm-config.sh, and run 'dracut -f' again :
sed -i -e s:stable-privacy:eui64: /run/NetworkManager/system-connections/exampleiface.nmconnection

Comment 1 Thomas Haller 2019-12-04 17:12:41 UTC
> - respect the IPV6_ADDR_GEN_MODE parameter set in /etc/sysconfig/network-scripts/ifcfg-exampleiface

This should work, provided that you placed the ifcfg file into the initrd (which I think dracut does not by default). Then NM should start activating this profile, instead of creating a new one. In general, should it be possible to embed a profile in initrd and use that.


Also, maybe when creating the initrd, it should also package "/var/lib/NetworkManager/secret_key". This file, together with /etc/machine-id is the "identity" of the host, and the hashed content is used for stuff like ipv6.addr-gen-mode=stable-privacy and ipv4.dhcp-client-id=stable. So, quite possibly these files should be also accessible from initrd.



But yes, good point. Maybe nm-initrd-generator should not default to stable-privacy. Or maybe it indeed should become configurable... ??

Comment 2 Beniamino Galvani 2019-12-04 17:21:16 UTC
(In reply to Thomas Haller from comment #1)
> But yes, good point. Maybe nm-initrd-generator should not default to
> stable-privacy. Or maybe it indeed should become configurable... ??

I agree, the addr-gen-mode should be EUI64 to guarantee stability of the address. I don't think it is necessary for now to make it configurable.

Comment 4 Ben Cotton 2020-11-03 17:14:22 UTC
This message is a reminder that Fedora 31 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '31'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 31 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 5 Ben Cotton 2020-11-24 20:17:54 UTC
Fedora 31 changed to end-of-life (EOL) status on 2020-11-24. Fedora 31 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.