Single subnet with local link address

This configuration only requires that IPv6 be installed on at least two nodes in the same CIDR Block (that is, a link or subnet) without an intermediate router.

Displays the configurations of two nodes on a single subnet that uses the local link address.

By default, the IPv6 protocol for the Windows Server 2003 Family and Windows XP configures the local link address for each interface corresponding to the installed Ethernet adapter. The local link address has a prefix of FE80:/64. The last 64 bits of an IPv6 address are called "interface identifiers ". It is derived from the 48-bit MAC address of the network adapter. For more information, see IPv6 Interface ID.

To create an IPv6 interface Identifier from a 48-bit (6-byte) Ethernet MAC address, perform the following operations:

Insert the hexadecimal 0xFF-FE value into the third and fourth bytes of the MAC address.

Returns the global/local bits (the second lowest bits starting from the MAC address. If it is 1, it is set to 0; if it is 0, it is set to 1.

For example, for MAC address 00-60-08-52-F9-D8:

Insert the hexadecimal 0xFF-FE into the 0x08 (third byte) and 0x52 (fourth byte) of the MAC address to form a 64-bit address 00-60-08-FF-FE-52-F9-D8.

Backend the global/local bits, that is, the second bitwise of the MAC address 0x00 (first byte. The second digit of 0x00 is 0, so the inverse value is 1. The result is 0x02 for the first byte 0x00.

The IPv6 interface identifier corresponding to the Ethernet MAC address 00-60-08-52-F9-D8 is 02-60-08-FF-FE-52-F9-D8.

The local link address of a node is a combination of the FE80:/64 prefix and the 64-bit interface identifier in the colon hexadecimal notation. As a result, the local link address of the node in this example (prefix FE80:/64 and interface identifier 02-60-08-FF-FE-52-F9-D8) is FE80: 260: 8FF: FE52: F9D8.

You can use netsh interface ipv6 show interface to view the local link address. Run this command without any other parameters. The system will output a simple list:

Index Met MTU status name --- ---- ----- ------------ ----- 5 0 1500 connected to Local Area Connection 4 0 1500 connected to Local Area Connection 2 3 1 1280 connected to 6to4 Tunneling Pseudo do-Interface 2 1 1280 connected to Automatic Tunneling Pseudo-Interface 1 0 1500 connected to Loopback Pseudo-Interface

To learn more about the output, you can specify the Connection name as a command parameter (for example, netsh interface ipv6 show interface "Local Area Connection 2 "). Using the interface parameter (including the interface name or interface index number) will generate the following output, including the local link address of the connection:

Interface 4: Local Area Connection 2

Address type DAD valid life preferred life address --------- ---------- ------------ temporary preferences 20174h38m46s 3ffe: 2900: d005: f282: 4063: 32a8: 5c81: 62f2 temporarily abandon 0 s 3ffe: 2900: d005: f282: cd74: 3dd7: 857b: b57 temporary discard slave 0 s 3ffe: 2900: d005: f282: d880: d193: f2dd: d929 temporary discard 3d4h50m7s 0 s 3ffe: 2900: d005: f282: 7482: 2f05: 8129: 54ba temporary discard 2d4h52m59s 0 s 3ffe: 2900: d005: f282: d530: 25de: 57b: 7ee0 temporary discard limit 0 s 3ffe: 2900: d005: f282: c58c: 4290: 22c6: 7b3b temporary discard 4h58m42s 0 s 3ffe: 2900: d005: f282: 8464: acf0: 8393: cf6 public preference 29d23h57m19s limit fec0 :: f282: 2c0: 4fff: fe19: bad3 public preference 29d23h57m19s limit 3ffe: 2900: d005: f282: 2c0: 4fff: fe19: bad3 link preference infinite fe80: 2c0: 4fff: fe19: bad3

Connection name: Local Area Connection 2 GUID: {433F15CA-E3FD-4DE4-B3FF-7EF4B30CA4E7} status: connected indicator: 0 link MTU: 1500 byte real link MTU: 1500 byte current hop limit: 64 reachable time: arrival time of 4h43m20s base: 8h20m re-transmission interval: 16m40s DAD transmission: 1 DNS suffix: example.microsoft.com Region ID-link: 4 Region ID-site: 1 detected by neighbors: send router announcement: No forwarding data packet: no link layer address: 00-c0-4f-19-ba-d3

Interface 4 is the interface corresponding to the installed Ethernet adapter with the local link FE80: 2C0: 4FFF: FE19: BAD3.

Test the connection between two local hosts.

Perform the following steps to execute a simple ping Command (Interchanging between ICMPv6 echo request and echo Response Message) between two connected local hosts using IPv6 ):

Install IPv6.

Run the netsh interface ipv6 show interface command on host A to obtain the local link address and the interface index of the Ethernet interface.

For example, the local link address of host A is FE80: 210: 5AFF: FEAA: 20A2, and the interface index of the Ethernet interface is 4.

Run the netsh interface ipv6 show interface command on host B to obtain the local link address and the interface index of the Ethernet interface.

For example, the local link address of host B is FE80: 260: 97FF: FE02: 6EA5, and the interface index of the Ethernet interface is 3.

Ping host B using ping.exe from ingress.

For example, ping FE80 :: 260: 97FF: FE02: 6EA5% 4

When specifying the local link or the local destination address of the site, you can specify the Region ID to make the communication area (network area in a specific scope) a specific region.

For example, on a computer with multiple Ethernet adapters connected to a single link, a local link address is assigned to each Ethernet adapter. The local address of the target link in this configuration is unclear, because a specific local link address can be assigned to multiple nodes on the link, all installed Ethernet adapters can be connected to this link. To define the expected network region, use the Region ID to indicate the Ethernet adapter that sends and receives communications through it. In IPv6, the Region ID of the local link is usually the interface index displayed in the netsh interface ipv6 show interface command. Define interface indexes on each IPv6 host. Therefore, the interface index used by host A to connect to host B may be different from that used by host B to connect to host.

When a local site address is used, it may be connected to multiple sites. In this case, a site identifier is assigned to each site. To define the expected network region, use the Region ID to represent the site identifier. In IPv6, the Region ID is "Region ID-site" in the "netsh interface ipv6 show interface level = verbose" command ". If you only connect to a single site, the default site ID is 1 and you do not need to specify a Region ID. The site ID is defined locally on each IPv6 host. Therefore, the site identifier used by host A to connect to host B may be different from that used by host B to connect host.

The Region ID used to specify the included Address is expressed as Address % ZoneID.