With the initial tests over it was time to actually move over to 'real' IPv6 addresses. After applying for a tunnel from SixXS it was time to set it up. Unfortunately none of my JUNOS or Cisco IOS images have IPv6 support so rather than buying another 2600XM I decided to use the Windows Server 2008 server that performs IPv6 DHCP as the router. The advice for setting up a tunnel on the Wiki only covers up to Windows Server 2003 and is below: netsh interface ipv6 install netsh interface ipv6 add v6v4tunnel SixXS [Your IPv4 Endpoint] [PoP IPv4 Endpoint] netsh interface ipv6 add ...

We already know that disabling IPv6 on a 2008 & Exchange 2007 server breaks things but what if we go IPv6 only? IPv6 Only Domain Controllers: The installation didn't cause any trouble but after initially logging on and running a DCDiag we see this: It turns out that the install of the DNS Server had set the NIC's properties to be ::1 but the DNS Server was only listening on the Static Site Local address FEC0::2 and its self assigned Link Local. This of course caused all DNS reliant checks to fail and cause a whole world of pain.           Changing the ...

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 ...