More clues...

[Timothe Litt]

Because it bugs me (yes, pun intended), I played some more with
the sample DUID
"\001\000\000\000\000\001\000\001\024\352\033$\010\000'*\230\202"

This unpacks into hex  '010000000001000114ea1b240800272a9882'

Working backwards, I believe it represents:

 01000000 0001 0001 14ea1b24 08:00:27:2a:98:82

Where 01000000 is the client IAID -- unfortunately in native, not
network order.
This makes it impossible to maintain lease files if a server's
endianness changes
in an upgrade.  Seems like a bug.

Then 0001 would be the DUID type (LLT), 0001 would be the HWtype (ethernet),
14ea1b24  would be sun, 13 Feb 2011 04:31:32 GMT - which is close enough
to the
other times in the sample lease file to be credible.

And 08:00:27:2a:98:82 seems like a reasonable ethernet link address.

Digging through the code, this analysis seems to be correct.

I'll file the bugs.

I still would appreciate some lease files that I can use for test data...

-- 
Timothe Litt
ACM Distinguished Engineer
--------------------------
This communication may not represent the ACM or my employer's views,
if any, on the matters discussed. 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/dhcp-users/attachments/20150121/d1a90ede/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4942 bytes
Desc: S/MIME Cryptographic Signature
URL: <https://lists.isc.org/pipermail/dhcp-users/attachments/20150121/d1a90ede/attachment.bin>