Local win7ping VM Linux IPv6 address issues

mentioned above

The system will automatically assign a link-local (link-local) address after Windows and Linux install IPv6
That is, Ifconfig-a saw a line "Inet6 addr:fe80::20c:29ff:fed7:4214/64 scope:link", the yellow part is the IPv6 link local address.

Now assume that the IPv6 address seen through Ipconfig under Win7 is as follows:

% The index,windows term for the network interface corresponding to this IPv6 address is called the scope ID, which can be understood as an interface ordinal

And the IPv6 address of Linux is:

fe80::20c:29ff:fed7:4214

This configuration, under Linux, uses the ping6-i eth0 fe80::20c:29ff:fed7:4214 to gracefully ping the IPv6 link-local address of Windows

However, using ping-6 fe80::20c:29ff:feda:aaa under Windows cannot ping the IPv6 address of Linux.

End

Toss for a long time, thought is the reason for the local link address, and later found that the original Windows system is a very funny thing (~_~ maybe just I feel funny)

You must use the ping-6 fe80::20c:29ff:fed7:4214%17 to ping the IPv6 link-local address of Linux, which means that you need to add the% and Windows network interface numbers after the IPv6 address of Linux.

The%17 behind this is from the VMware Network Adapter VMnet8

Why VMware Network Adapter VMNET8 instead of VMware network Adapter VMnet1, because NAT mode is used

So the physical machine and the virtual machine communicate using the VMNET8 this network interface.

So it ended up like this.

Ping-6 fe80::20c:29ff:fed7:4214%17

Complete.

Local win7ping VM Linux IPv6 address issues