Home 

IPV6 Addresses

Global Address:GA

Prefix: 2000::/3--the first block value is 2000-3FFF.

e.g. 2001:0:0:1::5000

1

unique local IPv6 unicast addresses—similar to 192.168.0.0/16, 172.16.0.0/12, and 10.0.0.0/8

Prefix: fd00::/8 –e.g. fd01, fd02, fd89, fdab, etc.

2

Local-Link Address:LLA –Similar to 169.254.0.0/16 prefix. One of the most useful aspects of IPv6 is its ability to automatically configure itself without the use of a stateful configuration protocol, such as Dynamic Host Configuration Protocol for IPv6 (DHCPv6).

Prefix: fe80
Network ID: fe80::/64

e.g. fe80::b11a:da9b:95e1:f763%12

3

Zone ID: adapter identification (local use only)

6to4 address

1

6to4 uses the global address prefix 2002:WWXX:YYZZ::/48.

WW:191--bf
XX:121 --79
YY:9 --9
ZZ:be

WWXX:YYZZ is the colon-hexadecimal representation of a IPv4 address (w.x.y.z).

Tunnel adapter 6TO4 Adapter:

Connection-specific DNS Suffix . :
IPv6 Address. . . . . . . . . . . : 2002:bf79:9be::bf79:9be
Default Gateway . . . . . . . . . : 2002:c058:6301::c058:6301

Teredo

netsh interface teredo set state client teredo.ipv6.microsoft.com 60 34567

Tunnel adapter Teredo Tunneling Pseudo-Interface:

Connection-specific DNS Suffix . :
IPv6 Address. . . . . . . . . . . : 2001:0:4137:9e50:14cb:1e69:4086:f641
Link-local IPv6 Address . . . . . : fe80::14cb:1e69:4086:f641%30
Default Gateway . . . . . . . . . :

Address for teredo server (teredo.ipv6.microsoft.com) is 65.55.158.80.

The colon representation of hexadecimal for 65.55.158.80 is 4137:9e50.

Teredo adapter address starts from 2001.

Address selection

By default, the ipv6 address is preferred over ipv4 address. For example,

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::ed:bae2:898c:2a36%12
IPv4 Address. . . . . . . . . . . : 191.121.9.190
Subnet Mask . . . . . . . . . . . : 255.255.128.0
Default Gateway . . . . . . . . . : 191.121.0.210

C:\Windows\system32>ping win72

Pinging Win72 [fe80::ed:bae2:898c:2a36%12] with 32 bytes of data:
Reply from fe80::ed:bae2:898c:2a36%12: time<1ms
Reply from fe80::ed:bae2:898c:2a36%12: time<1ms

Change the precedence of the prefixes:

netsh interface ipv6>

add prefix ::/96 50 0 ----IPv4 address --highest precedence
add prefix ::1/128 40 1
add prefix ::/0 30 2
add prefix 2001::/32 20 3
add prefix 2002::/16 10 4
add prefix fe80::/16 5 5 ---IPv6 Link-local address --lowerest precedence

or

netsh interface ipv6>

set prefix ::/96 50 0 ----IPv4 address --highest precedence
set prefix ::1/128 40 1
set prefix ::/0 30 2
set prefix 2001::/32 20 3
set prefix 2002::/16 10 4
add prefix fe80::/16 5 5 ---IPv6 Link-local address --lowerest precedence

C:\Windows\system32>ping win72

Pinging Win72 [191.121.9.190] with 32 bytes of data:
Reply from 191.121.9.190: bytes=32 time<1ms TTL=128
Reply from 191.121.9.190: bytes=32 time<1ms TTL=128

how about move the 2001::/32 prefix to the top precedence?

netsh interface ipv6 set prefix 2001::/32 60 0

C:\Windows\system32>netsh interface ipv6 show prefix
Querying active state...

Precedence Label Prefix
---------- ----- --------------------------------
60 0 2001::/32
50 0 ::/96
40 1 ::1/128
30 2 ::/0
10 4 2002::/16
5 5 fe80::/16

C:\Windows\system32>ping win72

Pinging Win72 [2001:0:4137:9e50:14cb:1e69:4086:f641] with 32 bytes of data:
Reply from 2001:0:4137:9e50:14cb:1e69:4086:f641: time<1ms
Reply from 2001:0:4137:9e50:14cb:1e69:4086:f641: time<1ms

C:\Windows\system32>ping localhost

Pinging Win72 [::1] with 32 bytes of data:
Reply from ::1: time<1ms
Reply from ::1: time<1ms

Modify the hosts file

127.0.0.1 localhost

C:\Windows\system32>ping localhost

Pinging Win72 [127.0.0.1] with 32 bytes of data:
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128