Manually resolve Windows7 's IPV6 support flaws

The "Remaining oil indicator" of the IPV4 address, which is closely linked to the Internet, is flashing a warning that is about to run out, with only 5% of the IPV4 address available and expected to be depleted by the fall of next year. For Microsoft's latest operating system, Windows 7, does it now have the perfect support to replace IPV4 's IPv6? I would say that, in a way, it has indeed achieved support.

In fact, Windows 7 has done a good job of supporting IPV6. It certainly works better than the previous operating systems on the IPV6, but there are still some flaws.

One of the first things I thought about was the random interface identity used to configure IPV6 addresses in Windows Server 2008 and Windows 7. Although Windows 7 should be proven to be ready for IPv6, there is a little bit of a difference from the intended goal.

IPV6 address setting is not supposed to be done this way. In fact, a IPV6 device should apply the NDP (Neighbor Discovery Protocol) to determine its network condition and interface identity and automatically configure a 128-bit IPV6 address. The relevant provisions on IPV6 address assignment are detailed in the documentation given by the IETF (Internet Engineering Task Force), which includes IETF RFC 2373 (schema), IETF RFC 2464 (transport), and RFC 4941 (configuration).

There seems to be some confusion about how the interface logo should be created, although Microsoft engineers have helped in the RfC 4941 writing process. Of course, you can still force your Windows 7 to adopt the correct IPV6 address configuration method by running the following command in the DOS interface:

netsh interface ipv6 set global

Randomizeidentifiers=disabled

It is recommended that you place these commands in a batch file or in a login file to enable the command to run automatically every time you start Windows 7 o'clock. Doing so allows you to avoid some IPv6-related problems with other Windows 7 systems or network devices that support IPV6 such as Cisco's Catalyst switch.

If Windows 7 can support the Send Secure Neighbor Discovery Protocol (RFC 3971), that would be nice. Send is a more secure version of NDP. With send, you can verify that the device in your local area network is safe and effective.

Unfortunately, Microsoft's software engineers are still not implementing it in the system, even though Microsoft has helped in writing the code for send. And some of the major network equipment suppliers, such as Cisco and Juniper Network, have implemented the support for send. It is hoped that Microsoft will be able to implement the send support in all of its operating systems in the next release of the service package, including the correct IPV6 address configuration method mentioned earlier. After all, the situation will be better in the face of the IPv4 crisis, the early elimination and IPv6-related potential implementation problems and security concerns.