<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Because it bugs me (yes, pun intended), I played some more with <br>
the sample DUID
"\001\000\000\000\000\001\000\001\024\352\033$\010\000'*\230\202"<br>
<br>
This unpacks into hex '010000000001000114ea1b240800272a9882'<br>
<br>
Working backwards, I believe it represents:<br>
<br>
01000000 0001 0001 14ea1b24 08:00:27:2a:98:82<br>
<br>
Where 01000000 is the client IAID -- unfortunately in native, not
network order.<br>
This makes it impossible to maintain lease files if a server's
endianness changes<br>
in an upgrade. Seems like a bug.<br>
<br>
Then 0001 would be the DUID type (LLT), 0001 would be the HWtype
(ethernet),<br>
<span style="color: rgb(51, 51, 51); font-family: 'Lucida Grande',
Verdana, 'Bitstream Vera Sans', Arial, sans-serif; font-size:
12px; font-style: normal; font-variant: normal; font-weight:
normal; letter-spacing: normal; line-height: 22px; orphans: auto;
text-align: start; text-indent: 0px; text-transform: none;
white-space: normal; widows: auto; word-spacing: 0px;
-webkit-text-stroke-width: 0px; display: inline !important; float:
none; background-color: rgb(255, 255, 255);">14ea1b24 would be
sun, 13 Feb 2011 04:31:32 GMT - which is close enough to the<br>
other times in the sample lease file to be credible.<br>
<br>
And </span>08:00:27:2a:98:82 seems like a reasonable ethernet
link address.<br>
<br>
Digging through the code, this analysis seems to be correct.<br>
<br>
I'll file the bugs.<br>
<br>
I still would appreciate some lease files that I can use for test
data...<br>
<br>
<pre class="moz-signature" cols="72">--
Timothe Litt
ACM Distinguished Engineer
--------------------------
This communication may not represent the ACM or my employer's views,
if any, on the matters discussed.
</pre>
</body>
</html>