- •For Web Developers
- •Contents at a Glance
- •Table of Contents
- •List of Figures
- •List of Tables
- •Foreword
- •Why Does Microsoft Care About IPv6?
- •Preface
- •Acknowledgments
- •Introduction
- •Who Should Read This Book
- •What You Should Know Before Reading This Book
- •Organization of This Book
- •Appendices of This Book
- •About the Companion CD-ROM
- •System Requirements
- •IPv6 Protocol and Windows Product Versions
- •A Special Note to Teachers and Instructors
- •Disclaimers and Support
- •Technical Support
- •Limitations of IPv4
- •Consequences of the Limited IPv4 Address Space
- •Features of IPv6
- •New Header Format
- •Large Address Space
- •Stateless and Stateful Address Configuration
- •IPsec Header Support Required
- •Better Support for Prioritized Delivery
- •New Protocol for Neighboring Node Interaction
- •Extensibility
- •Comparison of IPv4 and IPv6
- •IPv6 Terminology
- •The Case for IPv6 Deployment
- •IPv6 Solves the Address Depletion Problem
- •IPv6 Solves the Disjoint Address Space Problem
- •IPv6 Solves the International Address Allocation Problem
- •IPv6 Restores End-to-End Communication
- •IPv6 Uses Scoped Addresses and Address Selection
- •IPv6 Has More Efficient Forwarding
- •IPv6 Has Support for Security and Mobility
- •Testing for Understanding
- •Architecture of the IPv6 Protocol for Windows Server 2008 and Windows Vista
- •Features of the IPv6 Protocol for Windows Server 2008 and Windows Vista
- •Installed, Enabled, and Preferred by Default
- •Basic IPv6 Stack Support
- •IPv6 Stack Enhancements
- •GUI and Command-Line Configuration
- •Integrated IPsec Support
- •Windows Firewall Support
- •Temporary Addresses
- •Random Interface IDs
- •DNS Support
- •Source and Destination Address Selection
- •Support for ipv6-literal.net Names
- •LLMNR
- •PNRP
- •Literal IPv6 Addresses in URLs
- •Static Routing
- •IPv6 over PPP
- •DHCPv6
- •ISATAP
- •Teredo
- •PortProxy
- •Application Support
- •Application Programming Interfaces
- •Windows Sockets
- •Winsock Kernel
- •Remote Procedure Call
- •IP Helper
- •Win32 Internet Extensions
- •Windows Filtering Platform
- •Manually Configuring the IPv6 Protocol
- •Configuring IPv6 Through the Properties of Internet Protocol Version 6 (TCP/IPv6)
- •Configuring IPv6 with the Netsh.exe Tool
- •Disabling IPv6
- •IPv6-Enabled Tools
- •Ipconfig
- •Route
- •Ping
- •Tracert
- •Pathping
- •Netstat
- •Displaying IPv6 Configuration with Netsh
- •Netsh interface ipv6 show interface
- •Netsh interface ipv6 show address
- •Netsh interface ipv6 show route
- •Netsh interface ipv6 show neighbors
- •Netsh interface ipv6 show destinationcache
- •References
- •Testing for Understanding
- •The IPv6 Address Space
- •IPv6 Address Syntax
- •Compressing Zeros
- •IPv6 Prefixes
- •Types of IPv6 Addresses
- •Unicast IPv6 Addresses
- •Global Unicast Addresses
- •Topologies Within Global Addresses
- •Local-Use Unicast Addresses
- •Unique Local Addresses
- •Special IPv6 Addresses
- •Transition Addresses
- •Multicast IPv6 Addresses
- •Solicited-Node Address
- •Mapping IPv6 Multicast Addresses to Ethernet Addresses
- •Anycast IPv6 Addresses
- •Subnet-Router Anycast Address
- •IPv6 Addresses for a Host
- •IPv6 Addresses for a Router
- •Subnetting the IPv6 Address Space
- •Step 1: Determining the Number of Subnetting Bits
- •Step 2: Enumerating Subnetted Address Prefixes
- •IPv6 Interface Identifiers
- •EUI-64 Address-Based Interface Identifiers
- •Temporary Address Interface Identifiers
- •IPv4 Addresses and IPv6 Equivalents
- •References
- •Testing for Understanding
- •Structure of an IPv6 Packet
- •IPv4 Header
- •IPv6 Header
- •Values of the Next Header Field
- •Comparing the IPv4 and IPv6 Headers
- •IPv6 Extension Headers
- •Extension Headers Order
- •Hop-by-Hop Options Header
- •Destination Options Header
- •Routing Header
- •Fragment Header
- •Authentication Header
- •Encapsulating Security Payload Header and Trailer
- •Upper-Layer Checksums
- •References
- •Testing for Understanding
- •ICMPv6 Overview
- •Types of ICMPv6 Messages
- •ICMPv6 Header
- •ICMPv6 Error Messages
- •Destination Unreachable
- •Packet Too Big
- •Time Exceeded
- •Parameter Problem
- •ICMPv6 Informational Messages
- •Echo Request
- •Echo Reply
- •Comparing ICMPv4 and ICMPv6 Messages
- •Path MTU Discovery
- •Changes in PMTU
- •References
- •Testing for Understanding
- •Neighbor Discovery Overview
- •Neighbor Discovery Message Format
- •Neighbor Discovery Options
- •Source and Target Link-Layer Address Options
- •Prefix Information Option
- •Redirected Header Option
- •MTU Option
- •Route Information Option
- •Neighbor Discovery Messages
- •Router Solicitation
- •Router Advertisement
- •Neighbor Solicitation
- •Neighbor Advertisement
- •Redirect
- •Summary of Neighbor Discovery Messages and Options
- •Neighbor Discovery Processes
- •Conceptual Host Data Structures
- •Address Resolution
- •Neighbor Unreachability Detection
- •Duplicate Address Detection
- •Router Discovery
- •Redirect Function
- •Host Sending Algorithm
- •References
- •Testing for Understanding
- •MLD and MLDv2 Overview
- •IPv6 Multicast Overview
- •Host Support for Multicast
- •Router Support for Multicast
- •MLD Packet Structure
- •MLD Messages
- •Multicast Listener Query
- •Multicast Listener Report
- •Multicast Listener Done
- •Summary of MLD
- •MLDv2 Packet Structure
- •MLDv2 Messages
- •The Modified Multicast Listener Query
- •MLDv2 Multicast Listener Report
- •Summary of MLDv2
- •MLD and MLDv2 Support in Windows Server 2008 and Windows Vista
- •References
- •Testing for Understanding
- •Address Autoconfiguration Overview
- •Types of Autoconfiguration
- •Autoconfigured Address States
- •Autoconfiguration Process
- •DHCPv6
- •DHCPv6 Messages
- •DHCPv6 Stateful Message Exchange
- •DHCPv6 Stateless Message Exchange
- •DHCPv6 Support in Windows
- •IPv6 Protocol for Windows Server 2008 and Windows Vista Autoconfiguration Specifics
- •Autoconfigured Addresses for the IPv6 Protocol for Windows Server 2008 and Windows Vista
- •References
- •Testing for Understanding
- •Name Resolution for IPv6
- •DNS Enhancements for IPv6
- •LLMNR
- •Source and Destination Address Selection
- •Source Address Selection Algorithm
- •Destination Address Selection Algorithm
- •Example of Using Address Selection
- •Hosts File
- •DNS Resolver
- •DNS Server Service
- •DNS Dynamic Update
- •Source and Destination Address Selection
- •LLMNR Support
- •Support for ipv6-literal.net Names
- •Peer Name Resolution Protocol
- •References
- •Testing for Understanding
- •Routing in IPv6
- •IPv6 Routing Table Entry Types
- •Route Determination Process
- •Strong and Weak Host Behaviors
- •Example IPv6 Routing Table for Windows Server 2008 and Windows Vista
- •End-to-End IPv6 Delivery Process
- •IPv6 on the Sending Host
- •IPv6 on the Router
- •IPv6 on the Destination Host
- •IPv6 Routing Protocols
- •Overview of Dynamic Routing
- •Routing Protocol Technologies
- •Routing Protocols for IPv6
- •Static Routing with the IPv6 Protocol for Windows Server 2008 and Windows Vista
- •Configuring Static Routing with Netsh
- •Configuring Static Routing with Routing and Remote Access
- •Dead Gateway Detection
- •References
- •Testing for Understanding
- •Overview
- •Node Types
- •IPv6 Transition Addresses
- •Transition Mechanisms
- •Using Both IPv4 and IPv6
- •IPv6-over-IPv4 Tunneling
- •DNS Infrastructure
- •Tunneling Configurations
- •Router-to-Router
- •Host-to-Router and Router-to-Host
- •Host-to-Host
- •Types of Tunnels
- •PortProxy
- •References
- •Testing for Understanding
- •ISATAP Overview
- •ISATAP Tunneling
- •ISATAP Tunneling Example
- •ISATAP Components
- •Router Discovery for ISATAP Hosts
- •Resolving the Name “ISATAP”
- •Using the netsh interface isatap set router Command
- •ISATAP Addressing Example
- •ISATAP Routing
- •ISATAP Communication Examples
- •ISATAP Host to ISATAP Host
- •ISATAP Host to IPv6 Host
- •Configuring an ISATAP Router
- •References
- •Testing for Understanding
- •6to4 Overview
- •6to4 Tunneling
- •6to4 Tunneling Example
- •6to4 Components
- •6to4 Addressing Example
- •6to4 Routing
- •6to4 Support in Windows Server 2008 and Windows Vista
- •6to4 Host/Router Support
- •6to4 Router Support
- •6to4 Communication Examples
- •6to4 Host to 6to4 Host/Router
- •6to4 Host to IPv6 Host
- •Example of Using ISATAP and 6to4 Together
- •Part 1: From ISATAP Host A to 6to4 Router A
- •Part 2: From 6to4 Router A to 6to4 Router B
- •Part 3: From 6to4 Router B to ISATAP Host B
- •References
- •Testing for Understanding
- •Introduction to Teredo
- •Benefits of Using Teredo
- •Teredo Support in Microsoft Windows
- •Teredo and Protection from Unsolicited Incoming IPv6 Traffic
- •Network Address Translators (NATs)
- •Teredo Components
- •Teredo Client
- •Teredo Server
- •Teredo Relay
- •Teredo Host-Specific Relay
- •The Teredo Client and Host-Specific Relay in Windows
- •Teredo Addresses
- •Teredo Packet Formats
- •Teredo Data Packet Format
- •Teredo Bubble Packets
- •Teredo Indicators
- •Teredo Routing
- •Routing for the Teredo Client in Windows
- •Teredo Processes
- •Initial Configuration for Teredo Clients
- •Maintaining the NAT Mapping
- •Initial Communication Between Teredo Clients on the Same Link
- •Initial Communication Between Teredo Clients in Different Sites
- •Initial Communication from a Teredo Client to a Teredo Host-Specific Relay
- •Initial Communication from a Teredo Host-Specific Relay to a Teredo Client
- •Initial Communication from a Teredo Client to an IPv6-Only Host
- •Initial Communication from an IPv6-Only Host to a Teredo Client
- •References
- •Testing for Understanding
- •IPv6 Security Considerations
- •Authorization for Automatically Assigned Addresses and Configurations
- •Recommendations
- •Protection of IPv6 Packets
- •Recommendations
- •Host Protection from Scanning and Attacks
- •Address Scanning
- •Port Scanning
- •Recommendations
- •Control of What Traffic Is Exchanged with the Internet
- •Recommendations
- •Summary
- •References
- •Testing for Understanding
- •Introduction
- •Planning for IPv6 Deployment
- •Platform Support for IPv6
- •Application Support for IPv6
- •Unicast IPv6 Addressing
- •Tunnel-Based IPv6 Connectivity
- •Native IPv6 Connectivity
- •Name Resolution with DNS
- •DHCPv6
- •Host-Based Security and IPv6 Traffic
- •Prioritized Delivery for IPv6 Traffic
- •Deploying IPv6
- •Set Up an IPv6 Test Network
- •Begin Application Migration
- •Configure DNS Infrastructure to Support AAAA Records and Dynamic Updates
- •Deploy a Tunneled IPv6 Infrastructure with ISATAP
- •Upgrade IPv4-Only Hosts to IPv6/IPv4 Hosts
- •Begin Deploying a Native IPv6 Infrastructure
- •Connect Portions of Your Intranet over the IPv4 Internet
- •Connect Portions of Your Intranet over the IPv6 Internet
- •Summary
- •References
- •Testing for Understanding
- •Basic Structure of IPv6 Packets
- •LAN Media
- •Ethernet: Ethernet II
- •Ethernet: IEEE 802.3 SNAP
- •Token Ring: IEEE 802.5 SNAP
- •FDDI
- •IEEE 802.11
- •WAN Media
- •Frame Relay
- •ATM: Null Encapsulation
- •ATM: SNAP Encapsulation
- •IPv6 over IPv4
- •References
- •Added Constants
- •Address Data Structures
- •in6_addr
- •sockaddr_in6
- •sockaddr_storage
- •Wildcard Addresses
- •in6addr_loopback and IN6ADDR_LOOPBACK_INIT
- •Core Sockets Functions
- •Name-to-Address Translation
- •Address-to-Name Translation
- •Using getaddrinfo
- •Address Conversion Functions
- •Socket Options
- •New Macros
- •References
- •General
- •Addressing
- •Applications
- •Sockets API
- •Transport Layer
- •Internet Layer
- •Network Layer Security
- •Link Layer
- •Routing
- •IPv6 Transition Technologies
- •Chapter 1: Introduction to IPv6
- •Chapter 2: IPv6 Protocol for Windows Server 2008 and Windows Vista
- •Chapter 3: IPv6 Addressing
- •Chapter 4: The IPv6 Header
- •Chapter 5: ICMPv6
- •Chapter 6: Neighbor Discovery
- •Chapter 8: Address Autoconfiguration
- •Chapter 9: IPv6 and Name Resolution
- •Chapter 10: IPv6 Routing
- •Chapter 11: IPv6 Transition Technologies
- •Chapter 12: ISATAP
- •Chapter 13: 6to4
- •Chapter 14: Teredo
- •Chapter 15: IPv6 Security Considerations
- •Chapter 16: Deploying IPv6
- •IPv6 Test Lab Setup
- •CLIENT1
- •ROUTER1
- •ROUTER2
- •CLIENT2
- •IPv6 Test Lab Tasks
- •Performing Link-Local Pings
- •Enabling Native IPv6 Connectivity on Subnet 1
- •Configuring ISATAP
- •Configuring Native IPv6 Connectivity for All Subnets
- •Using Name Resolution
- •Configuring an IPv6-Only Routing Infrastructure
- •Overview
- •Mobile IPv6 Components
- •Mobile IPv6 Transport Layer Transparency
- •Mobile IPv6 Messages and Options
- •Mobility Header and Messages
- •Type 2 Routing Header
- •Home Address Option for the Destination Options Header
- •ICMPv6 Messages for Mobile IPv6
- •Modifications to Neighbor Discovery Messages and Options
- •Mobile IPv6 Data Structures
- •Binding Cache
- •Binding Update List
- •Home Agents List
- •Correspondent Registration
- •Return Routability Procedure
- •Detecting Correspondent Nodes That Are Not Mobile IPv6–Capable
- •Mobile IPv6 Message Exchanges
- •Data Between a Mobile Node and a Correspondent Node
- •Binding Maintenance
- •Home Agent Discovery
- •Mobile Prefix Discovery
- •Mobile IPv6 Processes
- •Attaching to the Home Link
- •Moving from the Home Link to a Foreign Link
- •Moving to a New Foreign Link
- •Returning Home
- •Mobile IPv6 Host Sending Algorithm
- •Mobile IPv6 Host Receiving Algorithm
- •References
- •Glossary
- •Index
- •About the Author
- •System Requirements
446 Understanding IPv6, Second Edition
This tests whether IPv4 packets can be forwarded between CLIENT2 on Subnet 3 and CLIENT1 on Subnet 1.
At this point in the test lab configuration, there is an IPv4-only routing infrastructure. IPv4 traffic can be sent and received by any node on the test lab network. All the nodes have IPv6 installed, but there is no native IPv6 routing or autoconfiguration of global or unique local address prefixes. Therefore, IPv6 nodes can communicate only with each other if they are connected to the same subnet and can use only link-local addresses. For example, CLIENT1 can use link-local addresses to communicate with DNS1 and ROUTER1, but it cannot use link-local addresses to communicate with ROUTER2 or CLIENT2.
IPv6 Test Lab Tasks
The following sections are designed to take you through the common IPv6 tasks and configurations to transform the IPv4-only test lab network to an IPv6-only test lab network:
■Performing link-local pings
■Enabling native IPv6 connectivity on Subnet 1
■Configuring ISATAP
■Configuring native IPv6 connectivity for all subnets
■Using name resolution
■Configuring an IPv6-only routing infrastructure
The last step is optional because most intranets in the near future will not be IPv6-only networks, but IPv6-capable networks that support both IPv4 and native IPv6 connectivity. However, you might need an IPv6-only test network to test IPv6-capable applications.
Performing Link-Local Pings
To ping a node using link-local addresses and view the entries created in the neighbor cache, complete the following steps:
1.On ROUTER1, type the netsh interface ipv6 show address command to obtain the link-local address of the interface named Subnet 1 Connection.
2.On CLIENT1, type the netsh interface ipv6 show address command to obtain the link-local address and interface index of the interface named Local Area Connection.
3.On CLIENT1, type the following command to ping the link-local address of ROUTER1’s interface on Subnet 1:
ping ROUTER1LinkLocalAddress%InterfaceIndex
InterfaceIndex is the interface index of the interface named Local Area Connection obtained in step 2.
Appendix E Setting Up an IPv6 Test Lab |
447 |
For example, if the link-local address of ROUTER1’s interface on Subnet 1 is fe80::b500:734b:fe5b:3945 and the interface index for the Local Area Connection interface on CLIENT1 is 7, the command is
ping fe80::b500:734b:fe5b:3945%7
4.On CLIENT1, type the netsh interface ipv6 show neighbors command to view the entry in the CLIENT1 neighbor cache for ROUTER1. You should see an entry for ROUTER1’s link-local address.
5.On CLIENT1, type the netsh interface ipv6 show route command to view the entries in the CLIENT1 routing table.
Enabling Native IPv6 Connectivity on Subnet 1
To enable native IPv6 connectivity on Subnet 1, complete the following steps:
1.On ROUTER1, type the following commands:
netsh interface ipv6 set interface “Subnet 1 Connection” advertise=enabled forwarding=enabled
netsh interface ipv6 add route 2001:db8:0:1::/64 “Subnet 1 Connection” publish=yes
netsh interface ipv6 add route ::/0 “Subnet 2 Connection” fe80::1 publish=yes
These commands configure ROUTER1 to advertise the 2001:DB8:0:1::/64 prefix on Subnet 1 and itself as a default IPv6 router. The FE80::1 address is a temporary next-hop IPv6 address for ROUTER1.
2.On ROUTER1, type the netsh interface ipv6 show address command to obtain the public address assigned to the interface named Subnet 1 Connection.
3.On CLIENT1, type the netsh interface ipv6 show address command to obtain the public address assigned to the interface named Local Area Connection.
4.On CLIENT1, type the following command to ping the public address of ROUTER1’s interface on Subnet 1:
ping ROUTER1PublicAddress
For example, if the public address of ROUTER1’s interface on Subnet 1 is 2001:db8::1:b500:734b:fe5b:3945, the command is
ping 2001:db8::1:b500:734b:fe5b:3945
At this point in the test lab configuration, there is an IPv4 routing infrastructure throughout the network and Subnet 1 has native IPv6 connectivity. CLIENT1 can use IPv6 addresses based on the 2001:DB8:0:1::/64 global address prefix and native IPv6 traffic to communicate
448 Understanding IPv6, Second Edition
with DNS1 and ROUTER1, but it still cannot use IPv6 to communicate with ROUTER2 or CLIENT2. To enable IPv6 connectivity to ROUTER2 and CLIENT2 without enabling native IPv6 routing and advertising on Subnet 2 and Subnet 3, our next task is to configure ROUTER1 as an Intra-Site Automatic Tunnel Addressing Protocol (ISATAP) router.
Configuring ISATAP
In this task, we configure ROUTER1 as an ISATAP router so that IPv6 hosts on the IPv4-only portion of the test lab network (Subnet 2 and Subnet 3) can communicate with IPv6 hosts on the native IPv6 portion of the test lab network (Subnet 1). To configure the test lab network to use ISATAP, do the following:
1.On ROUTER1, type the netsh interface isatap set router 10.0.2.1 command, and then the netsh interface ipv6 show address command to obtain the interface index of the ISATAP interface that is assigned the link-local address FE80::5EFE:10.0.2.1.
2.On ROUTER1, enable forwarding and advertising on the ISATAP interface, using the following commands:
netsh interface ipv6 set interface ISATAPInterfaceIndex forwarding=enabled advertise=enabled
ISATAPInterfaceIndex is the interface index obtained in step 1.
This command configures ROUTER1 as an advertising ISATAP router for the logical ISATAP subnet consisting of Subnet 2 and Subnet 3.
3.On ROUTER1, add a route for the subnet prefix of the logical ISATAP subnet to the ISATAP interface and configure it to be published with the following command:
netsh interface ipv6 add route 2001:db8:0:99::/64 ISATAPInterfaceIndex publish=yes
This command configures ROUTER1 to advertise the 2001:DB8:0:99::/64 route to ISATAP hosts on the logical ISATAP subnet.
4.On DNS1, use the Registry Editor (Regedit.exe) to remove the ISATAP entry from the HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\DNS\Parameters\ GlobalQueryBlockList registry value.
5.Use the DNS snap-in to restart the DNS Server service on DNS1.
6.Use the DNS snap-in to add a host (A) resource record named “ISATAP” to the testlab.microsoft.com forward lookup zone for the IPv4 address of 10.0.2.1.
7.On CLIENT1, type the netsh interface ipv6 show address command to obtain the public address assigned to the interface named Local Area Connection.
8.From the Network Connections folder on CLIENT2, disable and then enable the Local Area Connection. This renews CLIENT2’s configuration to determine the ISATAP router
Appendix E Setting Up an IPv6 Test Lab |
449 |
IPv4 address of 10.0.2.1 and obtain an ISATAP address with the global prefix of 2001:DB8:0:99::/64.
9.Ping CLIENT1 from CLIENT2. On CLIENT2, type the following command: ping CLIENT1PublicAddress
CLIENT1PublicAddress is the public address of CLIENT1 obtained in step 7.
This ping command should succeed because IPv6 connectivity using ISATAP now exists between CLIENT2 and CLIENT1. On the logical ISATAP subnet between CLIENT2 and ROUTER1, the IPv6 traffic is encapsulated as IPv4 packets.
At this point in the test lab configuration, there is an IPv4 routing infrastructure throughout the network. For IPv6 traffic, Subnet 1 has native IPv6 connectivity and Subnet 2 and Subnet 3 are a logical ISATAP subnet. CLIENT1 can communicate with DNS1 and ROUTER1 with native IPv6 traffic and communicate with ROUTER2 or CLIENT2 with encapsulated IPv6 traffic. In the next task, we will remove ISATAP and configure native IPv6 connectivity for all three subnets.
Configuring Native IPv6 Connectivity for All Subnets
To configure native IPv6 connectivity for all the subnets of the test lab network, complete the following steps:
1.On DNS1, type the netsh interface ipv6 show address command to obtain the public address assigned to the Local Area Connection interface.
2.On DNS1, use the DNS snap-in to remove the address (A) resource record named “ISATAP” from the testlab.microsoft.com forward lookup zone.
3.On ROUTER1, type the netsh interface ipv6 show address command to obtain the interface index of the ISATAP interface that is assigned the link-local address FE80::5EFE:10.0.2.1 and the link-local address of the interface named Subnet 2 Connection.
4.On ROUTER1, type the following commands: netsh interface isatap set router default
netsh interface ipv6 set interface ISATAPInterfaceIndex forwarding=disabled advertise=disabled
netsh interface ipv6 delete route 2001:db8:0:99::/64 ISATAPInterfaceIndex netsh interface ipv6 add dnsserver “Subnet 2 Connection” DNS1IPv6Address
ISATAPInterfaceIndex is the interface index of the ISATAP interface obtained in step 3. DNS1IPv6Address is the public address of DNS1 obtained in step 1.
5.On ROUTER2, type the netsh interface ipv6 show address command to obtain the link-local address of the interface named Subnet 2 Connection.
450Understanding IPv6, Second Edition
6.On ROUTER1, type the following commands:
netsh interface ipv6 set interface “Subnet 2 Connection” forwarding=enabled advertise=enabled
netsh interface ipv6 add route 2001:db8:0:2::/64 “Subnet 2 Connection” publish=yes
netsh interface ipv6 delete route ::/0 “Subnet 2 Connection”
netsh interface ipv6 add route ::/0 “Subnet 2 Connection”
ROUTER2AddressOnSubnet2 publish=yes
netsh interface ipv6 add dnsserver “Subnet 1 Connection” DNS1IPv6Address
ROUTER2AddressOnSubnet2 is the link-local address assigned to ROUTER2’s Subnet 2 Connection obtained in step 5.
7.On ROUTER2, type the following commands:
netsh interface ipv6 set interface “Subnet 2 Connection” forwarding=enabled advertise=enabled
netsh interface ipv6 set interface “Subnet 3 Connection” forwarding=enabled advertise=enabled
netsh interface ipv6 add route 2001:db8:0:2::/64 “Subnet 2 Connection” publish=yes
netsh interface ipv6 add route 2001:db8:0:3::/64 “Subnet 3 Connection” publish=yes
netsh interface ipv6 add route ::/0 “Subnet 2 Connection”
ROUTER1AddressOnSubnet2 publish=yes
ROUTER1AddressOnSubnet2 is the link-local address assigned to ROUTER1’s Subnet 2 Connection obtained in step 3.
8.On CLIENT1, run the netsh interface ipv6 add dnsserver “Local Area Connection”
DNS1IPv6Address command.
9.From the Network Connections folder on CLIENT1, disable and then enable the Local Area Connection. This renews CLIENT1’s configuration.
10.On CLIENT1, type the netsh interface ipv6 show route command to view the new routes for 2001:DB8:0:1::/64, 2001:DB8:0:2::/64, and ::/0.
As described in Chapter 10, “IPv6 Routing,” the IPv6 protocol for Windows Server 2008 and Windows Vista advertises off-link prefixes using the Route Information option in Router Advertisement messages. These prefixes become routes in the routing table of the receiving host.
11.On CLIENT2, run the netsh interface ipv6 add dnsserver “Local Area Connection”
DNS1IPv6Address command.