Having noticed that Google have an IPv6 address (ipv6.google.com) I thought I'd try PING-ing that and see how it resolved. I am running IPv6 Teredo, on Windows XP SP3. From what I've read Microsoft have included IPv6 in Vista & 7 but not earlier (XP) versions?
I wasn't surprised that my browser connected ok to ipv6.google.com, put the ping result:
N:\>ping ipv6.google.com
Pinging ipv6.l.google.com [2a00:1450:400b:c00::63] with 32 bytes of data:
Reply from 2a00:1450:400b:c00::63: time=100ms
Reply from 2a00:1450:400b:c00::63: time=36ms
Reply from 2a00:1450:400b:c00::63: time=37ms
Reply from 2a00:1450:400b:c00::63: time=37ms
Seems to show even the command-prompt ping utility at least partly understands IPv6 addresses. Similarly for TRACERT
N:\>tracert ipv6.google.com
Tracing route to ipv6.l.google.com [2a00:1450:400b:c00::68]
over a maximum of 30 hops:
1 * 24 ms 23 ms 6to4.lon1.he.net [2001:470:0:161::2]
2 34 ms 25 ms 24 ms gige-g4-4.core1.lon1.he.net [2001:470:0:161::1]
3 24 ms 23 ms 24 ms 2001:7f8:4::3b41:1
4 25 ms 48 ms 24 ms 2001:4860::1:0:6
5 35 ms 36 ms 36 ms 2001:4860::1:0:278c
6 38 ms 40 ms 59 ms 2001:4860::2:0:277b
7 47 ms 56 ms 49 ms 2001:4860:0:1::395
8 37 ms 38 ms 37 ms 2a00:1450:400b:c00::68
Trace complete.
Despite that i've not seen confirmation that XP is IPv6 supported, is XP partilly or fully supported?
[Edit]
Ping and tracert also accept IPv6 addresses as inputs e.g
"tracert tracert 2a00:1450:400b:c00::68" & "ping tracert 2a00:1450:400b:c00::68"
both work too.
Edited by deleted (Sun 05-Jun-11 11:06:00)



Print Thread
deleted