Koristim ipv6 zadnjih nekoliko godina, a takođe sam svim google servisima pristupao preko ipv6. Google je postavio posebam DNS koji je sve za google.com poddomene rezresavao IPv6. Bio je čak i poziv od strane he.net da se na lokalnim DNS-ovima stavi forward za zonu google.com koji je pokazivala na njihov test DNS koji vraća AAAA. Tako da ne mogu da se setim ali više od godinu ili dve google servisi sam bez problema koristio preko ipv6. Preko he.net je ping preko tunela znao povremeno da poraste kad su imali neke probleme i radove ali je od mene do ipv6.google.com bio u proseku 40ms. Sad je nešto ping povećan ali traceroute to terminacije ipv4 je nešto poveći što verovatnio znači da saobraćaj ide preko nekog rezervnog linka
d:\>ping
www.google.com -t
Pinging
www.l.google.com [2a00:1450:4016:801::1013] with 32 bytes of data:
Reply from 2a00:1450:4016:801::1013: time=41ms
Reply from 2a00:1450:4016:801::1013: time=41ms
Reply from 2a00:1450:4016:801::1013: time=41ms
Reply from 2a00:1450:4016:801::1013: time=42ms
Reply from 2a00:1450:4016:801::1013: time=139ms
Reply from 2a00:1450:4016:801::1013: time=127ms
Reply from 2a00:1450:4016:801::1013: time=52ms
Reply from 2a00:1450:4016:801::1013: time=135ms
Reply from 2a00:1450:4016:801::1013: time=40ms
Reply from 2a00:1450:4016:801::1013: time=42ms
Reply from 2a00:1450:4016:801::1013: time=109ms
Reply from 2a00:1450:4016:801::1013: time=136ms
Reply from 2a00:1450:4016:801::1013: time=41ms
Reply from 2a00:1450:4016:801::1013: time=133ms
Reply from 2a00:1450:4016:801::1013: time=51ms
Reply from 2a00:1450:4016:801::1013: time=120ms
Reply from 2a00:1450:4016:801::1013: time=75ms
Reply from 2a00:1450:4016:801::1013: time=143ms
Reply from 2a00:1450:4016:801::1013: time=45ms
Ping statistics for 2a00:1450:4016:801::1013:
Packets: Sent = 19, Received = 19, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 40ms, Maximum = 143ms, Average = 81ms
[img]http://ipv6.he.net/certification/make_badge.php?pass_name=digisoft[/img]