Bug 1051231

Summary:	NetworkManager needs ipv6 dhclient DUID pinning
Product:	[Fedora] Fedora	Reporter:	Wolfgang Rupprecht <wolfgang.rupprecht>
Component:	NetworkManager	Assignee:	Dan Williams <dcbw>
Status:	CLOSED EOL	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	20	CC:	cra, dcbw, gilwooden, markzzzsmith, nivex
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-06-29 14:18:18 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Wolfgang Rupprecht 2014-01-09 21:46:22 UTC

Description of problem:

The IPv6 dhcp DUID is meant to be the same across all interfaces.  Currently NetworkManager has per-interface DUID's and they change at the drop of a hat.

Every time I re-install fedora (such as the upgrade from f19 to f20) NetworkManager generates a new ipv6 dhclient DUID and my upstream assigns me a new IPv6 address.  NetworkManager needs to have (or needs to document) a way to select a DUID and stick with it.  KAME had a config file in /etc for the DUID.   Perhaps NetworkManager could too.

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

NetworkManager.x86_64           1:0.9.9.0-22.git20131003.fc20

How reproducible:

always

Steps to Reproduce:
1. reinstall fedora
2. notice ipv6 address changes
3. try to figure out where to put the DUID so that we get the old address back

Actual results:

No obvious way to set the DUID.

Expected results:

a file in /etc where one can set the DUID

Additional info:

Comment 1 Fedora End Of Life 2015-05-29 10:24:55 UTC

This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. 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 '20'.

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 20 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 2 Kevin Otte 2015-06-09 20:34:10 UTC

I'd even settle for a way to easily fetch the DUID for registration purposes.

I recently installed Fedora 22 in a VM and noted that the DUID is created by dhclient during setup:

May 26 12:22:02 localhost.localdomain dhclient[1074]: Created duid \000\001\000\001\034\367Z*RT\000,R\264.

I cannot, however, discern where this DUID is stored on the filesystem.

Comment 3 Kevin Otte 2015-06-09 20:43:17 UTC

Ah, upon further inspection I see that is a DUID-LLT that is not used in NetworkManager.

Examining /var/lib/NetworkManager/dhclient6-*.lease I see the default-duid directive being generated per lease. How is this generated? Can this be a system-wide value?

Comment 4 Fedora End Of Life 2015-06-29 14:18:18 UTC

Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.