Build from 8x four-digit HEX number 1111:2222:3333:4444:5555:6666:7777:8888
2^128 Numbers 54'525'952 Numbers / m2 earth surface. As they are split in ranges for different purpose the real number is much less.
Build from 8x four-digit HEX number 1111:2222:3333:4444:5555:6666:7777:8888
2^128 Numbers 54'525'952 Numbers / m2 earth surface. As they are split in ranges for different purpose the real number is much less.
001 T TTTTT TTTTT TTTTT : RRRR RRRR NNNN NNNN : NNNN -NNNN : SSSS - SSSS : IIII - : : : - IIII
001 = FP
T = TLA ID
R = Reserve
N = NLA ID
S = SLA ID
I = Interface ID
Is about what APIPA is in IPv4
1111 1110 1000 0000 : 0 : 0 : 0 : : IIII - : : : - IIII
FE80:: Interface ID
Is equal to IPv4 Privat ranges
1111 1110 0110 0000: 0 : 0: SSSS SSSS SSSS SSSS : 0 : IIII - : : - IIII
FE60:0:0:Site:0:Interface ID
0:0:0:0:0:0:0:0:0 = :: = 0:0:0:0
0:0:0:0:0:0:0:0:1 = ::1 = 127.0.0.1 = loopback interface
0000 001 …… NSAP Address map 0000 010 …… IPX Address map
xxxx xxxx FFFF SSSS : Group ID X = FP = 1111 1111 = FF F= Flag S = Scope
0 = Reserve 1 = Node-local Scope 2 = Link-Local Scope 5 = Site-Local Scope 8 = Organization-Local Scope e = Global Scope f = Reserved
FE80::6b:28c:16D2:c97 = Host IPv6 Address FF02:: 1:FF00:0 /104 = to process all Link-local hosts of the last 24 Bit Hosts FF02:: 1:FFD2:C97 = Corresponding solicited-node Address
Bit net mask help
16:32:48:64:80:96 : 100 104 108 112 : 116 120 124 128
They are currently only assigned to routers
The following address would be encapsulated in IPv4 and sent o the destination using IPv4 0:0:0:0:0:0:W:X:Y:Z W:X:Y:Z = IPv4
2001:0:TTTT:TTTT:FFFF:UUUU:IIII:IIII 2001:0: = Teredo Prefix T = Teredo Server IP F = Flag U = UDP Port I = Host IP XOR converted To get the contained Host IP
1. Xor the IP Part 0123456789ABCDEF Hex in Teredo Number to FEDCBA9876543210 Xor Result
F5 FF:9B FE = IP in Teredo string 0A 00:64 01 = converted XOR in HEX 10.0.100.1 = IP Number Dezimal
F5.. .... = 10... 53.. .... = 172... 3F57 .... = 192.168.. 5601 .... = 169.254..
You change the network adapter on a server without uninstalling the device in windows and end up with a hidden adapter in your registry. I found a solution to remove the lost hardware from windows. Source was http://forums.techarena.in/windows-server-help/1141789.htm
If you get an error code 39 from your cdrom drive and uninstallling the driver dos not help to fix it do the following.
Info from http://www.pchell.com/hardware/cd_drive_error_code_39.shtml"