Dual Stack (IPv4 & IPv6) DHCP in Windows Server 2008
IPv6 is coming and I’m trying to stay ahead of the curve on this one so I’m moving the NAMOS LAN over to an IPv6 network [public services such as DNS, Web and mail are already running on IPv6] which means in the meantime I’m going to have to go through some of the transitional pains.
Armed with a [now depreciated] netblock I set about the practise run for the Plan O’ Doom.
Configuring the scopes is easy and so doesn’t really need to be covered but in order to split my /48 [SixXS subnets are /48] into more usable subnets I cheated on the calculations and used Rhys Koedijk’s IPv6 Subnet calculator.
A word of caution, despite setting up the Scopes and binding static IPv6 addresses on the relevant interfaces the clients were not getting any leases because the Interfaces on the relevant subnets were not configured correctly. You will need to run the following command to get leases working:
netsh interface ipv6 set interface
Unfortunately a day later I had a quick look at the leases on my ‘test’ subnetwork and was greeted by the following:
Thinking that this could be due to my previous experiments I deleted the leases and then logged onto each machine that should have IPv6 enabled and did a release6 & renew6.
Unfortunately there was still one left:
A.J. Anto has an old post which details why these BAD_ADDRESS’s should be showing up but that doesn’t seem to be the case here.
A bit more research found a Hyper V’d Vista machine that I’d forgotten about which had a 12 day lease.
Interestingly even if you assign a static IPv6 address to an interface Windows Server 2008 (and probably Vista too) still request an IP from DHCP:
The next IPv6 experiment is a SixXS tunnel to a Juniper Netscreen 5GT with the LAN and Wireless segments having ‘real’ IPv6 addresses. - Keep an eye out for the “NetworksAreMadeOfString IPv6″ SSID.
November 3rd, 2008 at 12:28 am
[...] the initial tests over it was time to actually move over to ‘real’ IPv6 [...]