sammy:~# ping6 ipv6.google.com PING ipv6.google.com(2001:4860:0:2001::68) 56 data bytes 64 bytes from 2001:4860:0:2001::68: icmp_seq=1 ttl=58 time=97.7 ms 64 bytes from 2001:4860:0:2001::68: icmp_seq=2 ttl=58 time=96.9 ms 64 bytes from 2001:4860:0:2001::68: icmp_seq=3 ttl=58 time=97.2 ms 64 bytes from 2001:4860:0:2001::68: icmp_seq=4 ttl=58 time=98.0 ms sammy:~# ping google.com PING google.com (64.233.187.99) 56(84) bytes of data. 64 bytes from jc-in-f99.google.com (64.233.187.99): icmp_seq=1 ttl=246 time=94.5 ms 64 bytes from jc-in-f99.google.com (64.233.187.99): icmp_seq=2 ttl=246 time=97.7 ms 64 bytes from jc-in-f99.google.com (64.233.187.99): icmp_seq=3 ttl=246 time=93.7 ms 64 bytes from jc-in-f99.google.com (64.233.187.99): icmp_seq=4 ttl=246 time=92.5 ms(Not that much worse.)
And I can now see all the dancing logos on various websites. (it's IPv6 tradition to serve animated GIFs of your company/site logo for people accessing it over IPv6.... silly, but cute.)
Still have some work to do... I need to get the rest of my machines routing through my Linux server (the one with the tunnel), including wifi. What's the typical configuration here? DHCPv6 and broadcast the route? Or does the IPv6 stateless auto-configuration for assigning the locally-scoped/link-local/etc addresses also include smarts of hosts w/ gateways advertising that?
In any case, still clueless, but at least with the tools to get slightly less clueless now.
It's weird having my own /64. (that's 2^64 addresses for my house)