DHCP6 getting strange lease.

[mrzaz]

Hello,

I'm quite new in the IPv6 arena but have tested some with the IPv6 in pfsense against Win7 machine.

I have managed to get both Unmanaged (stateless_autoconfig) to work and also Managed (with DHCP6).
(including ping and FTP to a IPv6 aware FTP-server on one of the machines working OK)

However I stumbled on a strange thing that I can't figure out if it is fault from my side or something fishy!

My LAN IPv6 IP is: (Using Unique Local IP)
fd00::10:0a00:27ff:fe6f:e98e / 64

LinkLocal:
fe80::a00:27ff:fe6f:e98e

Router Advertisements = Managed
Enable DHCPv6 = YES
Subnet fd00:0:0:10:0:0:0:0
Subnet mask 64 bits
Available range fd00:0:0:10:0:0:0:1 - fd00:0:0:10:ffff:ffff:ffff:ffff

Just for testing I made the following range:
fd00:0:0:10:FFFF:0:9999:1     TO     fd00:0:0:10:FFFF:0:9999:2

BUT has also tested with
fd00:0:0:10:0:0:0:1     TO     fd00:0:0:10:0:0:0:9

Prefix Delegation = blank (default)

RESULT:
The client always get  IPv6 Address. . . . . . . . . . . : fd00:0:0:10::2000
regardless what I put in the "Range" settings above.   Have tested 2 different range settings but same result.
And the IP assigned is not within the range.

No.     Time        Source                Destination           Protocol Length Info
     1 0.000000    fe80::39cf:c6b0:4657:c4ed ff02::1:2             DHCPv6   147    Solicit XID: 0xb3d717 CID: 00010001153faa28f46d04063ba8
     2 0.001531    fe80::a00:27ff:fe6f:e98e fe80::39cf:c6b0:4657:c4ed DHCPv6   166    Advertise XID: 0xb3d717 IAA: fd00:0:0:10::2000 CID: 00010001153faa28f46d04063ba8
     3 1.000891    fe80::39cf:c6b0:4657:c4ed ff02::1:2             DHCPv6   193    Request XID: 0xb3d717 CID: 00010001153faa28f46d04063ba8 IAA: fd00:0:0:10::2000
     4 1.003097    fe80::a00:27ff:fe6f:e98e fe80::39cf:c6b0:4657:c4ed DHCPv6   166    Reply XID: 0xb3d717 IAA: fd00:0:0:10::2000 CID: 00010001153faa28f46d04063ba8

LinkLocal IP of the Client:
fe80::39cf:c6b0:4657:c4ed

The advertise from the PfSense is:
   Identity Association for Non-temporary Address
       Option: Identity Association for Non-temporary Address (3)
       Length: 40
       Value: 0ef46d04000000000000000000050018fd00000000000010…
       IAID: 0ef46d04
       T1: 0
       T2: 0
       IA Address:  fd00:0:0:10::2000
           Option: IA Address (5)
           Length: 24
           Value: fd0000000000001000000000000020000000119400001c20
           IPv6 address: fd00:0:0:10::2000
           Preferred lifetime: 4500
           Valid lifetime: 7200

Could someone explain why I am getting this strange behaviour ?

I'm currently testing on a somewhat old release and will update and test again but still.
Current version: 2.1-BETA0  Built On: Wed May 30 19:35:22 EDT 2012

UPDATE 2012-06-12: I have now tested on latest build with same result.
2.1-BETA0  Built On: Tue Jun 12 05:15:27 EDT 2012

//Dan Lundqvist

[databeestje]

Strange, that's the range I normally create for interfaces which are setup as "track6".

Maybe it's somehow not cleaning out a variable. I'll investigate.

[mrzaz]

Hi,

Thanks for the response. :-)

Do you think that you will have a correction for the tonight's build or later ?
Just to know when I should test if the problem is gone and you could put that bug to rest. :-)

Could you make a note here when a correction has been included and then I'll upgrade and test
again to verify that the problem has been solved.

Best regards
Dan Lundqvist

[mrzaz]

I have done a check now and from what I could see it is giving correct leases now within the span defined. :-)
Using build Sat Jun 16 14:16:56 EDT 2012

I have switched to a non Unique Local Addressing scheme to real Internet IPv6 addresses now so i have
my own /64 Routed IPv6 Prefixes.  I have selected a ::2 to ::ffff span for the DHCP and it seems to give out
within this scope to the clients when setting to Managed mode.

So I think this problem has been resolved ?
Unless there is a specific problem when using fd00:….  addresses.

Best regards
Dan Lundqvist
Stockholm, Sweden