How can I configure ipv6 correctly for your windows 7?

Various information shows that the "remaining fuel indicator" of IPv4 addresses closely related to the Internet is flashing a warning that the IPv4 address is about to run out. Only 5% of IPv4 addresses are available, it is expected to be exhausted by the fall of next year. For Microsoft's latest operating system Windows 7, is it now able to perfectly support the replacement of IPv4 IPV6 addresses?

In fact, compared with the previous operating systems, the Windows 7 operating system has already made great support for IPV6; however, there are still some flaws.

The first problem that comes to mind is that the IPV6 protocol addresses configured in Windows Server 2008 and Windows 7 are still identified by random interfaces. Although the Windows 7 operating system has proved to be ready 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 address device should apply the 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 protocol allocation are described in detail in the IETF Internet Engineering Task Group. The documents include:

Ietf rfc 2373IPV6 addressing system architecture)

Ietf rfc 2464IPV6 protocol data packets are transmitted over Ethernet)

Security Extension automatically configured for stateless addresses in RFC 4941IPV6)

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 operating system 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 problems related to other Windows 7 systems or IPV6-supported network devices, such as Cisco Catalyst switches.

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, Windows 7 still does not implement 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 IPv4 protocol address crisis, it is better to eliminate potential implementation problems and security concerns related to IPV6 protocol addresses earlier.