issues with ipv6 and DUID

[Cory Coager]

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?

On 04/04/2013 06:35 PM, Cory Coager wrote:
> 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.
>
> Here is the server logs for a release and renew:
> Apr  4 22:26:48 server dhcpd: Release message from 
> fe80::5054:ff:feea:db36 port 546, transaction ID 0x88BFCA00
> 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.
> Apr  4 22:26:48 server dhcpd: Sending Reply to fe80::5054:ff:feea:db36 
> port 546
> Apr  4 22:26:49 server dhcpd: Solicit message from 
> fe80::5054:ff:feea:db36 port 546, transaction ID 0x9E590C00
> Apr  4 22:26:49 server dhcpd: Sending Advertise to 
> fe80::5054:ff:feea:db36 port 546
> Apr  4 22:26:50 server dhcpd: Request message from 
> fe80::5054:ff:feea:db36 port 546, transaction ID 0x6366E00
> Apr  4 22:26:50 server dhcpd: Sending Reply to fe80::5054:ff:feea:db36 
> port 546
>
> I haven't tried a packet capture yet.
>
> I just tried with a /64 subnet, didn't make a difference.
>
> 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.
>
> On 04/04/2013 05:23 PM, Steven Carr wrote:
>> 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?
>>
>> 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.
>>
>> Steve
>>
>>
>>
>> On 2 April 2013 23:10, Cory Coager <ccoager at gmail.com 
>> <mailto:ccoager at gmail.com>> wrote:
>>
>>     On 04/01/2013 09:15 PM, Cory Coager wrote:
>>
>>         On 04/01/2013 10:03 AM, Simon Hobson wrote:
>>
>>             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.
>>
>>         Did you see the log I posted?  I'm already do this and it
>>         doesn't seem to work.
>>
>>
>>     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.
>>
>>     Has anyone gotten this to work?  Is this a bug perhaps?
>>
>>     I'm using version 4.1.ESV-R4-0ubuntu5.6 on Ubuntu 12.04.
>>
>>     _______________________________________________
>>     dhcp-users mailing list
>>     dhcp-users at lists.isc.org <mailto:dhcp-users at lists.isc.org>
>>     https://lists.isc.org/mailman/listinfo/dhcp-users
>>
>>
>>
>>
>> _______________________________________________
>> dhcp-users mailing list
>> dhcp-users at lists.isc.org
>> https://lists.isc.org/mailman/listinfo/dhcp-users
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/dhcp-users/attachments/20130404/cdd2cb50/attachment.html>