"Use the same DUID + IAID as set in DHCPv6 for DHCPv4 ClientID as per RFC4361."
The option "duid" should not be activated by default.
It makes dhcpcd to send the wrong MAC address who breaks almost every installation of Gentoo in a network who uses MAC related security / access as it sends the IPv6 mac regardless of the protocol used by the dhcp server.
I'm curious why duid is enabled in the default configuration file when
the man page says it is disabled by default?
From this bug it sounds like it might be better to disable it in the
What do you think?
DUID is a requirement of DHCPv6. Clarified a little here.
From RFC2131, DHCPv4, the clientid is supposed to be opaque and as such not translated in any way or form.
Plus, the MAC address for ethernet is sent in the chaddr field.
As to why it's now enabled by default, please read RFC4361.
Using dhcpcd-6 and duid + ISC dhcpd server, configuration by hardware address works fine.
The dhcp server in my network didn't recognize the network address. Instead of IPv4 mac XX:XX:XX:XX:XX:XX it sent the IPv6 (40 chars MAC) which the server didn't recognize. If this is the default config then at least put a warning so others know that it may cause problems with certain dhcp servers / configurations.
If you enable debug in dhcpcd, it does tell you what the client ID is going to be.
If you want more warning, modify the ebuild I guess, or maybe a news item.
Just a minor nitpick - DUID is not IPv6 specific and dhcpcd has had the option for years, just not on by default.
I have added messages to the ebuild for dhcpcd-6.0.5.
I've just been bit by this particular bug, i. e. dhcpcd-5.6.4 gets me a lease in my university network with MAC access controls, dhcpcd-6.2.0 does not. Is there a way to force dhcpcd _not_ to transmit this DUID thingy? If not, is there any chance of a noduid option in a future version?
(In reply to Andreas Eckstein from comment #6)
> I've just been bit by this particular bug, i. e. dhcpcd-5.6.4 gets me a
> lease in my university network with MAC access controls, dhcpcd-6.2.0 does
> not. Is there a way to force dhcpcd _not_ to transmit this DUID thingy? If
> not, is there any chance of a noduid option in a future version?
You can remove duid from /etc/dhcpcd.conf
noduid would be counter intuitive.