dhcpcd.duid - timestamp being changed in solicit
Roger James
Wed Mar 13 17:21:57 2019Running dhcpcd version 1:6.11.5-1+rpt7 on debian. I see the DUID-LLT generated by dhcpcd and stored dhcpcd.duid is being updated with a new timestamp every time it is sent out for example in a solicit. Surely this is contrary to RFC6355.
"DUIDs are intended to remain constant over time, so that they can be used as permanent identifiers for a device. In the case of DUID- LLTs, they are intended to be generated once, stored in stable storage, and reused from that point forward." Is this intentional?Also if the dhcp.duid file is hand edited and a DUID-UUID is inserted, then then the UUID part of the DUID is truncated to 8 bytes when it is used.
This makes it difficult to use dhcpcd to assign static dhcpv6 leases. Roger
| Re: dhcpcd.duid - timestamp being changed in solicit | Roy Marples |