issues with ipv6 and DUID

[Steven Carr]

Then yes, I would say there is either something wrong with your dhclient
installation or it's a bug in dhclient. What happens if you try a different
client/OS?


On 5 April 2013 19:09, Cory Coager <ccoager at gmail.com> wrote:

> I can tell you from experience in my testing, the DUID changed numerous
> times just by releasing and renewing my ipv6 address.  If it's meant to be
> generated once and never change and my experience is different, then it
> sounds like a bug.
>
>
> On Fri, Apr 5, 2013 at 1:43 PM, Steven Carr <sjcarr at gmail.com> wrote:
>
>> DUID-LLT is not meant to be dynamic in the sense of constantly
>> regenerating itself, it's dynamic in that it creates a new DUID once based
>> on a known hardware ID + timestamp + link local ID to hopefully generate a
>> DUID that is unique (hardware ID and link local ID can be manually changed
>> in most OSs so you can't rely on them being unique).
>>
>> And it defaults to DUID-LLT as that is what is required in the RFC:*
>> DUID-LL is recommended for devices that have a permanently-connected
>> network interface with a link-layer address, and do not have nonvolatile,
>> writable stable storage.  DUID-LL MUST NOT be used by DHCP clients or
>> servers that cannot tell whether or not a network interface is permanently
>> attached to the device on which the DHCP client is running.*
>>
>> You need to find out why dhclient keeps regenerating the DUID-LLT value,
>> find out where dhclient stores that value and then monitor the file for
>> changes to see what/why it is being changed.
>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/dhcp-users/attachments/20130405/e3cce0a5/attachment.html>