Implementation and testing of IPv6 transition mechanisms

Research on IPV4/IPV6 translation gateway based on NAT-PT technology and Network Traffic Capture and Storage for IPv6 Network
AnnaWills Profile Pic
AnnaWills,Mexico,Researcher
Published Date:21-08-2017
Your Website URL(Optional)
Comment
APPENDIx C Setting Up an IPv6 test Lab his appendix provides information about how you can use ive computers to create a test lab to Tconigure and test the IPv6 protocol for Windows. These instructions take you t roh ugh setting up a test lab based on the Base Coniguration test lab and deploying IPv6 using four s vee r co r mputers and one client computer. The resulting IPv6 test lab demonstrates defauld co t annigured IPv6 con- nectivity across an intranet and a simulated IPv4-only Internet. Beyond the set of tasks described in this appendix, these instructions allow you to create a func- tioning IPv6-capable network. You can use this network to: ■ Learn about and experiment with IPv6 features and functionality ■ Explore network protocol and process speciics by capturing network ti ra c w f ith a packet analyzer such as Network Monitor 3.4 ■ Aid in developing applications for IPv6 or modifying existing applications to work over both IPv4 and IPv6. Important The following instructions are for coniguring an IPv6 test lab using the mi - ni mum number of computers. Individual computers are needed to separate the services provided on the network and to clearly show the desired functionality. This c gu orn ai tion is neither designed to relect best practices nor does it relect a desired or r m ec m oended coniguration for a production network. The coniguration, including IP a dred sses and all other coniguration parameters, is designed only to work on a separate test lae b n twork. Attempting to adapt this IPv6 test lab coniguration to a pilot or production de m pe ln ot y can result in coniguration or functionality issues. IPv6 Test Lab Setup In this test lab, IPv6 connectivity is deployed with: ■ One computer running Windows Server 2012 (when using the Windows Server 2012-based Base Coniguration test lab) or Windows Server 2008 R2 Enterprise Edition (n u whe sing the Windows Server 2008 R2-based Base Coniguration test lab) named DC1 that is coni urg ed as an intranet domain controller, Domain Name System (DNS) server, Dynamic Hoo sni t Cgura- tion Protocol (DHCP) server, and an IPv6 router. 487■ One intranet member server running Windows Server 2012 (when using the Windows Server 2012-based Base Coniguration test lab) or Windows Server 2008 R2 Enterprise E ti di on (when using the Windows Server 2008 R2-based Base Coniguration test lab) named ED1 t GEhat is conigured as a 6to4 relay. ■ One intranet member server running Windows Server 2012 (when using the Windows Server 2012-based Base Coniguration test lab) or Windows Server 2008 R2 Enterprise E ti di on (when using the Windows Server 2008 R2-based Base Coniguration test lab) named APPh 1 t at is conigured as a general application server. ■ One stand-alone server running Windows Server 2012 (when using the Windows Server 2012- based Base Coniguration test lab) or Windows Server 2008 R2 Enterprise Editiw oh n ( en using the Windows Server 2008 R2-based Base Coniguration test lab) named INET1 t ah t is conig - ured as an Internet DHCP server, DNS server, and web server. ■ One roaming member client computer running Windows 8 (when using the Windows Server 2012-based Base Coniguration test lab) or Windows 7 Enterprise or Ultimate ( en u whsing the Windows Server 2008 R2-based Base Coniguration test lab) named CLIENT1. The IPv6 test lab consists of three subnets isolated from your organization intranet that simulate the following: ■ The Internet (131.107.0.0/24). Note that this subnet is not connected to the actual Internet. ■ An intranet subnet named Corpnet (10.0.0.0/24), separated from the Internet by EDGE1. ■ An additional intranet subnet named Corpnet2 (10.0.1.0/24), separated from the Corpnet subnet by DC1. Computers on each subnet connect using a hub or switch. See Figure C-1 for the conigru ation of subnets and computers. INET1 DC1 Corpnet2 10.0.2.0/24 Internet Corpnet 131.107.0.0/24 10.0.0.0/24 EDGE1 APP1 CLIENT1 FIGURE C-1 The IPv6 test lab. 488 Understanding IPv6This appendix demonstrates the following: ■ The default behavior of IPv6 and connectivity on an IPv4-only intranet ■ IPv6-based intranet connectivity using the Intra-Site Automatic Tunnel Addressing Protocol (ISATAP) ■ IPv6-based intranet connectivity using native IPv6 addressing ■ IPv6 connectivity across a simulated IPv4-only Internet using 6to4 Optional exercises include setting up a Dynamic Host Coniguration Pro l f to oco r IPv6 (DHCPv6) server, demonstrating a DNS zone transfer over IPv6, and coniguring the Corn pet and Corpnet2 subnets for IPv6-only operation. Hardware and Software Requirements The following are required components of the test lab: ■ The product disc or iles for Windows Server 2012 or Windows Server 2008 R2. ■ The product disc or iles for Windows 8 or Windows 7. ■ Four computers that meet the minimum hardware requirements for Windows Server 2012 or Windows Server 2008 R2 Enterprise Edition. Two of these computers have two network adapt- ers installed. ■ One computer that meets the minimum hardware requirements for Windows 8 or Windows 7 Enterprise or Ultimate. Steps for Coniguring the IPv6 Test Lab There are six steps to follow when setting up the IPv6 test lab. 1. Set up the Base Coniguration test lab. The IPv6 test lab requires either the Windows Server 2012 Base Coniguration te asb o t lr the Windows Server 2008 R2 Base Coniguration test lab as its starting point. You can get the Base Coniguration Test Lab Guide for Windows Server 2012 and Windows 8 from http://go.microsoft.com/FWLink/p/?Linkid=2363. 58 You can get the Base Coniguration Test Lab Guide for Windows Server 2008 R2 an d Windows 7 from http://go.microsoft.com/FWLink/p/?Linkid=1981.40 2. Conigure the test lab for the Corpnet2 subnet. Add the Corpnet2 subnet, and conigure routing and DHCP so that all IPv4 locati s o on n the Corpnet and Corpnet2 subnets are reachable. APPENDIx C Setting Up an IPv6 Test Lab 4893. Demonstrate default IPv6 connectivity. Show the automatic coniguration but limited connectivity of link-local I dP re vs 6 a ses d. 4. Demonstrate ISATAP-based IPv6 connectivity. Conigure EDGE1 as an advertising ISATAP router, and show how ISATAP provid s I ePv6 con- nectivity across both subnets of the IPv4-only Contoso intranet. 5. Demonstrate native IPv6 connectivity. Conigure DC1 as an advertising and forwarding IPv6 router, and show the resulg n tinative IPv6 connectivity across the Contoso intranet. 6. Demonstrate 6to4-based connectivity. Conigure EDGE1 as a 6to4 relay, and show the IPv6 connectivity between CLIENT1 o n the Internet subnet and the Contoso intranet. Note You must be logged on as a member of the Domain Admins group or a member of the Administrators group on each computer to complete the tasks described in this appen- dix. If you cannot complete a task while you are logged on with an account that is a mem- ber of the Administrators group, try performing the task while you are logged on with an account that is a member of the Domain Admins group. This appendix provides steps for coniguring the computers of the IPv6 test lab and d mo enstrating various types of IPv6 connectivity. The following sections provide details about how to perform these steps. Step 1: Set Up the Base Coniguration test Lab Set up the Base Coniguration test lab for both the Corpnet and Internet subnets b y using the proce - dures in the “Steps for Coniguring the Corpnet Subnet” and “Steps for Coniguring t he Internet Sub- net” sections of the Test Lab Guide: Base Coniguration for Windows Server 201ht 2 ( tp://go.microsoft .com/FWLink/p/?Linkid=23635 ) o 8 r the Test Lab Guide: Base Coniguration ( http://go.microsoft.com/ FWLink/p/?Linkid=19814 ) ( 0for Windows Server 2008 R2 and Windows 7). Step 2: Conigure the test Lab for the Corpnet2 Subnet To demonstrate the default IPv6 behavior and IPv6 connectivity between the subnets of an intranet, you must add another subnet, Corpnet2, to the Contoso intranet. Use the following procedures: ■ Conigure DC1. ■ Conigure EDGE1. 490 Understanding IPv6■ Conigure APP1. ■ Verify IPv4 connectivity to the Corpnet2 subnet. Conigure DC1 In this procedure, we conigure DC1 with an additional network adapter, with a D CP s Hcope for the new Corpnet2 subnet, and as an IPv4 router between the subnets. 1. Add another network adapter to DC1, and connect it to the Corpnet2 subnet. 2. From DC1: a. For Windows Server 2008 R2: Click Start, right-click Network, and then click Properties. b. For Windows Server 2012: Right-click the network icon in the notiication are d t a, a he nn click Open Network and Sharing Center. 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. Click Advanced, and then click the DNS tab. 12. In DNS Sufix For This Connection, type corp.contoso.com, click OK three times, and then click Close. 13. Close the Network Connections window. 14. To open the DHCP snap-in: a. For Windows Server 2008 R2: click Start, point to Administrative Tools, and then click DHCP. b. For Windows Server 2012: from the Start screen, click DHCP. 15. In the console tree, open dc1.corp.contoso.com/IPv4/Scope 10.0.0.0 Corpnet, right-click Scope Options, and then click Conigure Options. APPENDIx C Setting Up an IPv6 Test Lab 49116. In the Available Options list, select 121 Classless Static Routes, and then click Add Route. 17. In the Add a Static Route dialog box, type 10.0.2.0 in Destination, type 255.255.255.0 in Network Mask, type 10.0.0.1 in Router, and then click OK twice. 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 Conigure 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. To open a command prompt or Windows PowerShell: a. For Windows Server 2008 R2: click Start, click All Programs, click Accessories, right-click Command Prompt, and then click Run As administrator. b. For Windows Server 2012: on the taskbar, right-click Windows PowerShell, and then click Run As Administrator. 32. In the Command Prompt or Windows PowerShell window, type netsh interface ipv4 set interface Corpnet forwarding=enabled, and then press Enter. For Windows Server 2012, you can also use the Set-NetIPInterface -InterfaceAlias Corpnet -AddressFamily IPv4 -Forwarding Enabled Windows PowerShell command. 33. In the Command Prompt or Windows PowerShell window, type netsh interface ipv4 set interface Corpnet2 forwarding=enabled, and then press Enter. For Windows Server 2012, you can also use the Set-NetIPInterface -InterfaceAlias Corpnet2 -AddressFamily IPv4 -Forwarding Enabled Windows PowerShell command. 34. Leave the Command Prompt or Windows PowerShell window open. 492 Understanding IPv6Conigure eDGe1 In this procedure, we conigure EDGE1 with a static route so tn t hat I he n Pv4 l ew C ocaotirponnes o t2 subnet are reachable and enable ile sharing, which allows inhe P comin ing t g.exe t rafioc f ol.or t 1. On EDGE1, to open a command prompt or Windows PowerShell: a. For Windows Server 2008 R2: click Start, click All Programs, click Accessories, right-click Command Prompt, and then click Run As administrator. b. For Windows Server 2012: on the taskbar, right-click Windows PowerShell, and then click Run As Administrator. 2. In the Command Prompt or Windows PowerShell window, type netsh interface ipv4 add route 10.0.2.0/24 interface=Corpnet nexthop=10.0.0.1, and then press Enter. For Windows Server 2012, you can also use the Add-NetRoute -DestinationPreix 10.0.2.0/24 -InterfaceAlias Corpnet -NextHop 10.0.0.1 -AddressFamily IPv4 Windows PowerShell command. 3. In the Command Prompt or Windows PowerShell window, type ping 10.0.2.1 , and then press Enter. There should be four successful replies. 4. Leave the Command Prompt or Windows PowerShell window open. 5. Right-click the network icon in the notiication area, and then click Open Nk A etw no d r Sharing Center. 6. In the Network And Sharing Center window, click Change Advanced Sharing Settings. 7. Open Domain, click Turn On File And Printer Sharing, and then click Save Changes. 8. Close the Network And Sharing Center window. Conigure App1 In this procedure, we conigure APP1 with a static route so that IPv4 locations o hn t e Corpnet2 subnet are reachable. 1. On APP1, to open a command prompt or Windows PowerShell: a. For Windows Server 2008 R2: click Start, click All Programs, click Accessories, right-click Command Prompt, and then click Run As administrator. b. For Windows Server 2012: on the taskbar, right-click Windows PowerShell, and then click Run As Administrator. 2. In the Command Prompt or Windows PowerShell window, type netsh interface ipv4 add route 10.0.2.0/24 interface=”Wired Ethernet Connection” next o h p=10.0.0.1 (for Windows Server 2012) or netsh interface ipv4 add route 10.0.2.0/24 interface=”Local Area Connection” nexthop=10.0.0.1 (for Windows Server 2008 R2) and then press Enter. For Windows Server 2012, you can also use the Add-NetRoute -DestinationPreix 10.0.2.0/24 APPENDIx C Setting Up an IPv6 Test Lab 493-InterfaceAlias ”Wired Ethernet Connection” -NextHop 10.0.0.1 -AddressFamily IPv4 Windows PowerShell command. 3. In the Command Prompt or Windows PowerShell window, type ping 10.0.2.1 , and then press Enter. There should be four successful replies. 4. Leave the Command Prompt or Windows PowerShell window open. Verify IPv4 Connectivity to the Corpnet2 Subnet In this procedure, we verify that CLIENT1 can communicate with IPv4 locations on the Corpnet2 subnet and, while on the Corpnet2 subnet, can resolve names and communicate with locations on the Corpnet subnet. 1. Connect CLIENT1 to the Corpnet subnet. 2. To open a command prompt or Windows PowerShell: a. For Windows Server 2008 R2: click Start, click All Programs, click Accessories, right-click Command Prompt, and then click Run As administrator. b. For Windows Server 2012: on the taskbar, right-click Windows PowerShell, and then click Run As Administrator. 3. In the Command Prompt or Windows PowerShell window, type ping 10.0.2.1 , and then press Enter. There should be four successful replies. 4. Connect CLIENT1 to the Corpnet2 subnet. 5. In the Command Prompt or Windows PowerShell window, type ipconig , and then press Enter. CLIENT1 should have an IPv4 address in the range 10.0.2.100 to 10.0.2.150, with a default gateway of 10.0.2.1 and the DNS Server address of 10.0.0.1. 6. In the Command Prompt or Windows PowerShell window, type ping 10.0.0.2 , and then press Enter. There should be four successful replies. 7. In the Command Prompt or Windows PowerShell window, type ping 10.0.0.3 , and then press Enter. There should be four successful replies. 8. In the Command Prompt or Windows PowerShell window, type ping edge1, and then press Enter. There should be a successful name resolution to the IPv4 address 10.0.0.2 and four suc- cessful replies. 9. In the Command Prompt or Windows PowerShell window, type ping app1, and then press Enter. There should be a successful name resolution to the IPv4 address 10.0.0.3 and four suc- cessful replies. 494 Understanding IPv6Step 3: Demonstrate Default IPv6 Connectivity In the absence of advertising IPv6 routers, the Windows-based computers on the Corpnet and Corpnet2 subnets automatically conigure link-local IPv6 addresse egin s (bning with “fe80”). However, these addresses have limited scope and function for connectivity and are not registered in DNS. Use the following procedures to show the default IPv6 connectivity: ■ Demonstrate default IPv6 coniguration and link-local connectivity on t am he s e subnet. ■ Demonstrate link-local connectivity between subnets. Demonstrate Default Ipv6 Coniguration and Link-local Connectivity on the Same Subnet In this procedure, we demonstrate the default IPv6 coniguration and lin ok c-al l connectivity on the Corpnet subnet. 1. Connect CLIENT1 to the Corpnet subnet. 2. On DC1, to open the DNS snap-in: a. For Windows Server 2008 R2: click Start, point to Administrative Tools, and then click DNS. b. For Windows Server 2012: from the Start screen, click DNS. 3. In the console tree, open DNS\DC1\Forward Lookup Zones, and then click corp.contoso.com. Notice that there are no AAAA records corresponding to registered IPv6 addresses for DC1, CLIENT1, or APP1 listed in the contents pane. 4. Leave the DNS snap-in open. 5. On APP1, in the Command Prompt or Windows PowerShell window, type ipconig , and then press Enter. Notice the IPv6 address assigned to the Wired Ethernet Connection or Local Area Connection interface that starts with “fe80”. This is the automatically-assigned link-local address. Write the address here: 6. On CLIENT1, in the Command Prompt or Windows PowerShell window, type ipconig , and then press Enter. Notice the IPv6 address assigned to the Wired Ethernet Connec- tion or Local Area Connection interface that starts with “fe80”. Write the address here: 7. In the Command Prompt or Windows PowerShell window, type ping APP1’s link-local address (from step 5), and then press Enter. You should see four successful replies. Demonstrate Link-local Connectivity Between Subnets In this procedure, we demonstrate the scope of functionality for link-local addresses. 1. Connect CLIENT1 to the Corpnet2 subnet. APPENDIx C Setting Up an IPv6 Test Lab 4952. In the Command Prompt or Windows PowerShell window, type ping APP1’s link-local address (from step 5 of the previous procedure), and then press Enter. You should see fo ur Destination host unreachable messages. 3. On APP1, in the Command Prompt or Windows PowerShell window, type ping CLIENT1’s link-local address (from step 6 of the previous procedure), and then press Enter. You should see four Destination host unreachable messages. 4. On DC1, in the Command Prompt or Windows PowerShell window, type ipconig , and then press ENTER. Notice the link-local IPv6 address assigned to the Corpnet2 interface. Write the address here: 5. On CLIENT1, in the Command Prompt or Windows PowerShell window, type ping DC1’s link-local address (from step 4), and then press Enter. You should see four successful replies. In their default coniguration on the Contoso intranet, the computers runn g W in indows automat- i cally conigure link-local IPv6 addresses that provide connectivity onl th y to o er IPv6 hosts on the same subnet. These link-local addresses are not registered in DNS. Step 4: Demonstrate ISataP-Based IPv6 Connectivity ISATAP provides IPv6 connectivity across an IPv4-only intranet without having to conigure native IPv6 addressing and routing. This step demonstrates coniguring ISATAP for t e C h ontoso intranet. Use the following procedures to show ISATAP-based connectivity on the Contoso intranet: ■ Conigure ISATAP for the Contoso intranet. ■ Demonstrate ISATAP connectivity on the Contoso intranet. Conigure ISAtAp for the Contoso Intranet In this procedure, we conigure EDGE1 as an advertising ISATAP router. 1. On EDGE1, in the Command Prompt or Windows PowerShell window, type netsh interface ipv6 set interface isatap.corp.contoso.com advertise=enable, and then press Enter. For Windows Server 2012, you can also use the Set-NetIPInterface -InterfaceAlias isatap .corp.contoso.com -AddressFamily IPv6 -Forwarding Enabled -Advertising Enabled Windows PowerShell command. 2. In the Command Prompt or Windows PowerShell window, type netsh interface ipv6 add route 2001:db8:0:abcd::/64 interface=isatap.corp.contoso.com p ublish=ye , a s nd then press Enter. For Windows Server 2012, you can also use the Add-NetRoute -DestinationPreix 2001:db8:0:abcd::/64 -InterfaceAlias isatap.corp.contoso.com -AddressFamily IPv6 -Publish Yes Windows PowerShell command. 3. On DC1, in the Command Prompt or Windows PowerShell window, type dnscmd /conig / globalqueryblocklist wpad, and then press Enter. This step removes the name “ISATAP” from the default global query block list. 496 Understanding IPv64. In the console tree of the DNS snap-in, right-click DNS, point to All Tasks, and then click Restart. 5. In the console tree of the DNS snap-in, open DNS\DC1\Forward Lookup Zones, right-click corp.contoso.com, and then click New Host (A Or AAAA). 6. In the New Host dialog box, type isatap in Name, type 10.0.0.2 in IP Address, click Add Host, click OK, and then click Done. Demonstrate ISataP Connectivity on the Contoso Intranet In this procedure, we demonstrate the coniguration of ISATAP addresses on C ontoso computers, DNS registration of ISATAP addresses, and ISATAP-based connectivity across the Corpnet and Corpnet2 subnets. 1. Connect CLIENT1 to the Corpnet subnet. 2. In the Command Prompt or Windows PowerShell window, type ipconig , and then press Enter. Notice the new IPv6 address beginning with “2001” that is assigned to the interface named isatap.corp.contoso.com. This address is based on the 2001:db8:0:abc ::d /64 preix that EDGE1 is advertising as an ISATAP router. 3. On APP1, in the Command Prompt or Windows PowerShell window, type net stop iphlpsvc, press Enter, type net start iphlpsvc, and then press Enter. 4. In the Command Prompt or Windows PowerShell window, type ipconig , and then press Enter. Notice the IPv6 address 2001:db8:0:abcd:0:5efe:10.0.0.3 that is assigned to the isatap. corp.contoso.com interface. 5. On DC1, in the Command Prompt or Windows PowerShell window, type net stop iphlpsvc, press Enter, type net start iphlpsvc, and then press Enter. 6. On CLIENT1, in the Command Prompt or Windows PowerShell 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 or Windows PowerShell window, type ping 2001:db8:0:abcd:0:5 efe:10.0.0.3, and then press Enter. You should see four successful replies. 8. In the Command Prompt or Windows PowerShell window, type ipconig /lushdns , and then press Enter. 9. In the Command Prompt or Windows PowerShell window, type ping app1, and then press Enter. You should see four successful replies. Notice that CLIENT1 is now usin0 g 20 1: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. In the Command Prompt or Windows PowerShell window, type ping edge1, and then press Enter. You should see four successful replies. Notice that CLIENT1 is now usin0 g 20 1:db8:0:abc d:0:5efe:10.0.0.2, the ISATAP-based IPv6 address, rather than the IPv4 address 10.0.0.2. APPENDIx C Setting Up an IPv6 Test Lab 49711. Connect CLIENT1 to the Corpnet2 subnet. 12. In the Command Prompt or Windows PowerShell window, type ping 2001:db8:0:abcd:0:5 efe:10.0.0.3, and then press Enter. You should see four successful replies. 13. On EDGE1, in the Command Prompt or Windows PowerShell window, type ping client1, and then press Enter. You should see four successful replies. You can use ISATAP for IPv6 addressing and connectivity across an IPv4-only int ranet 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. Step 5: Demonstrate Native IPv6 Connectivity Use the following procedures to show native IPv6 connectivity across the Contoso intranet: ■ Remove ISATAP connectivity ■ Conigure native IPv6 connectivity ■ Demonstrate native IPv6 connectivity remove ISataP Connectivity In this procedure, we remove the ISATAP coniguration, returning the Contoso in tranet to link-local IPv6 connectivity. 1. On EDGE1, in the Command Prompt or Windows PowerShell window, type netsh interface ipv6 set interface isatap.corp.contoso.com advertise=disabled, and then press Enter. For Windows Server 2012, you can also use the Set-NetIPInterface -InterfaceAlias isatap.corp .contoso.com -AddressFamily IPv6 -Forwarding Enabled -Advertising Disabled Windows Power- Shell command. 2. In the Command Prompt or Windows PowerShell window, type netsh interface ipv6 delete route 2001:db8:0:abcd::/64 interface=isatap.corp.con toso.com, and then press Enter. For Windows Server 2012, you can also use the Remove-NetRoute -DestinationPreix 2001:db8:0:abcd::/64 -InterfaceAlias isatap.corp.contoso.com -AddressFamily IPv6 Windows PowerShell command. 3. On DC1, in the console tree of the DNS snap-in, open DNS\DC1\Forward Lookup Zones\corp .contoso.com. 4. In the details pane, right-click the isatap A record, click Delete, and then c es li . ck Y 5. In the Command Prompt or Windows PowerShell window, type net stop iphlpsvc, press Enter, type net start iphlpsvc, press Enter, type ipconig /registerdn , a s nd then press Enter. 6. On EDGE1, in the Command Prompt or Windows PowerShell window, type net stop iphlpsvc, press Enter, type net start iphlpsvc, press Enter, type ipconig /registerdn , a s nd then press Enter. 498 Understanding IPv67. In the Command Prompt or Windows PowerShell window, type ipconig , and then press Enter. Notice the link-local IPv6 address that is assigned to the Corpnet interface. Write the address here: 8. On APP1, in the Command Prompt or Windows PowerShell window, type net stop iphlpsvc, press Enter, type net start iphlpsvc, press Enter, type ipconig /registerdn , a s nd then press Enter. 9. On CLIENT1, in the Command Prompt or Windows PowerShell window, type net stop iphlpsvc, press Enter, type net start iphlpsvc, press Enter, type ipconig /registerdn a s,nd then press Enter. 10. On DC1, refresh the details pane of the DNS snap-in and verify that there are no IPv6 addresses (AAAA records) registered for CLIENT1, DC1, and APP1. Conigure Native Ipv6 Connectivity In this procedure, we conigure DC1 as an advertising and forwarding IPv6 router t at a h dvertises native IPv6 preixes to the Corpnet and Corpnet2 subnets. For this procedr ue, you will need the link- local address of EDGE1’s Corpnet interface, as recorded in step 7 of the previous procedure. 1. On DC1, in the Command Prompt or Windows PowerShell window, type netsh interface ipv6 set interface Corpnet forwarding=enabled advertise=enabled advertisedefaultroute=enabled, and then press Enter. For Windows Server 2012, you can also use the Set-NetIPInterface -InterfaceAlias Corpnet -AddressFamily IPv6 -Forwarding Enabled -Advertising Enabled –AdvertiseDefaultRoute Enab W le in ddows PowerShell command. 2. In the Command Prompt or Windows PowerShell window, type netsh interface ipv6 set interface Corpnet2 forwarding=enabled advertise=enabled advertisedefaultroute=enabled, and then press Enter. For Windows Server 2012, you can also use the Set-NetIPInterface -InterfaceAlias Corpnet2 -AddressFamily IPv6 -Forwarding Enabled -Advertising Enabled –AdvertiseDefaultRoute Enab W le in ddows PowerShell command. 3. In the Command Prompt or Windows PowerShell window, type netsh interface ipv6 add route 2001:db8::/64 interface=Corpnet publish=y, a esnd then press Enter. For Win- dows Server 2012, you can also use the Add-NetRoute -DestinationPreix 2001:db8::/64 -InterfaceAlias Corpnet -AddressFamily IPv6 -Publish Yes Windows PowerShell command. 4. In the Command Prompt or Windows PowerShell window, type netsh interface ipv6 add route 2001:db8:0:2::/64 interface=Corpnet2 publish=y, a esnd then press Enter. For Win- dows Server 2012, you can also use the Add-NetRoute -DestinationPreix 2001:db8:0:2::/64 -InterfaceAlias Corpnet2 -AddressFamily IPv6 -Publish Yes Windows PowerShell command. 5. In the Command Prompt or Windows PowerShell window, type netsh interface ipv6 add route ::/0 interface=Corpnet nexthop= link-local address of EDGE1’s Corpnet interface publish=yes (from step 7 of the previous procedure), and then press Enter. For Windows Server 2012, you can also use the Add-NetRoute -DestinationPreix ::/0 -InterfaceAlias Corpnet APPENDIx C Setting Up an IPv6 Test Lab 499-NextHop link-local address of EDGE1’s Corpnet interface -AddressFamily IPv6 -Publish Yes Windows PowerShell command. 6. In the Command Prompt or Windows PowerShell window, type ipconig , and then press Enter. Notice the new IPv6 address starting with “2001:db8::” assigned to the Corpnet interface and the address starting with “2001:db8:0:2” assigned to the Corpnet2 inter- face. Notice the link-local address of the Corpnet interface. Write the address here: 7. On APP1, in the Command Prompt or Windows PowerShell window, type ipconig , and then press Enter. Notice the new IPv6 address starting with “2001:db8::” and the default gateway of DC1’s link-local address, as recorded in step 6. 8. Connect CLIENT1 to the Corpnet subnet. 9. On CLIENT1, in the Command Prompt or Windows PowerShell window, type ipconig , and then press Enter. Notice the new IPv6 address starting with “2001:db8::” and the default gate- way of DC1’s link-local address, as recorded in step 6. 10. On DC1, refresh the details pane of the DNS snap-in and verify there are new AAAA records registered for CLIENT1, EDGE1, APP1, and DC1. Demonstrate Native IPv6 Connectivity In this procedure, we demonstrate native IPv6 connectivity on both the Corpnet and Corpnet2 subnets. 1. Connect CLIENT1 to the Corpnet2 subnet. 2. On APP1, in the Command Prompt or Windows PowerShell window, type ipconig /lushdns , and then press Enter. 3. In the Command Prompt or Windows PowerShell window, type ping client1, and then press Enter. You should see a successful name resolution to CLIENT1’s IPv6 addresn t s ohe Corpnet2 subnet (starting with “2001:db8:0:2”) and four successful replies. 4. On CLIENT1, in the Command Prompt or Windows PowerShell window, type ipconig /lushdns, and then press Enter. 5. In the Command Prompt or Windows PowerShell window, type ping edge1, and then press Enter. You should see a successful name resolution to EDGE1’s IPv6 address on t e C h orpnet subnet (starting with “2001:db8::”) and four successful replies. 6. In the Command Prompt or Windows PowerShell window, type ping app1.corp.contoso.com, and then press Enter. You should see four successful replies. Notice that C N LT IE 1 is using APP1’s IPv6 address starting with “2001:db8::”, rather than the IPv4 address 10.0.0.3. 7. From the taskbar, click the Internet Explorer icon. 500 Understanding IPv68. In the Address bar, type http://app1.corp.contoso.com/, and then press Enter. You should see the default IIS 7 webpage for APP1. 9. For the Windows Server 2008 R2-based test lab, in the Address bar, type https://app1.corp .contoso.com/, and then press Enter. You should see the default IIS 7 webpage for APP1. 10. To view the \\app1\Files shared folder: a. For Windows Server 2008 R2: click Start, type \\app1\Files, and then press Enter. b. For Windows Server 2012: from Internet Explorer, in the Address bar, type \\app1\Files, and then press Enter. 11. You should see the contents of the Files shared folder. 12. Double-click the Example.txt ile. You should see the contents of the Examp xt i le.l te. 13. Close the Example.txt ile and the Files shared folder window. Step 6: Demonstrate 6to4-Based Connectivity Computers running Windows use the 6to4 transition technology for IPv6 connectivity across the IPv4-only Internet. In this step, you conigure EDGE1 as a 6to4 relay and demon trsate how CLIENT1 uses it to reach IPv6 locations on the Contoso intranet. Important This step is not a recommended practice for real-world deployments because it creates a direct channel of communication between Internet and intranet hosts. A variation of this coniguration is used by DirectAccess in Windows Server 2012, Windows Sr 2 er0 ve 08 R2, Windows 8, and Windows 7. However, the incoming trafic to the DirectAccess ser rve destined for the intranet is authenticated and protected with Internet Protocol security (IPsec). Use the following procedures to show 6to4-based connectivity across the Internet subnet: ■ Conigure 6to4-based connectivity ■ Demonstrate 6to4-based connectivity Conigure 6to4-Based Connectivity In this procedure, we conigure EDGE1 as a 6to4 relay. 1. On EDGE1, in the Command Prompt or Windows PowerShell window, type netsh interface 6to4 set state enabled, and then press Enter. For Windows Server 2012, you can also use the Set-Net6to4Coniguration -State Enable W d indows PowerShell command. APPENDIx C Setting Up an IPv6 Test Lab 5012. In the Command Prompt or Windows PowerShell window, type netsh interface ipv6 set interface “6TO4 Adapter” forwarding=enable , a dnd then press Enter. For Windows Server 2012, you can also use the Set-NetIPInterface -InterfaceAlias “6TO4 Adapter” -AddressFamily IPv6 -Forwarding Enabled Windows PowerShell command. 3. In the Command Prompt or Windows PowerShell window, type netsh interface ipv6 set interface Corpnet forwarding=enabled, and then press Enter. For Windows Server 2012, you can also use the Set-NetIPInterface -InterfaceAlias Corpnet -AddressFamily IPv6 -Forwarding Enabled Windows PowerShell command. 4. On INET, to open the DNS snap-in: a. For Windows Server 2008 R2: click Start, point to Administrative Tools, and then click DNS. b. For Windows Server 2012: from the Start screen, click DNS. 5. In the console tree, open DNS\INET1. 6. Right-click Forward Lookup Zones, click New Zone, and then click Next. 7. On the Zone Type page, click Next. 8. On the Zone Name page, type ipv6.microsoft.com in Zone Name, and then click Next. 9. On the Dynamic Update page, click Do Not Allow Dynamic Updates, click Next, and then click Finish. 10. In the console tree, right-click the ipv6.microsoft.com zone, and then click New Host (A or AAAA). 11. In the New Host dialog box, type 6to4 in Name, type 131.107.0.2 in IP Address, click Add Host, click OK, and then click Done. Demonstrate 6to4-Based Connectivity In this procedure, we demonstrate 6to4-based IPv6 connectivity between CLIENT1 on the Internet subnet and computers on the Contoso intranet. 1. On EDGE1, in the Command Prompt or Windows PowerShell window, type ipconig , and then press ENTER. Notice the 2002:836b:2::836b:2 and 2002:836b:3::836b:3 IPv6 addresses assigned to the 6TO4 Adapter. These are 6to4 addresses that EDGE1 automatically assigns based on the public IPv4 addresses 131.107.0.2 and 131.107.0.3, which are assigned to the Internet interface. 2. Connect CLIENT1 to the Internet subnet. 3. On CLIENT1, in the Command Prompt or Windows PowerShell window, type ipconig , and then press ENTER. Notice the address starting with “2002:836b:” assigned to the 6TO4 Adapter. This is a 6to4 address corresponding to its public IPv4 address. Also notice that the default gateway for the 6TO4 Adapter is set to 2002:836b:2::836b:2, a 6to4 address assigned to EDGE1. 502 Understanding IPv64. On APP1, in the Command Prompt or Windows PowerShell window, type ipconig , and then press Enter. Notice the address starting with “2001:db8::” assigned to the Wired Ethernet Connection or Local Area Connection interface. Write the address here: 5. On DC1, in the Command Prompt or Windows PowerShell window, type ipconig , and then press Enter. Notice the address starting with “2001:db8:0:2:” assigned to the Corpnet2 inter- face. Write the address here: 6. On CLIENT1, in the Command Prompt or Windows PowerShell window, type ping APP1’s IPv6 address (from step 4), and then press Enter. You should see four successful replies. 7. In the Command Prompt or Windows PowerShell window, type ping DC1’s 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. Snapshot the Coniguration To save this coniguration of the IPv6 test lab so that you can quickly return to a workin Pv g I 6 con- iguration for your own experimentation and learning, do the following: 1. On all physical computers or virtual machines in the test lab, close all windows and then per- form a graceful shutdown. 2. If your lab is based on virtual machines, save a snapshot of each virtual machine and name the snapshots IPv6. If your lab uses physical computers, create disk images to save the IPv6 test lab coniguration. Additional IPv6 Test Lab Exercises The following sections describe additional exercises that you can do with the IPv6 test lab. Demonstrate DhCPv6 This section describes how to conigure DHCPv6 for the Contoso intranet. You conigure DC1 as a DHCPv6 server and modify its role as an advertising router for the Corpnet and Corpnet2 subnets. Conigure DC1 as the DhCpv6 Server 1. On DC1, to open a command prompt or Windows PowerShell: a. For Windows Server 2008 R2: click Start, click All Programs, click Accessories, right-click Command Prompt, and then click Run As Administrator. APPENDIx C Setting Up an IPv6 Test Lab 503b. For Windows Server 2012: on the taskbar, right-click Windows PowerShell, and then click Run As Administrator. 2. In the Command Prompt or Windows PowerShell window, type netsh interface ipv6 add address Corpnet 2001:db8::1111, and then press Enter. For Windows Server 2012, you can also use the New-NetIPAddress –InterfaceAlias Corpnet –IPAddress 2001:db8::1111 Windows PowerShell command. 3. In the Command Prompt or Windows PowerShell window, type netsh interface ipv6 add address Corpnet2 2001:db8:0:2::2222, and then press Enter. For Windows Server 2012, you can also use the New-NetIPAddress –InterfaceAlias Corpnet2 –IPAddress 2001:db8:0:2::2222 Windows PowerShell command. The DHCP Server service needs static IPv6 addresses on its interfaces to service DHCPv6 requests from IPv6 hosts. 4. On DC1, to open the DHCP snap-in: a. For Windows Server 2008 R2: click Start, point to Administrative Tools, and then click DHCP. b. For Windows Server 2012: from the Start screen, click DHCP. 5. In the console tree of the DHCP snap-in, open dc1.corp.contoso.com, right-click IPv6, and then click New Scope. 6. On the Welcome page, click Next. 7. On the Scope Name page, type Corpnet in Name, and then click Next. 8. On the Scope Preix page, type 2001:db8:: in Preix, and then click Next. 9. On the Add Exclusions page, click Next. 10. On the Scope Lease page, click Next. 11. On the Completing page, click No in Activate Scope Now, and then click Finish. 12. In the console tree of the DHCP snap-in, right-click IPv6, and then click New Scope. 13. On the Welcome page, click Next. 14. On the Scope Name page, type Corpnet2 in Name, and then click Next. 15. On the Scope Preix page, type 2001:db8:0:2:: in Preix, and then click Next. 16. On the Add Exclusions page, click Next. 17. On the Scope Lease page, click Next. 18. On the Completing page, click No in Activate Scope Now, and then click Finish. 19. In the Command Prompt or Windows PowerShell window, run the following commands: 504 Understanding IPv6netsh interface ipv6 set interface Corpnet managedaddress=enable otherstateful=enable netsh interface ipv6 set interface Corpnet2 managedaddress=enable otherstateful=enable For Windows Server 2012, you can also use the following Windows PowerShell commands: Set-NetIPInterface -InterfaceAlias Corpnet -AddressFamily I6 Pv -ManagedAddressConiguration Enabled –OtherStatefulConiguration Enabled Set-NetIPInterface -InterfaceAlias Corpnet2 -AddressFamily IPv6 -ManagedAddress Coniguration Enabled –OtherStatefulConiguration Enabled 20. Connect CLIENT1 to the Corpnet subnet. 21. In the Command Prompt or Windows PowerShell window, type ipconig , and then press Enter. Notice that there is an address starting with “2001:db8:: assigned to the Wired Ethernet Connection or Local Area Connection adapter. DC1 is still advertising stateless address pre- ixes on the Corpnet and Corpnet2 subnets. 22. On DC1, in the console tree of the DHCP snap-in, right-click Scope 2001:db8:: Corpnet, and then click Activate. 23. In the console tree of the DHCP snap-in, right-click Scope 2001:db8:0:2:: Corpnet2, and then click Activate. Demonstrate the Use of DhCPv6 by CLIeNt1 1. Connect CLIENT1 to the Corpnet2 subnet. 2. In the Command Prompt or Windows PowerShell window, type ipconig , and then press Enter. 3. Notice that there are two IPv6 addresses beginning with “2001:db8:0:2” assigned to the Wired Ethernet Connection or Local Area Connection adapter. 4. In the Command Prompt or Windows PowerShell window, type ipconig /al , a lnd then press Enter. 5. Notice that one of the IPv6 addresses beginning with “2001:db8:0:2” has Lease Obtained and Lease Expires ields after the address. This indicates that this address w s asa signed by a DHCPv6 server. 6. In the Command Prompt or Windows PowerShell window, type ipconig /renew6 , and then press Enter. 7. In the Command Prompt or Windows PowerShell window, type ipconig /al , a lnd then press Enter. APPENDIx C Setting Up an IPv6 Test Lab 5058. Notice that the Lease Obtained and Lease Expires ields for the DHCPv6-asn si eg d address have changed to new times (from step 5). 9. Notice that 10.0.0.1 is the only DNS server assigned to the Wired Ethernet Connection or Local Area Connection adapter. 10. On DC1, in the DHCP snap-in, right-click Server Options, and then click Conigp ut ri e O ons. 11. On the General tab, select 0023 DNS Recursive Name Server IPv6 Addresses, type 2001:db8::1111 in New IPv6 Address, click Add, and then click OK. 12. On CLIENT1, in the Command Prompt or Windows PowerShell window, type ipconig /renew6, and then press Enter. 13. In the Command Prompt or Windows PowerShell window, type ipconig /al , a lnd then press Enter. Notice that the DNS servers assigned to the Wired Ethernet Connection or Local Area Connection adapter now include 2001:db8::1111. With this new coniguration, CLIENT1 can obtain native IPv6 addresses on the C nto oso intranet from a DHCPv6 server in addition to the router advertisements sent by the native IPv6 router for the Corpnet and Corpnet2 subnets (DC1). CLIENT1 can also obtain the IPv6 address of its DNS server (DC1). Notice that CLIENT1 is still coniguring its default router from the r er a ou dtvertisements sent by the native IPv6 router (DC1). There is no DHCPv6 option to conigure the defaula t g teway. Hosts on the Corpnet and Corpnet2 conigure two IPv6 address: one that is statee lss from DC1 as an advertising router and one that is stateful from DC1 as the DHCPv6 server. Because there is no way to clear the Autonomous lag in an advertised route for a Windows-based advesrin tig router, in the IPv6 test lab we can conigure one of the following conigurations: ■ Allow DC1 to advertise the 2001:db8::/64 and 2001:db8:0:2::/64 routes, resulting in two IPv6 addresses, but hosts will have local-subnet routes of 2001:db8::/64 when attached to the Corpnet subnet and 2001:db8:0:2::/64 when connected to the Corpnet2 subnet. ■ Prevent DC1 from advertising the 2001:db8::/64 and 2001:db8:0:2::/64 routes, resulting in a single IPv6 address (stateful from DHCPv6), but hosts will not have local-subnet routes of 2001:db8::/64 when attached to the Corpnet subnet and 2001:db8:0:2::/64 when connected to the Corpnet2 subnet. Without a local subnet route, hosts must rely on a Redirect message from the subnet router (DC1) to communicate with hosts on the same subnet. This is the least desirable coniguration. restore the IPv6 test Lab If you are running the IPv6 test lab in a virtual environment, you can discard the changes made by these procedures by restoring the previously made snapshots of the VMs for all of the computers in the test lab. Alternatively, if you would like return to this working conig n u urs ain tio g DHCPv6, you can create a new set of snapshots before restoring the previously made snapshots. To manually restore the coniguration of the IPv6 test lab, perform the follo g p win rocedure. 506 Understanding IPv6

Advise: Why You Wasting Money in Costly SEO Tools, Use World's Best Free SEO Tool Ubersuggest.