<html><head></head><body><div style="font-family: Verdana;font-size: 12.0px;"><div>
<div style="font-family: Verdana;font-size: 12.0px;">
<div>Hello all,</div>
<div> </div>
<div>I hope I'm using the connect list for this dhclient (or admin?) issue.<br/>
If not, I'm sorry for that.</div>
<div>Which one it the correct one?</div>
<div> </div>
<div>My question in short words:<br/>
which words we have to put in a line in /etc/dhcp/dhclient.conf (or somewhere else) to force dhclient to use DUID-TTL (client-id=1) oder DUID-LL (client-id=3) for DHCPv6 solicitate message.<br/>
We don't want to define the whole client-id, just the type of it.</div>
<div> </div>
<div><br/>
Now the long version of my issue:<br/>
We want to use a IPv6 Linux client with DHCP. The client is connected to a network where the first hop is a Cisco ASA. The ASA is configured and is working as a DHCPv6 relay system, too.<br/>
The DHCPv6-Server is attached to another interface of the ASA firewall.</div>
<div>We see a working relay config for IPv6, but mainly for Windows client. Most of today debian Linux clients doesn't get any DHCPv6 information even if other and/or managed flag is set in RA packets.</div>
<div> </div>
<div>Debuging DHCP on the ASA, we see dhclient is using a dhcp client id with type 4 (new in RFC 6355) and default type when using network manager.<br/>
This type of client id is most likely not implemented in the relay agent and the Cisco bug-report (CSCvr63051) recommends to change the type of client-id to 1 (if we know this, we can interpret the bug-report like that)</div>
<div> </div>
<div>OK, looks like we have to force the dhcp6 client to use another type of the client-id...</div>
<div> </div>
<div>Looking to RFC 3315, the client-id of 1 is DUID-LLT. So we added the following line in /etc/dhcp/dhclient.conf</div>
<div> option dhcp6.client-id duid-llt;</div>
<div> </div>
<div>To have the same situation than a clear system we did a<br/>
rm /var/lib/dhcp/dhclient6.leases<br/>
<br/>
and after that we run<br/>
dhclient -6 -r ens192<br/>
<br/>
Now we checked log file:<br/>
journalctl | grep dhc</div>
<div>dhclient[839]: /etc/dhcp/dhclient.conf line 14: expecting "code" keyword.<br/>
dhclient[839]: option dhcp6.client-id =<br/>
dhclient[839]: ^</div>
<div><br/>
We change the added line to<br/>
option dhcp6.client-id code=1;<br/>
and got another message:<br/>
<br/>
dhclient[2321]: /etc/dhcp/dhclient.conf line 14: expecting option code number.<br/>
dhclient[2321]: option dhcp6.client-id code=<br/>
dhclient[2321]: ^</div>
<div><br/>
we tried many different things like<br/>
option dhcp6.client-id code="\000\001";<br/>
option dhcp6.client-id code="1"</div>
<div>but we never got rid of a error message like above. We deleted the lease-file and then we run dhclient every time</div>
<div> </div>
<div>Now the question is:<br/>
can anyone help how we have to add the line to force dhclient to use DUID-LLT or DUID-LL without a error message?<br/>
Or is there something totally wrong in our way to realize this?<br/>
Any other ideas to force the client to sent the DHCPv6 solicit-message with a client-id type of 1 or type of 3?</div>
<div> </div>
<div>Looking forward for interesting answers.</div>
<div> </div>
<div>Regards<br/>
Uwe</div>
<div> </div>
</div>
</div>
<div class="signature"> </div></div></body></html>