Académique Documents
Professionnel Documents
Culture Documents
Microsoft Corporation
Published: January 2011
Abstract
Internet Protocol version 6 (IPv6) is designed to solve many of the problems
of the current version of IP (known as IPv4) such as address depletion,
autoconfiguration, extensibility, and restoration of end-to-end connectivity. Its
use will also expand the capabilities of the Internet and enable a variety of
valuable and exciting scenarios, including peer-to-peer and mobile
applications. This paper contains an introduction to IPv6 and step-by-step
instructions for extending the Base Configuration test lab to demonstrate IPv6
functionality and connectivity in Windows 7 and Windows Server 2008 R2.
Copyright Information
This document is provided for informational purposes only and Microsoft
makes no warranties, either express or implied, in this document. Information
in this document, including URL and other Internet Web site references, is
subject to change without notice. The entire risk of the use or the results from
the use of this document remains with the user. Unless otherwise noted, the
example companies, organizations, products, domain names, e-mail
addresses, logos, people, places, and events depicted herein are fictitious,
and no association with any real company, organization, product, domain
name, e-mail address, logo, person, place, or event is intended or should be
inferred. Complying with all applicable copyright laws is the responsibility of
the user. Without limiting the rights under copyright, no part of this document
may be reproduced, stored in or introduced into a retrieval system, or
transmitted in any form or by any means (electronic, mechanical,
photocopying, recording, or otherwise), or for any purpose, without the
express written permission of Microsoft Corporation.
Contents
Test Lab Guide: Demonstrate IPv6....................................................................1
Abstract...................................................................................................... 1
Copyright Information...................................................................................... 2
Contents........................................................................................................... 3
Introduction...................................................................................................... 4
In this guide................................................................................................... 6
Test lab overview........................................................................................... 6
Hardware and software requirements............................................................7
Steps for Configuring the IPv6 Test Lab............................................................8
Step 1: Set up the Base Configuration Test Lab.............................................9
Step 2: Configure the Test Lab for the Corpnet2 Subnet................................9
Configure DC1............................................................................................. 9
Configure EDGE1....................................................................................... 11
Configure APP1......................................................................................... 12
Verify IPv4 connectivity to the Corpnet2 subnet.......................................12
Step 3: Demonstrate default IPv6 connectivity...........................................13
Demonstrate default IPv6 configuration and link-local connectivity on the
same subnet........................................................................................... 14
Demonstrate link-local connectivity between subnets..............................14
Step 4: Demonstrate ISATAP-based IPv6 connectivity.................................15
Configure ISATAP for the Contoso intranet................................................15
Demonstrate ISATAP connectivity on the Contoso intranet.......................16
Step 5: Demonstrate native IPv6 connectivity.............................................17
Remove ISATAP connectivity.....................................................................17
Configure native IPv6 connectivity............................................................19
Demonstrate native IPv6 connectivity......................................................20
Step 6: Demonstrate 6to4-based connectivity............................................21
Configure 6to4-based connectivity...........................................................21
Demonstrate 6to4-based connectivity......................................................22
Snapshot the Configuration............................................................................23
Additional Resources...................................................................................... 23
Introduction
The current version of IP (known as Version 4 or IPv4) has not been
substantially changed since Request for Comments (RFC) 791 was published
in 1981. IPv4 has proven to be robust, easily implemented and interoperable,
and has stood the test of scaling an internetwork to a global utility the size of
todays Internet. However, on todays Internet, IPv4 has the following
disadvantages:
Limited address space The most visible and urgent problem with using
IPv4 on the modern Internet is the depletion of public addresses. This
limited address space has forced the wide deployment of network address
translators (NATs), which can share one public IPv4 address among several
privately addressed computers. NATs have the side effect of acting as a
barrier for server, listener, and peer-to-peer applications running on
computers that are located behind the NAT. Although there are
workarounds for NAT issues, they only add complexity to what should be
an end-to-end addressable global network.
All of these issues and others prompted the Internet Engineering Task Force
(IETF) to begin the development of a replacement protocol that would solve
the problems of IPv4 and be extensible to solve additional problems in the
future. This replacement protocol is IPv6.
IPv6 solves the problems of IPv4 in the following ways:
Huge address space IPv6 addresses are 128 bits long, creating an
address space with 3.4 X 1038 possible addresses. This is plenty of address
space for the foreseeable future and allows all manner of devices to
connect to the Internet without the use of NATs. Address space can also be
allocated internationally in a more equitable manner.
Required support for IPsec headers Unlike IPv4, IPv6 support for
IPsec protocol headers is required. Applications can always rely on
industry standard security services for data sent and received. However,
the requirement to process IPsec headers does not make IPv6 inherently
more secure. IPv6 packets are not required to be protected with AH or ESP.
For more information about IPv6 in Windows, see the IPv6 TechNet web page.
In this guide
This paper contains instructions for setting up a test lab based on the Base
Configuration test lab and deploying IPv6 using four server computers and one
client computer. The resulting IPv6 test lab demonstrates default and
configured IPv6 connectivity across an intranet and a simulated IPv4-only
Internet.
Important
The following instructions are for configuring an IPv6 test lab using the
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 does it 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. Attempting to adapt this IPv6 test
lab configuration to a pilot or production deployment can result in
configuration or functionality issues.
The IPv6 test lab consists of three subnets that simulate the following:
Computers on each subnet connect using a hub or switch. See the following
figure.
Configure DC1.
Configure EDGE1.
Configure APP1.
To configure DC1
1. Add another network adapter to DC1 and connect it to the Corpnet2
subnet.
2. From DC1, click Start, right-click Network, and then click Properties.
3. In the Network and Sharing Center, click Change adapter
settings.
4. In Network Connections, right-click the network connection that is
connected to the Corpnet subnet, and then click Rename.
5. Type Corpnet, and then press ENTER.
6. Right-click the network connection that is connected to the Corpnet2
subnet, and then click Rename.
7. Type Corpnet2, and then press ENTER.
8. Right-click Corpnet2, and then click Properties.
9. Click Internet Protocol Version 4 (TCP/IPv4), and then click
Properties.
10.Select Use the following IP address. In IP address, type 10.0.2.1.
In Subnet mask, type 255.255.255.0.
11.
12.
13.
18.In the console tree, right click IPv4, click New Scope, and then click
Next.
19.On the Scope Name page, type Corpnet2 in Name, and then click
Next.
20.On the IP Address Range page, type 10.0.2.100 in Start IP address,
type 10.0.2.150 in End IP address, type 24 in Length, and then
click Next.
21.On the Add Exclusions and Delay page, click Next.
22.On the Lease Duration page, click Next.
23.On the Configure DHCP Options page, click Next.
24.On the Router (Default Gateway) page, type 10.0.2.1 in IP address,
click Add, and then click Next.
25.On the Domain Name and DNS Servers page, click 127.0.0.1, and
then click Remove.
26. Type 10.0.0.1 in IP address, click Add, and then click Next.
27.On the WINS Servers page, click Next.
28.On the Activate Scope page, click Next.
29.On the Completing the New Scope Wizard page, click Finish.
30.Close the DHCP snap-in.
31.Click Start, click All Programs, click Accessories, right-click
Command Prompt, and then click Run as administrator.
32.In the Command Prompt window, type netsh interface ipv4 set
interface Corpnet forwarding=enabled, and then press ENTER.
33.In the Command Prompt window, type netsh interface ipv4 set
interface Corpnet2 forwarding=enabled, and then press ENTER.
34.Leave the Command Prompt window open.
Configure EDGE1
In this procedure, we configure EDGE1 with a static route so that IPv4
locations on the new Corpnet2 subnet are reachable and enable file sharing,
which allows incoming traffic for the Ping.exe tool.
11
12
press ENTER, type net start iphlpsvc, and then press ENTER.
6. On CLIENT1, in the Command Prompt window, type ping
2001:db8:0:abcd:0:5efe:10.0.0.2, and then press ENTER. You
should see four successful replies.
7. In the Command Prompt window, type ping
2001:db8:0:abcd:0:5efe:10.0.0.3, and then press ENTER. You
should see four successful replies.
8. In the Command Prompt window, type ipconfig /flushdns, and then
press ENTER.
9. In the Command Prompt window, type ping app1, and then press
ENTER. You should see four successful replies. Notice that CLIENT1 is
now using 2001:db8:0:abcd:0:5efe:10.0.0.3, the ISATAP-based IPv6
address of APP1, rather than the IPv4 address 10.0.0.3.
10.
11.
In the Command Prompt window, type ping edge1, and then press
ENTER. You should see four successful replies. Notice that CLIENT1 is
now using 2001:db8:0:abcd:0:5efe:10.0.0.2, the ISATAP-based IPv6
address, rather than the IPv4 address 10.0.0.2.
Connect CLIENT1 to the Corpnet2 subnet.
12.
13.
You can use ISATAP for IPv6 addressing and connectivity across an IPv4-only
intranet that is not possible with link-local addresses. However, ISATAP should
be used in a limited capacity for testing while you deploy native IPv6
capabilities.
folder.
12.In the Files shared folder window, double-click the Example.txt file.
You should see the contents of the Example.txt file.
13.Close the example.txt - Notepad and the Files shared folder
windows.
here: _________________________
5. On DC1, in the Command Prompt window, type ipconfig, and then
press ENTER. Notice the address starting with 2001:db8:0:2:
assigned to the Corpnet2 interface. Write the address here:
_________________________
6. On CLIENT1, in the Command Prompt window, type ping APP1s IPv6
address (from step 4), and then press ENTER. You should see four
successful replies.
7. In the Command Prompt window, type ping DC1s IPv6 address on the
Corpnet 2 interface (from step 5), and then press ENTER. You should
see four successful replies.
The 6to4 transition technology and EDGE1 acting as a 6to4 relay allows
CLIENT1 to reach locations on the IPv6-capable Contoso intranet over the
IPv4-only Internet subnet.
Additional Resources
For more information about IPv6 in Windows, see the IPv6 TechNet web page.
To get your questions about this test lab or IPv6 answered, see the IPv6
TechNet Forum.
To provide the authors of this guide with feedback or suggestions for
improvement, send an email message to tlgfb@microsoft.com.
23
For a list of TLGs related to this test lab or extensions to try for additional
functionality, see IPv6 Test Lab for Windows Server 2008 R2 and Windows 7 in the
TechNet Wiki.
For a list of additional Microsoft TLGs, see Test Lab Guides in the TechNet Wiki.
24