What are the optimizations required by the Win7 System for IPv6 headaches?

The "remaining fuel indicator" for IPv4 addresses that are closely related to the Internet is flashing a warning that it is about to run out. Only 5% of IPv4 addresses are available, and it is expected that they will be exhausted by next autumn. For Microsoft's latest operating system Windows 7, is it now able to perfectly support replacing IPv4 IPv6? To some extent, it has already achieved support.

In fact, Windows 7 has already done a good job in IPv6 support. It certainly works better than the previous operating systems on IPv6, but there are still some flaws.

The first question that comes to my mind is whether all IPv6 addresses configured in Windows Server 2008 and Windows 7 are identified by random interfaces. Although Windows 7 has proven to be well prepared for IPv6, it is still a little different from the predefined goal.

This method should not be used to set IPv6 addresses. In fact, an IPv6 device should apply NDP (Neighbor Discovery Protocol) to determine its network conditions and interface identifiers and automatically configure a 128-bit IPv6 address. The relevant provisions on IPv6 Address allocation are described in detail in the IETF (Internet Engineering Task Group) documents, including ietf rfc 2373 (Architecture) and ietf rfc 2464 (transmission), RFC 4941 (configuration ).

Microsoft seems a little confused about how to create interface identifiers, even though Microsoft engineers have helped in writing RFC 4941. Of course, you can still force your Windows 7 to adopt the correct IPv6 address configuration method by running the following command on the DOS interface:

Netsh interface ipv6 set global

Randomizeidentifiers = disabled

We recommend that you put these commands in the batch processing file or login file to automatically run the above commands each time Windows 7 is started. This helps you avoid IPv6-related problems with other Windows 7 systems or IPv6-supported network devices, such as Cisco's Catalyst Switch.

If Windows 7 supports the SEND security Neighbor Discovery Protocol (RFC 3971), this is a good situation. SEND is a safer version of NDP. Application SEND, you can verify whether the device in your LAN is safe and valid.

Unfortunately, although Microsoft has helped in writing the SEND specification, Microsoft's software engineers still haven't implemented it in the system. Some major network equipment suppliers, such as Cisco and Juniper Networks, have enabled SEND support. It is hoped that Microsoft will support sending in all its operating systems in the next release of the service patch package, as well as the implementation of the correct IPv6 address configuration method mentioned above. After all, in the face of the IPv4 crisis, it is better to eliminate potential implementation problems and security concerns related to IPv6 earlier.