Google and IPv6
Steve Wilcox
stevewilcox at google.com
Wed Mar 19 12:16:37 CET 2008
Hi Tim,
so I'm trying to figure out your connectivity here..
>From your traceroute below I see:
2002:0000:: == 26943 (Your.org EU)
2001:4978:: == 19255 (Your.org NA)
2001:0590:: == 4436 (nLayer)
2001:0504:: == Equinix
2001:4860:: == 15169 (Google)
And from here I see the following route:
2002::/16 *[BGP/170] 2w5d 17:47:22, MED 1000, localpref 1000, from
2001:7f8:1::a500:6777:1
AS path: 26943 I
and traceroute:
traceroute6 to 2002:4775:eda1:2::3:0 (2002:4775:eda1:2::3:0) from
2001:7f8:1::a501:5169:1, 30 hops max, 12 byte packets
1 ge-0.3.0.core1.ams.bb6.your.org (2001:7f8:1::a502:6943:1) 1.052 ms
0.974 ms 0.904 ms
2 stf.ams.bb6.your.org (2001:4978:2:410:211:43ff:fee8:2c76) 0.773 ms
0.836 ms 0.898 ms
3 2002:4775:eda1:: (2002:4775:eda1::) 177.692 ms 177.495 ms 177.302 ms
4 2002:4775:eda1:: (2002:4775:eda1::) 3229.121 ms !A 3178.494 ms !A
3179.705 ms !A
Any suggestion on how to fix it?
Steve
On Wed, Mar 19, 2008 at 8:28 AM, Tim <tim-projects at sentinelchicken.org>
wrote:
>
> Hello,
>
> Been using ipv6.google.com for a couple of days now as my default search
> engine. Been noticing some broken connectivity off and on for the last
> day though, so thought I would bring it up. Essentially requests are
> just hanging indefinitely. I'm really not well versed in debugging
> routing issues, but here's what I'm seeing:
>
> ~> host ipv6.google.com
> ipv6.google.com is an alias for ipv6.l.google.com.
> ipv6.l.google.com has IPv6 address 2001:4860:0:2001::68
>
> ~> tracepath6 -n 2001:4860:0:2001::68
> 1?: [LOCALHOST] pmtu 1500
> 1: 2002:4775:eda1:2:: 0.409ms
> 1: 2002:4775:eda1:2:: 0.322ms
> 2: 2002:4775:eda1:2:: 0.329ms pmtu 1480
> 2: 2002:c058:6301:: 80.294ms
> 2: 2002:c058:6301:: 79.992ms
> 3: 2001:4978:1:410::ffff 82.114ms asymm 4
> 4: 2001:590::451f:6f15 82.759ms
> 5: 2001:590::451f:6f85 81.871ms asymm 6
> 6: 2001:590::4516:8e3d 100.075ms asymm 7
> 7: 2001:504:0:2:0:1:5169:1 182.722ms !A
> Resume: pmtu 1480
>
> ~> traceroute6 -n 2001:4860:0:2001::68
> traceroute to 2001:4860:0:2001::68 (2001:4860:0:2001::68) from
> 2002:4775:eda1:2::3:0, 30 hops max, 24 byte packets
> 1 2002:4775:eda1:2:: 0.163 ms 0.077 ms 0.075 ms
> 2 2002:c058:6301:: 75.727 ms 75.02 ms 74.404 ms
> 3 2001:4978:1:410::ffff 75.002 ms 77.831 ms 74.701 ms
> 4 2001:590::451f:6f15 75.074 ms 75.207 ms 74.954 ms
> 5 2001:590::451f:6f85 74.655 ms 75.046 ms 77.293 ms
> 6 2001:590::4516:8e3d 94.994 ms 95.442 ms 92.119 ms
> 7 2001:504:0:2:0:1:5169:1 179.96 ms 177.397 ms 177.797 ms
> 8 * * *
> 9 2001:4860:0:2001::68 180.935 ms 179.936 ms 180.038 ms
>
>
> As you can see, I'm using 6to4. I'm able to reach my web server which
> is also on 6to4, but that's probably not a surprise. The other service
> I use over v6 is IRC, and that's not on 6to4:
>
> ~> host ipv6.chat.freenode.net
> ipv6.chat.freenode.net has IPv6 address 2001:6b0:e:2018::172
> ipv6.chat.freenode.net has IPv6 address 2001:1418:13:1::25
>
> ~> tracepath6 -n 2001:1418:13:1::25
> 1?: [LOCALHOST] pmtu 1500
> 1: 2002:4775:eda1:2:: 1.523ms
> 1: 2002:4775:eda1:2:: 0.326ms
> 2: 2002:4775:eda1:2:: 0.329ms pmtu 1480
> 2: 2002:c058:6301:: 80.374ms
> 2: 2002:c058:6301:: 79.961ms
> 3: 2001:4978:1:410::ffff 82.109ms asymm 4
> 4: 2001:1838::40ca:6f26 82.559ms
> 5: 2001:1838::d8f6:5ff2 83.169ms asymm 6
> 6: 2001:1900:4:2::29 225.737ms asymm 8
> 7: 2001:1900:4:1::5 228.644ms
> 8: 2001:1900:6:1::1 230.432ms asymm 6
> 9: 2001:1900:6:1::1 227.034ms pmtu 1450
> 9: 2001:1900:5:2::2a 227.557ms asymm 5
> 9: 2001:1900:5:2::2a 229.557ms asymm 5
> 10: 2001:1418:1:700::a 232.490ms asymm 6
> 11: 2001:1418:13:1::25 227.824ms reached
> Resume: pmtu 1450 hops 11 back 58
>
> ~> tracepath6 -n 2001:6b0:e:2018::172
> 1?: [LOCALHOST] pmtu 1500
> 1: 2002:4775:eda1:2:: 1.089ms
> 1: 2002:4775:eda1:2:: 0.443ms
> 2: 2002:4775:eda1:2:: 0.330ms pmtu 1480
> 2: 2002:c058:6301:: 80.614ms
> 2: 2002:c058:6301:: 82.639ms
> 3: 2001:4978:1:410::ffff 83.005ms asymm 4
> 4: 2001:470:0:7f::1 83.713ms
> 5: 2001:470:0:4e::2 103.043ms
> 6: 2001:470:0:3e::2 172.584ms
> 7: 2001:470:0:3f::2 182.677ms
> 8: 2001:7f8:1::a500:2603:1 201.492ms
> 9: 2001:948:0:f03f::1 203.493ms asymm 7
> 10: 2001:948:0:f053::2 199.304ms asymm 4
> 11: 2001:6b0:dead:beef:2::de 198.864ms asymm 5
> 12: 2001:6b0:dead:beef:2::2e6 211.988ms asymm 5
> 13: 2001:6b0:e::51 211.150ms asymm 6
> 14: 2001:6b0:e::62 217.762ms asymm 7
> 15: 2001:6b0:e:2018::172 210.209ms reached
> Resume: pmtu 1480 hops 15 back 57
>
> And this seems to be working fine for me (though it did drop
> connectivity last night, but that could have just been the periodic DoS
> attacks the network receives.)
>
> However, www.arin.net is also giving me issues, as it too is hanging
> indefinitely and the tracepath doesn't look so hot:
>
> ~> host www.arin.net
> www.arin.net has address 192.149.252.7
> www.arin.net has address 199.43.0.202
> www.arin.net has IPv6 address 2001:500:4:1::80
>
> ~> tracepath6 -n 2001:500:4:1::80
> 1?: [LOCALHOST] pmtu 1500
> 1: 2002:4775:eda1:2:: 1.377ms
> 1: 2002:4775:eda1:2:: 0.324ms
> 2: 2002:4775:eda1:2:: 0.321ms pmtu 1480
> 2: 2002:c058:6301:: 80.520ms
> 2: 2002:c058:6301:: 79.490ms
> 3: 2001:4978:1:410::ffff 82.598ms asymm 4
> 4: 2001:470:0:7f::1 82.174ms
> 5: 2001:470:0:4e::2 102.798ms
> 6: 2001:470:0:36::1 110.181ms
> 7: 2001:504:0:2:0:1:745:1 207.068ms asymm 8
> 8: no reply
> 9: no reply
> 10: no reply
> ...
>
>
>
> Anything else I could run to help provide more info?
>
> thanks,
> tim
>
--
Global Infrastructure
Google Inc.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.cluenet.de/pipermail/ipv6-ops/attachments/20080319/3a478382/attachment.htm
More information about the ipv6-ops
mailing list