IPv6 test lab tasks
The following tasks are designed to take you through the common IPv6 configurations in Windows by using the test lab infrastructure configured in Setting up the infrastructure
| • | Link-local ping |
| • | Creating a static routing infrastructure |
| • | Using name resolution |
| • | Using anonymous addresses |
Note
| • | The following instructions are for configuring a test lab using a minimum number of computers. Individual computers are needed to separate the services provided on the network and to clearly show the desired functionality. This configuration is neither designed to reflect best practices nor is it designed to reflect a desired or recommended configuration for a production network. The configuration, including IP addresses and all other configuration parameters, is designed only to work on a separate test lab network. |
Link-local ping
To ping a host using link-local addresses and view the entries created in the neighbor and route caches, complete the following steps:
1. | On DNS1, type the ipv6 if command to obtain the link-local address of the interface named Local Area Connection. |
2. | On CLIENT1, type the ipv6 if command to obtain the link-local address and interface identifier of the interface named Local Area Connection. |
3. | On CLIENT1, type the following command to ping the link-local address of DNS1: ping6 DNS1LinkLocalAddress%InterfaceIdentifier For example, if the link-local address of DNS1 is FE80::2AA:FF:FE9D:10C5, and the interface identifier for the Local Area Connection interface on CLIENT1 is 3, the command is: ping6 FE80::2AA:FF:FE9D:10C5%3 |
4. | On CLIENT1, type the following command: ipv6 nc to view the entry in the CLIENT1 neighbor cache for DNS1. For more information, see Neighbor Discovery (ND) |
5. | On CLIENT1, type the following command: ipv6 rc to view the entry in the CLIENT1 route cache for DNS1. For more information, see Neighbor Discovery (ND) |
6. | On CLIENT1, type the following command: ipv6 rt to view the entries in the CLIENT1 routing table. For more information, see The IPv6 routing table |
Creating a static routing infrastructure
To configure a static routing infrastructure so that all test lab nodes are reachable using IPv6 traffic, complete the following steps:
1. | On ROUTER1, type the ipv6 if command to obtain the link-local addresses and interface index numbers of the Subnet 1 and Subnet 2 interfaces. | ||||||
2. | On ROUTER1, type the following commands: ipv6 ifc Subnet1InterfaceIndex forwards advertises ipv6 ifc Subnet2InterfaceIndex forwards advertises ipv6 rtu FEC0:0:0:1::/64 Subnet1InterfaceIndex publish ipv6 rtu FEC0:0:0:2::/64 Subnet2InterfaceIndex publish ipv6 rtu ::/0 Subnet2InterfaceIndex/ROUTER2AddressOnSubnet2 publish where:
For example, if the Subnet 1 interface index is 4, the Subnet 2 interface index is 3, and the link-local address of the ROUTER2 Subnet 2 interface is FE80::2AA:FF:FE87:4D5C, the commands should be typed as follows: ipv6 ifc 4 forwards advertises ipv6 ifc 3 forwards advertises ipv6 rtu FEC0:0:0:1::/64 4 publish ipv6 rtu FEC0:0:0:2::/64 3 publish ipv6 rtu ::/0 3/FE80::2AA:FF:FE87:4D5C publish | ||||||
3. | On ROUTER2, type the ipv6 if command to obtain the link-local addresses and interface index numbers of the Subnet 2 and Subnet 3 interfaces. | ||||||
4. | On ROUTER2, type the following commands: ipv6 ifc Subnet2InterfaceIndex forwards advertises ipv6 ifc Subnet3InterfaceIndex forwards advertises ipv6 rtu FEC0:0:0:2::/64 Subnet2InterfaceIndex publish ipv6 rtu FEC0:0:0:3::/64 Subnet3InterfaceIndex publish ipv6 rtu ::/0 Subnet2InterfaceIndex/ROUTER1AddressOnSubnet2 publish For example, if the Subnet 2 interface index is 4, the Subnet 3 interface index is 3, and the link-local address of the ROUTER1 Subnet 2 interface is FE80::2AA:FF:FE9A:203F, the commands should be typed as follows: ipv6 ifc 4 forwards advertises ipv6 ifc 3 forwards advertises ipv6 rtu FEC0:0:0:2::/64 4 publish ipv6 rtu FEC0:0:0:3::/64 3 publish ipv6 rtu ::/0 4/FE80::2AA:FF:FE9A:203F publish | ||||||
5. | On CLIENT1, type the ipv6 if command to view a new address on the LAN interface that is based on the site-local prefix of FEC0:0:0:1::/64. | ||||||
6. | On CLIENT1, type the ipv6 rt command to view new routes for FEC0:0:0:1::/64, FEC0:0:0:2::/64, and ::/0. | ||||||
7. | On CLIENT2, type the ipv6 if command to view a new address on the LAN interface that is based on the site-local prefix of FEC0:0:0:3::/64. | ||||||
8. | On CLIENT2, type the ipv6 rt command to view new routes for FEC0:0:0:2::/64, FEC0:0:0:3::/64, and ::/0. | ||||||
9. | On CLIENT1, type the ping6 command to ping the CLIENT2 site-local address as follows: ping6 CLIENT2SiteLocalAddress | ||||||
10. | On CLIENT1, type the tracert6 command with the -d option to trace the route between CLIENT1 and CLIENT2: tracert6 -d CLIENT2SiteLocalAddress In the tracert6 display, you can view the link-local address of the Subnet 1 interface for ROUTER1 and the link-local address of the Subnet 2 interface for ROUTER2. | ||||||
11. | On ROUTER1, type the following commands: ipv6 nc to view the entries in the ROUTER1 neighbor cache for CLIENT1 and ROUTER2. ipv6 rc to view the entries in the ROUTER1 route cache for DNS1 and ROUTER2. |
Note
| • | The IPv6 protocol for Windows currently advertises off-link prefixes in Router Advertisement messages. Prefix Information options for off-link prefixes become routes in the routing table of the receiving host. |
Using name resolution
To configure DNS and the local Hosts file to resolve names to IPv6 addresses, complete the following steps:
1. | On DNS1, create a zone named testlab.microsoft.com. For more information, see To add a forward lookup zone |
2. | Create a AAAA (quad-A) resource record for CLIENT2 with the DNS name client2.testlab.microsoft.com for its site-local IPv6 address. For more information, see To add a resource record to a zone For example, for the CLIENT2 site-local address of FEC0::3:260:8FF:FE52:F9D8, the contents of the AAAA resource record are: Name: client2.testlab.microsoft.com Address: FEC0::3:260:8FF:FE52:F9D8 |
3. | On CLIENT1, type the following command: ping6 client2.testlab.microsoft.com The name client2.testlab.microsoft.com is resolved to its site-local address by sending a DNS query to DNS1. |
4. | On CLIENT2, create the following entry in the Hosts file (located in the systemroot\System32\Drivers\Etc folder): client1.testlab.microsoft.com Client1SiteLocalAddress |
5. | On CLIENT2, type the following command: ping6 client1.testlab.microsoft.com The name client1.testlab.microsoft.com is resolved to its site-local address by using the local Hosts file. |
Using anonymous addresses
To use anonymous addresses for global address prefixes, complete the following steps:
1. | On ROUTER1, type the following command: ipv6 rtu 3000:0:0:1::/64 Subnet1InterfaceIndex publish where Subnet1InterfaceIndex is the interface index of the ROUTER1 interface on Subnet 1. For example, if the Subnet 1 interface index is 4, the command is: ipv6 rtu 3000:0:0:1::/64 4 publish |
2. | On CLIENT1, type the ipv6 if command to view a new address on the LAN interface that is based on the global prefix of 3000:0:0:1::/64. There should be two addresses that are based on the 3000:0:0:1::/64 prefix. One address uses an interface identifier that is based on the EUI-64 address of the interface. The other address is an anonymous address from which the interface identifier is randomly derived. For more information, see IPv6 interface identifiers |
3. | On ROUTER1, type the following command: ipv6 rtu 3000:0:0:1::/64 Subnet1InterfaceIndex life 0 where Subnet1InterfaceIndex is the interface index of the ROUTER1 interface on Subnet 1. For example, if the Subnet 1 interface index is 4, the command is: ipv6 rtu 3000:0:0:1::/64 4 life 0 This command removes the global prefix from the ROUTER1 routing table and prevents ROUTER1 from advertising it on its interfaces. |