Test your connectivity for World IPv6 Day

[Bjørn Mork]

SM <sm at resistor.net> writes:
> Hi Pekka,
> At 22:58 29-05-2011, Pekka Savola wrote:
>> FWIW, Afrinic (2001:42d0::200:2:1) is broken here from from both
>> AS719 and AS1741.
>>
>>TCP traceroute dies (or sometimes goes to hop 7):
>>
>>  6  afrinicza-2-pt.tunnel.tserv18.fra1.ipv6.he.net
>> (2001:470:15:101::2)  275.314 ms  262.993 ms  263.262 ms
>>  7  gw.vlan100.ar02.jnb.afrinic.net (2001:42d0:0:100::4)  3270.314 ms !H * *
>
> This is what you should be seeing:
>
>  7  gw.vlan100.ar02.jnb.afrinic.net  347.588 ms  347.447 ms  347.273 ms
>  8  www.afrinic.net  345.85 ms  345.813 ms  345.638 ms

Is that through the London or Frankfurt tunnel?  I also have a working
connection, apparently via London:

traceroute to www.afrinic.net (2001:42d0::200:2:1), 30 hops max, 80 byte packets
 1  2001:4600:10:101::1 (2001:4600:10:101::1)  13.784 ms  13.735 ms  22.075 ms
 2  * * *
 3  * * *
 4  * * *
 5  afrinicza-1-pt.tunnel.tserv17.lon1.ipv6.he.net (2001:470:14:cb::2)  317.969 ms  317.951 ms  317.933 ms
 6  10gigabitethernet1-1.core1.lon1.he.net (2001:7f8:4::1b1b:1)  81.300 ms  67.362 ms  67.318 ms
 7  gige-g0-1.tserv17.lon1.ipv6.he.net (2001:470:0:a3::2)  63.917 ms  52.410 ms  56.348 ms
 8  afrinicza-1-pt.tunnel.tserv17.lon1.ipv6.he.net (2001:470:14:cb::2)  299.849 ms  295.446 ms  295.450 ms
 9  gw.vlan100.ar02.jnb.afrinic.net (2001:42d0:0:100::4)  255.592 ms  251.417 ms  255.750 ms
10  www.afrinic.net (2001:42d0::200:2:1)  255.719 ms  251.927 ms  251.883 ms

But they are obviously doing a bit of magic, since hop 5 and 8 claim to
be the same.  And tracing the tunnel endpoints send me on "Tour de
Hurricane Electric", also with a double London router entry:

traceroute to 2001:470:14:cb::2 (2001:470:14:cb::2), 30 hops max, 80 byte packets
 1  2001:4600:10:101::1 (2001:4600:10:101::1)  18.268 ms  18.233 ms  18.218 ms
 2  * * *
 3  * * *
 4  * * *
 5  10gigabitethernet5-3.core1.lon1.he.net (2001:470:0:1d2::1)  74.161 ms  78.463 ms  78.445 ms
 6  10gigabitethernet1-3.core1.sto1.he.net (2001:7f8:d:fb::187)  46.436 ms  35.647 ms  35.596 ms
 7  10gigabitethernet3-3.core1.fra1.he.net (2001:470:0:110::1)  67.554 ms  43.925 ms  55.435 ms
 8  10gigabitethernet5-3.core1.lon1.he.net (2001:470:0:1d2::1)  67.408 ms  52.289 ms  63.451 ms
 9  gige-g0-1.tserv17.lon1.ipv6.he.net (2001:470:0:a3::2)  63.401 ms  55.467 ms  55.936 ms
10  afrinicza-1-pt.tunnel.tserv17.lon1.ipv6.he.net (2001:470:14:cb::2)  300.162 ms  299.960 ms  303.893 ms

traceroute to 2001:470:14:cb::1 (2001:470:14:cb::1), 30 hops max, 80 byte packets
 1  2001:4600:10:101::1 (2001:4600:10:101::1)  78.756 ms  83.200 ms  83.176 ms
 2  * * *
 3  * * *
 4  * * *
 5  10gigabitethernet5-3.core1.lon1.he.net (2001:470:0:1d2::1)  151.351 ms  151.332 ms  151.314 ms
 6  10gigabitethernet1-3.core1.sto1.he.net (2001:7f8:d:fb::187)  122.949 ms  103.534 ms  115.918 ms
 7  10gigabitethernet3-3.core1.fra1.he.net (2001:470:0:110::1)  127.891 ms  95.865 ms  71.526 ms
 8  10gigabitethernet5-3.core1.lon1.he.net (2001:470:0:1d2::1)  87.012 ms  86.981 ms  71.634 ms
 9  gige-g0-1.tserv17.lon1.ipv6.he.net (2001:470:0:a3::2)  55.435 ms  56.443 ms  56.340 ms


The reversed RTT/TTL and strange detour are probably symptoms of too
much creativeness.  I wouldn't be surprised if this had something to do
with the connectivity problems...

KISS, please.



Bjørn