4.0 RC3 DUID Conflict and Solution
Posted: Thu Jan 31, 2019 4:41 am
I had two pi-star 4.0 RC3 instances on my internal network contending for the same IPv6 address. I noticed that they both had the same DUID, which was in the distributed software. DUIDs are supposed to be completely unique and not copied between systems. My solution was to delete /etc/dhcpcd.duid and then reboot. Each system then had its own DUID and ended up with the expected IPv6 addresses.
Interestingly, the wired ethernet host created a DUID but did not create /etc/dhcpcd.duid, whereas the WLAN connected instance did. I do not know why. So, on the wired host I had to stop dhcpcd.service and run dhcpcd --duid in order to recreate the file.
It would be beneficial as IPv6 spreads its reach if this could be ultimately handled somehow in the initial boot process. But at least the image should omit /etc/dhcpcd.duid (as well as dhcpcd.secret).
Interestingly, the wired ethernet host created a DUID but did not create /etc/dhcpcd.duid, whereas the WLAN connected instance did. I do not know why. So, on the wired host I had to stop dhcpcd.service and run dhcpcd --duid in order to recreate the file.
It would be beneficial as IPv6 spreads its reach if this could be ultimately handled somehow in the initial boot process. But at least the image should omit /etc/dhcpcd.duid (as well as dhcpcd.secret).