IPv6 Test Lab Extension: Demonstrating DHCPv6

IPv6 Test Lab Extension: Demonstrating DHCPv6

This IPv6 Test Lab Extension describes how to configure DHCPv6 for the Contoso intranet. You configure DC1 as a DHCPv6 server for the Corpnet and Corpnet2 subnets.

Note  These instructions are designed for a working IPv6 test lab that has been configured based on the instructions in the Test Lab Guide: Demonstrate IPv6.

If you are running the IPv6 test lab in a virtual environment, you can create snapshots of the virtual machines (VMs) for all of the test lab computers before performing the following procedure.

Configuring and Demonstrating DHCPv6 for IPv6 Addresses and Settings
To configure DC1 as the DHCPv6 server:

  1. On DC1, click Start, click All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.
  2. In the Command Prompt window, type netsh interface ipv6 add address Corpnet 2001:db8::1111, and then press ENTER.
  3. In the Command Prompt window, type netsh interface ipv6 add address Corpnet2 2001:db8:0:2::2222, and then press ENTER. The DHCP Server service needs static IPv6 addresses on its interfaces to service DHCPv6 requests from IPv6 hosts.
  4. On DC1, click Start, point to Administrative Tools, and then 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 Prefix page, type 2001:db8:: in Prefix, 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 Prefix page, type 2001:db8:0:2:: in Prefix, 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 window, run the following commands:

    netsh interface ipv6 set interface Corpnet managedaddress=enable otherstateful=enable

    netsh interface ipv6 set interface Corpnet2 managedaddress=enable otherstateful=enable

  20. Connect CLIENT1 to the Corpnet subnet.
  21. In the Command Prompt window, type ipconfig, and then press ENTER. Notice that there is an address starting with “2001:db8::” assigned to the Local Area Connection adapter. DC1 is still advertising address prefixes 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.

To demonstrate the use of DHCPv6 by CLIENT1:

  1. Connect CLIENT1 to the Corpnet2 subnet.
  2. In the Command Prompt window, type ipconfig, and then press ENTER.
  3. Notice that are two IPv6 addresses beginning with "2001:db8:0:2" assigned to the Local Area Connection adapter.
  4. In the Command Prompt window, type ipconfig /all, and then press ENTER.
  5. Notice that one of the addresses beginning with "2001:db8:0:2" have Lease Obtained and Lease Expires fields after the IPv6 address. This indicates that this address was assigned by a DHCPv6 server.
  6. In the Command Prompt window, type ipconfig /renew6, and then press ENTER.
  7. In the Command Prompt window, type ipconfig /all, and then press ENTER.
  8. Notice the Lease Obtained and Lease Expires fields after the IPv6 address beginning with "2001:db8:0:2" has changed from step 5.
  9. Notice that 10.0.0.1 is the only DNS server assigned to the Local Area Connection adapter.
  10. On DC1, in the DHCP snap-in, right-click Server Options, and then click Configure Options.
  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 window, type ipconfig /renew6, and then press ENTER.
  13. In the Command Prompt window, type ipconfig /all, and then press ENTER. Notice that the DNS servers assigned to the Local Area Connection adapter now includes 2001:db8::1111.

With this new configuration, CLIENT1 can obtain native IPv6 addresses on the Contoso intranet 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 configuring its default router from the router advertisements sent by the native IPv6 router (DC1). There is no DHCPv6 option to configure the default gateway.

Hosts on the Corpnet and Corpnet2 configure two IPv6 address: one that is stateless 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 flag in an advertised route for a Windows-based advertising router, in the IPv6 test lab we can configure one of the following: 

  • 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 configuration.

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. Alternately, if you would like return to this working configuration using DHCPv6, you can create a new set of snapshots before restoring the previously made snapshots.

To manually restore the configuration of the IPv6 test lab, perform the following procedure.

Restoring the IPv6 Test Lab
To restore the IPv6 test lab to its original configuration:

  1. On DC1, in the Command Prompt window, run the following commands:

    netsh interface ipv6 del address Corpnet 2001:db8::1111

    netsh interface ipv6 del address Corpnet2 2001:db8:0:2::2222

    netsh interface ipv6 set interface Corpnet managedaddress=disable otherstateful=disable

    netsh interface ipv6 set interface Corpnet2 managedaddress=disable otherstateful=disable

    netsh interface ipv6 set route 2001:db8::/64 Corpnet publish=yes

    netsh interface ipv6 set route 2001:db8:0:2::/64 Corpnet2 publish=yes

  2. In the DHCP console tree, click Server Options.
  3. In the details pane, right-click 00023 DNS Recursive Name, click Delete, and then click OK.
  4. In the DHCP console tree, right-click Scope [2001:db8::] Corpnet, click Delete, and then click Yes twice.
  5. In the DHCP console tree, right-click Scope [2001:db8:0:2::] Corpnet2, click Delete, and then click Yes twice.

 

For additional IPv6 test lab extensions, see IPv6 Test Lab for Windows Server 2008 R2 and Windows 7.
Sort by: Published Date | Most Recent | Most Useful
Comments
  • Hi ,

    Under "Configuring and Demonstrating DHCPv6 for IPv6 Addresses and Settings" In step3, the command typed has a little typing mistake "netsh interface ipv6 add address Corpnet2 2001:db8:0:1::2222,". the address has same prefix 2001:db8:0:1 as Corpnet but its should be 2001:db8:0:2 in this case as later route is based on this.

    It should be " netsh interface ipv6 add address Corpnet2 2001:db8:0:2::2222"

    Let's correct it and thank you for wonderful article.

    Regards,

    Vik

  • FYI: I fixed the references to 2001:db8:0:1::2222. Thanks for pointing this out!

Page 1 of 1 (2 items)