<div dir="ltr"><a href="http://linuxreviews.org/man/dhclient/" target="_blank">http://linuxreviews.org/man/dhclient/</a><br><div class="gmail_quote"><div dir="ltr"><dl compact><dt><b>-D</b><i> LL or LLT</i>
</dt><dd>
Override the default when selecting the type of DUID to use. By default,
DHCPv6 <b>dhclient</b> creates an identifier based on the link-layer address
(DUID-LL) if it is running in stateless mode (with <b>-S</b>, not
requesting an address), or it creates an identifier based on the
link-layer address plus a timestamp (DUID-LLT) if it is running in
stateful mode (without <b>-S</b>, requesting an address). <b>-D</b>
overrides this default, with a value of either <i>LL</i> or <i>LLT</i>.
</dd></dl><div><div class="h5"><div class="gmail_extra"><br><br><br><div class="gmail_quote">On 4 April 2013 23:52, Cory Coager <span dir="ltr"><<a href="mailto:ccoager@gmail.com" target="_blank">ccoager@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
So the packet capture was a great help. Looks like the client is
using DUID-LLT which always changes. How do I tell the client to
use DUID-LL instead?<div><div><br>
<br>
<div>On 04/04/2013 06:35 PM, Cory Coager
wrote:<br>
</div>
<blockquote type="cite">
Client OS is Ubuntu 12.04, client version 4.1.ESV-R4-0ubuntu5.6.
It seems to support ipv6 as I can get an ipv6 address from the
server and basic networking seems to function.<br>
<br>
Here is the server logs for a release and renew:<br>
Apr 4 22:26:48 server dhcpd: Release message from
fe80::5054:ff:feea:db36 port 546, transaction ID 0x88BFCA00<br>
Apr 4 22:26:48 server dhcpd: Client
00:01:00:01:18:e8:e9:79:52:54:00:ea:db:36 releases address
fde8:cceb:ccfe:b5b4:238a:691f:17d3:24ae, which is not leased to
it.<br>
Apr 4 22:26:48 server dhcpd: Sending Reply to
fe80::5054:ff:feea:db36 port 546<br>
Apr 4 22:26:49 server dhcpd: Solicit message from
fe80::5054:ff:feea:db36 port 546, transaction ID 0x9E590C00<br>
Apr 4 22:26:49 server dhcpd: Sending Advertise to
fe80::5054:ff:feea:db36 port 546<br>
Apr 4 22:26:50 server dhcpd: Request message from
fe80::5054:ff:feea:db36 port 546, transaction ID 0x6366E00<br>
Apr 4 22:26:50 server dhcpd: Sending Reply to
fe80::5054:ff:feea:db36 port 546<br>
<br>
I haven't tried a packet capture yet.<br>
<br>
I just tried with a /64 subnet, didn't make a difference.<br>
<br>
fde8:cceb:ccfe:b5b4:238a:691f:17d3:2440 is the DHCP server which
is also serving DNS. There is no router involved in this subnet,
all on the same vlan.<br>
<br>
<div>On 04/04/2013 05:23 PM, Steven Carr
wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div>
<div>What client are you using? Does this client fully
support DHCPv6? You've indicated what the client log shows
but what does the server logs show? What messages can you
see in a packet capture?<br>
<br>
</div>
There was also some discussion a while back (possibly not on
this list) but about potential issues with non /64 subnet
sizes, in that the OS stack may not support anything other
than a /64 given that for native SLAAC to work it requires
/64.<br>
<br>
</div>
Steve<br>
<br>
</div>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">On 2 April 2013 23:10, Cory Coager <span dir="ltr"><<a href="mailto:ccoager@gmail.com" target="_blank">ccoager@gmail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div>On 04/01/2013 09:15 PM, Cory Coager wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"> On
04/01/2013 10:03 AM, Simon Hobson wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
AFAIK, the only reliable way of getting it is to
wait for the client to boot, and get the DUID from
the lease created (or the logfile ?). On a busy
network, I'm not sure how you'd identify that
specific client.<br>
</blockquote>
Did you see the log I posted? I'm already do this and
it doesn't seem to work.<br>
</blockquote>
<br>
</div>
I just tried this again. The DUID from the DHCP logs
matches up with what I have in the config file for a fixed
address. However, it is assigning the client a random IP
still.<br>
<br>
Has anyone gotten this to work? Is this a bug perhaps?<br>
<br>
I'm using version 4.1.ESV-R4-0ubuntu5.6 on Ubuntu 12.04.
<div>
<div><br>
_______________________________________________<br>
dhcp-users mailing list<br>
<a href="mailto:dhcp-users@lists.isc.org" target="_blank">dhcp-users@lists.isc.org</a><br>
<a href="https://lists.isc.org/mailman/listinfo/dhcp-users" target="_blank">https://lists.isc.org/mailman/listinfo/dhcp-users</a><br>
</div>
</div>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset></fieldset>
<br>
<pre>_______________________________________________
dhcp-users mailing list
<a href="mailto:dhcp-users@lists.isc.org" target="_blank">dhcp-users@lists.isc.org</a>
<a href="https://lists.isc.org/mailman/listinfo/dhcp-users" target="_blank">https://lists.isc.org/mailman/listinfo/dhcp-users</a></pre>
</blockquote>
<br>
</blockquote>
<br>
</div></div></div>
</blockquote></div><br></div></div></div></div>
</div><br></div>