Chapter 2 IPv6 Protocol for Windows Server 2008 and Windows Vista |
37 |
Table 2-1 lists some common configuration combinations and the corresponding value of
DisabledComponents.
Table 2-1 Configuration Combinations and the DisabledComponents Registry Value
Configuration Combination |
DisabledComponents Value |
Disable all tunnel interfaces |
0x1 |
|
|
Disable 6to4 |
0x2 |
|
|
Disable ISATAP |
0x4 |
|
|
Disable Teredo |
0x8 |
|
|
Disable Teredo and 6to4 |
0xA |
|
|
Disable all LAN and PPP interfaces |
0x10 |
|
|
Disable all LAN, PPP, and tunnel interfaces |
0x11 |
|
|
Prefer IPv4 over IPv6 |
0x20 |
|
|
Disable IPv6 over all interfaces, and prefer IPv4 to IPv6 |
0xFF |
|
|
You must restart the computer for the changes to the DisabledComponents registry value to take effect.
You can set DisabledComponents on individual computers with the Registry Editor tool, or you can use Active Directory and Group Policy with a customized .ADM file to set DisabledComponents on a group of computers. If you use a customized .ADM file and then remove the DisabledComponents registry value from the .ADM file, the DisabledComponents registry value does not get automatically removed from registries of the computers to which the updated
.ADM file is applied.
IPv6-Enabled Tools
Windows Server 2008 and Windows Vista include the following IPv6-enabled command-line tools that are most commonly used for network troubleshooting:
■Ipconfig
■Route
■Ping
■Tracert
■Pathping
■Netstat
Ipconfig
The Ipconfig tool displays all current TCP/IP network configuration values, and it is used to perform maintenance tasks such as refreshing DHCP and DNS settings. In Windows
38 Understanding IPv6, Second Edition
Server 2008 and Windows Vista, the ipconfig command without options displays IPv4 and IPv6 configuration for all physical adapters and tunnel interfaces that have addresses.
The following is an example display of the ipconfig command on a computer running Windows Server 2008 or Windows Vista:
Windows IP Configuration
Ethernet adapter Local Area Connection: Connection-specific DNS Suffix . : ecoast.example.com
IPv6 Address. . . . . . . . . . . : 2001:db8:21da:7:713e:a426:d167:37ab Temporary IPv6 Address. . . . . . : 2001:db8:21da:7:5099:ba54:9881:2e54 Link-local IPv6 Address . . . . . : fe80::713e:a426:d167:37ab%6
IPv4 Address. . . . . . . . . . . : 157.60.14.11
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : fe80::20a:42ff:feb0:5400%6 157.60.14.1
Tunnel adapter Local Area Connection* 6:
Connection-specific DNS Suffix |
. : |
IPv6 Address. . . . . . . . . . |
. : 2001:db8:908c:f70f:0:5efe:157.60.14.11 |
Link-local IPv6 Address . . . . |
. : fe80::5efe:157.60.14.11%9 |
Site-local IPv6 Address . . . . . |
: fec0::6ab4:0:5efe:157.60.14.11%1 |
Default Gateway . . . . . . . . . |
: fe80::5efe:131.107.25.1%9 |
|
fe80::5efe:131.107.25.2%9 |
Tunnel adapter Local Area Connection* 7: |
|
Media State . . . . . . . . . . . |
: Media disconnected |
Connection-specific DNS Suffix |
. : |
Ipconfig.exe displays the IPv6 addresses before the IPv4 addresses and indicates the type of IPv6 address using the following labels:
■IPv6 Address A global address with a permanent interface ID
■Temporary IPv6 Address A global address with a randomly derived interface ID that has a short valid lifetime
■Link-local IPv6 Address A link-local address with its corresponding zone ID (the interface index)
■Site-local IPv6 Address A site-local address with its corresponding zone ID (the site ID)
For more information about the different types of IPv6 addresses and the zone ID, see Chapter 3.
By default, the interface names containing an asterisk (*) are tunneling interfaces.
Route
The Route tool displays the entries in the local IPv4 and IPv6 routing tables and allows you to change them. The Route tool displays both the IPv4 and IPv6 routing table when you run the route print command. The following is an example of the IPv6 route table portion of the
Chapter 2 IPv6 Protocol for Windows Server 2008 and Windows Vista |
39 |
display of the route print command on a computer running Windows Server 2008 or Windows Vista:
IPv6 Route Table
===========================================================================
Active Routes: |
|
||
If Metric Network Destination |
Gateway |
||
8 |
286 |
::/0 |
fe80::3cec:bf16:505:eae6 |
1 |
306 |
::1/128 |
On-link |
8 |
38 |
2001:db8::/64 |
On-link |
8 |
286 |
2001:db8::4074:2dce:b313:7c65/128 |
|
|
|
|
On-link |
8 |
286 |
2001:db8::b500:734b:fe5b:3945/128 |
|
|
|
|
On-link |
8 |
286 |
fe80::/64 |
On-link |
17 |
296 |
fe80::5efe:10.0.0.3/128 |
On-link |
8 |
286 |
fe80::b500:734b:fe5b:3945/128 |
|
|
|
|
On-link |
1 |
306 |
ff00::/8 |
On-link |
8 |
286 |
ff00::/8 |
On-link |
===========================================================================
You can change entries in the IPv6 routing table with the Route.exe tool with the route add, route change, and route delete commands.
For more information about the IPv6 routing table, see Chapter 10.
Ping
In previous versions of Windows, the Ping tool verified IPv4-level connectivity to another TCP/IP computer by sending Internet Control Message Protocol (ICMP) Echo messages. The receipt of corresponding Echo Reply messages is displayed, along with round-trip times. Ping is the primary TCP/IP tool used to troubleshoot reachability and name resolution.
The Ping tool in Windows Server 2008 and Windows Vista has been enhanced to support IPv6 in the following ways:
■Ping uses either ICMPv4 Echo or ICMPv6 Echo Request messages to verify IPv4-based or IPv6-based connectivity.
■Ping can parse both IPv4 and IPv6 address formats.
■If you specify a target host by name, the addresses returned by using Windows name resolution techniques can contain both IPv4 and IPv6 addresses—in which case, by default, an IPv6 address is preferred (subject to source and destination address selection).
The following is an example display of the Ping tool on a computer running Windows Server 2008 or Windows Vista for an IPv6 destination address:
F:\>ping 2001:db8:1:f282:dd48:ab34:d07c:3914
Pinging 2001:db8:1:f282:dd48:ab34:d07c:3914 from 2001:db8:1:f282:3cec:bf16:505:eae6 with 32 bytes of data:
40 Understanding IPv6, Second Edition
Reply from 2001:db8:1:f282:dd48:ab34:d07c:3914: time<1ms
Reply from 2001:db8:1:f282:dd48:ab34:d07c:3914: time<1ms
Reply from 2001:db8:1:f282:dd48:ab34:d07c:3914: time<1ms
Reply from 2001:db8:1:f282:dd48:ab34:d07c:3914: time<1ms
Ping statistics for 2001:db8:1:f282:dd48:ab34:d07c:3914:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
The following command-line options support IPv6:
■-i HopLimit
Sets the value of the Hop Limit field in the IPv6 header. The default value is 128. The -i option is also used to set the value of the Time-to-Live (TTL) field in the IPv4 header.
■-R
Forces Ping to trace the round-trip path by sending the ICMPv6 Echo Request message to the destination and to include an IPv6 Routing extension header with the sending node as the next destination.
■-S SourceAddr
Forces Ping to use a specified IPv6 source address.
■-4
Forces Ping to use an IPv4 address when the DNS name query for a host name returns both IPv4 and IPv6 addresses.
■-6
Forces Ping to use an IPv6 address when the DNS name query for a host name returns both IPv4 and IPv6 addresses.
Note The Ping -f, -v TOS, -r count, -s count, -j host-list, and -k host-list commandline options are not supported for IPv6.
When you specify a destination IPv6 address for a Ping, Tracert, or Pathping command, you might have to specify a zone ID as part of the address. The zone ID specifies the zone of the destination for Echo Request messages. The syntax for specifying a zone ID is IPv6Address%ZoneID, in which ZoneID is an integer value. For typical link-local addresses, ZoneID is equal to the interface index of the sending interface, as displayed by the output of the netsh interface ipv6 show interface command. For site-local addresses, ZoneID is equal to the site number, as displayed in the output of the netsh interface ipv6 show interface
level=verbose command (the “Zone ID for Site” property). If multiple sites are not being used, a zone ID for site-local addresses is not required. The ZoneID parameter is not required when the destination is a global address.