Bug 869636

Summary:	problematic DUID configuration
Product:	Red Hat Enterprise Linux 5	Reporter:	elias
Component:	dhcpv6	Assignee:	Jiri Popelka <jpopelka>
Status:	CLOSED WONTFIX	QA Contact:	Release Test Team <release-test-team-automation>
Severity:	unspecified	Docs Contact:
Priority:	low
Version:	5.7	CC:	jcpunk
Target Milestone:	rc
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-03-05 15:45:27 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 elias 2012-10-24 12:57:23 UTC

Description of problem:
I have a client with MAC address 52:54:00:F8:2D:0C. Choice of DUID for this adapter is
00:01:00:01:18:12:27:1f:48:aa:c1:b1:62:2b
(from /var/lib/dhcpv6/client6.leases204339200)
^00:01 indicates that this should be a DUID-LLT, but I don't see the MAC address anywhere there. I also don't see any MAC address on that system inside of this DUID.

Moreover, DUID is stored in binary form and this is very inconvenient when you need to copy this data to config file of DHCPv6 server.

There also seems to be no option for selecting DUID-LL type instead DUID-LLT (or something what wants to look like DUID-LLT).

Version-Release number of selected component (if applicable):
Name       : dhcpv6
Arch       : x86_64
Version    : 1.0.10
Release    : 20.el5


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:
DUID type cannot be changed and is not a proper LLT DUID.

Expected results:
DUID type should be configurable and real DUIDs should match the specification.


Additional info:

Comment 1 Jiri Popelka 2012-10-24 15:28:18 UTC

(In reply to comment #0)
> I have a client with MAC address 52:54:00:F8:2D:0C. Choice of DUID for this
> adapter is
> 00:01:00:01:18:12:27:1f:48:aa:c1:b1:62:2b
> (from /var/lib/dhcpv6/client6.leases204339200)
> ^00:01 indicates that this should be a DUID-LLT, but I don't see the MAC
> address anywhere there.

Yes, this seems to be a bug, the last octets should contain the link layer address. However probably not a serious one, because RFC 3315 says:
"Clients and servers MUST treat DUIDs as opaque values and MUST only
compare DUIDs for equality. Clients and servers MUST NOT in any
other way interpret DUIDs."

> Moreover, DUID is stored in binary form and this is very inconvenient when
> you need to copy this data to config file of DHCPv6 server.

Strange, in my case the /var/lib/dhcpv6/client6.leases<IAID> is ASCII text file.
 
> There also seems to be no option for selecting DUID-LL type instead DUID-LLT
> (or something what wants to look like DUID-LLT).

I have no idea whether there's a way to change the DUID type, sorry.

Comment 2 Jiri Popelka 2013-03-05 15:45:27 UTC

RHEL-5.10 (the next RHEL-5 minor release) is going to be the first production phase 2 [1] release of RHEL-5.
I'm closing this bugzilla as WONTFIX because since phase 2 we'll be addressing only security or critical issues.

[1] https://access.redhat.com/support/policy/updates/errata/

Comment 3 Jiri Popelka 2013-11-13 14:05:39 UTC

(In reply to elias from comment #0)
> ^00:01 indicates that this should be a DUID-LLT, but I don't see the MAC
> address anywhere there. I also don't see any MAC address on that system
> inside of this DUID.

If you by any chance still need it, I back-ported (because of bug #1028314) a patch that should fix this.
Unofficial builds are here
http://jpopelka.fedorapeople.org/dhcpv6-DUID-MAC/