Rpis and connman are providing multiple DUIDs to dhcpv6 server

[JimKnopf]

@sam_nazarko

wget https://collab.osmc.tv/index.php/s/ZeYdZHapKwNmHpS/download/armv7-connman-osmc.deb -O connman.deb
sudo dpkg -i connman.deb
reboot

If you believe the entries in the settings file, this seems to work:

#cat /var/lib/connman/ethernet_900eb31cafdd_cable/settings
[ethernet_900eb31cafdd_cable]
Name=Wired
AutoConnect=true
Modified=2024-04-06T08:22:07Z
IPv4.method=dhcp
IPv4.DHCP.LastAddress=10.10.10.182
IPv6.method=auto
IPv6.privacy=disabled
IPv6.DHCP.DUID=00030001900eb31cafdd

root@osmc-vero4kplus:~# connmanctl disconnect ethernet_900eb31cafdd_cable && connmanctl connect ethernet_900eb31cafdd_cable
Disconnected ethernet_900eb31cafdd_cable
Connected ethernet_900eb31cafdd_cable

root@osmc-vero4kplus:~# cat /var/lib/connman/ethernet_900eb31cafdd_cable/settings
[ethernet_900eb31cafdd_cable]
Name=Wired
AutoConnect=true
Modified=2024-04-06T08:22:36Z
IPv4.method=dhcp
IPv4.DHCP.LastAddress=10.10.10.182
IPv6.method=auto
IPv6.privacy=disabled
IPv6.DHCP.DUID=00030001900eb31cafdd

I’m still wondering why the connman folks insert timestamp information by default. Are there dhcpv6 systems, which have a problem with getting the same DUID again and again?