In this article, we'll study a basic, static IPv6 networking. We'll use two computers and a switch.
You can use any Vista, Seven, 8, Windows Server 2008, 2008 R2 or 2012 for this lab of course, you don't need a server OS.
Here is the Network Map we will put in place, step by step, from this subnet, through the next following articles :
For a reminder, the relationship between Link-local and Unique-local scopes :
The first step is putting in place a first static subnet.
we use this link : link ( RFC 4193 algorithm )
or this one : link ( almost RFC 4193 algorithm )
to generate a pseudo-random pseudo-unique-enough ULA ( Unique Locale Address )
in our case, we use this Network ID : fd07:432d:ce02::/48
The first subnet will be : fd07:432d:ce02:3::
Hosts, Switch, and a static ULA subnet
1. Enable IPv6 ping response
As we'll be doing quiet a lot of ping and tracert, the first thing we'll do is enable IPv6 ping response. For this, in Vista, Seven, Windows Server 2008 or 2008 R2 :
Control Panel ) Windows Firewall ) Advanced Firewall )
Incoming Rules ) New Rule )
. All programs
. Protocol : ICMPv6
. All IPs ( default )
. Authorize ( default )
. All network types ( default )
. Name : ICMPv6in
Clients Static IPv6 addresses
The next step will be to setup this first subnet, in the fd07:432d:ce02:3:/64 range, using static IPs.
Note the representation I use on the drawing for the Router : It's a switch inline with a Router, as a usual custommer router is combined with a switch on the lan side. I prefer for theorical clarity to keep on drawing the switching side, as a reminder.
As we won't be networking beyond Router#1 for yet, you can replace Router#1 with a switch, or even use the switching side of a non IPv6-capable router. Just assign a 192.168.3.1 IPv4 address to this Router #1 Lan Side, and disable DHCPv4.
First, we will assign static IP addresses to our two PCs.
. PC#1 will be fd07:432d:ce02:3::210/64
. PC#2 will be fd07:432d:ce02:3::140/64
We set these static IPs using the network card properties, selecting IPv6 and clicking properties again.
Please note that, as we're just using the switching side of our router, this router doesn't need to support IPv6. Just set up its IPv4 address according to the same subnet as PC#1 and PC#2, ie 192.168.3.x, and turn off the Router DHCPv4.
We'll leave the default gateway and DNS fields blank, as we don't use them at this step.
As for the IPv4 addresses, we'll use :
. PC#1 will be 192.168.3.210
. PC#2 will be 192.168.3.140
again, leave the Default Gteway and DNS fields blank.
You can now check the IP addresses by typing >ipconfig or >ipconfig /all.
An fd00::/8 ULA address has now appeared beside the FE80::/64 Link-local address
The 2 PCs can ping each other, usin either the ULA ( Unique Local Address ) or the Link-local Address. Using as an exemple, from PC#2 to PC#1 :
you could use >ping -6 fd07:432d:ce02:3::140 to explicit the will to use IPv6, but the fd00::/8 address already makes this clear
We can check the Routing table using the Command Prompt :
>netsh int ipv6 show route
notice these lines :
No Manual 256 fd07:432d:ce02:3::/64 10 Local Network Connection
No Manual 256 fd07:432d:ce02:3::140/128 10 Local Network Connection
these two routes won't be published ( advertised on the link ) and they were set up manually.
fd07:432d:ce02:3::/64 is the subnet route and fd07:432d:ce02:3::140/128 is the interface route.
10 is the Index of the interface used.
Let's see the other lines :
No Manual 256 ::1/128 1 Loopback Pseudo-Interface 1
is the loopback interface route
No Manual 256 fe80::/64 10 Local Network Connection
No Manual 256 fe80::1728:cd23:8d82:42b/128 10 Local Network Connection
these are the link-local route, and the is the interface link-local route
No Manual 256 ff00::/8 1 Loopback Pseudo-Interface 1
No Manual 256 ff00::/8 10 Local Network Connection
these are the multicast route for each interface.