Configure ipv6 correctly for your windows 7 system

Various information shows that the remaining fuel indicator of the IPv4 address closely related to the Internet is flashing a warning that it will be exhausted. Only 5% of the IPv4 address is available, and it is expected to be completely exhausted by next autumn. The latest operating system for Microsoft, Wind

, shows that the "remaining fuel indicator" of the IPv4 address that is closely related to the Internet is flashing a warning that it will be exhausted, and only 5% of the IPv4 address is available. It is expected that it will be completely exhausted by the fall of next year. For Microsoft's latest operating system, Windows 7, is it now able to perfectly support the IPV6 address that will replace IPv4?

In fact, compared to the previous operating systems, the Windows 7 operating system has It has done a good job of supporting the IPV6 protocol; however, there are still some flaws.

One of the first thoughts is that the IPV6 protocol addresses used in Windows Server 2008 and Windows 7 operating systems are still random interface identifiers. Although the Windows 7 operating system has proven to be ready for IPV6, there is still a difference from the intended goal.

The IPV6 address setting should not be used this way. In fact, an IPV6 address device should use NDP (Neighbor Discovery Protocol) to determine its network status and interface identity and automatically configure a 128-bit IPV6 address. The relevant provisions on the allocation of IPV6 protocol, detailed in documents IETF (Internet Engineering Task Force) is given, the file includes:

IETF RFC 2373 (IPV6 addressing architecture)

IETF RFC 2464 (IPV6 protocol data packet transmission over Ethernet)

RFC 4941 (IPV6 extension confidentiality stateless address autoconfiguration)

Microsoft There seems to be some confusion as to how the interface identification should be generated, although Microsoft engineers have helped in the writing of RFC 4941. Of course, you can still force your Windows 7 Caozuoxitong IPV6 address with the correct configuration by running the following command in the DOS interface to:

netsh interface IPV6 set global randomizeidentifiers = disabled < Br>

It is recommended that you put these commands in a batch file or login file to automatically run the above commands each time you start Windows 7. Doing so will prevent you from having problems with the IPV6 protocol with other Windows 7 systems or network devices that support IPV6, such as Cisco's Catalyst switches.

If Windows 7 supports the SEND Secure Neighbor Discovery Protocol (RFC 3971), that's a good thing. SEND is a more secure version of NDP. With SEND, you can verify that the devices on your LAN are safe and effective.

Unfortunately, although Microsoft has helped in the process of writing the SEND specification, Windows 7 is still not implemented in the system. Some major network equipment vendors, such as Cisco and Juniper Networks, have implemented support for SEND. It is hoped that Microsoft will implement SEND support in all of its operating systems in the next release of the service patch, as well as the implementation of the correct IPV6 address configuration method mentioned earlier. After all, in the face of the crisis on the IPv4 protocol address, it would be better to eliminate potential implementation issues and security concerns related to the IPV6 protocol address earlier.