Hello Juri

On 31.08.2012 10:52, Juri Haberland wrote:
On 30/08/12 13:53, Fabian Wenk wrote:

 traceroute6 to 2001:6f8:1ccd::1 (2001:6f8:1ccd::1) from

 10  2001:6f8:1:0:87:86:71:237  26.417 ms  26.073 ms  25.206 ms
 11  * * *
 12  * * *
 13  2001:6f8:891:1::c2e9:c724  36.086 ms  38.782 ms  35.934 ms

 It took very long for hop 11 and 12, and then finished to the end
 right through. There seems to be something wrong in between. Are

The delay might just come from (failing) DNS resolution, please retry with
"-n".

I did, but as expected, this had no impact, it even took longer:

fabian@superman:~ $ time traceroute6 -n 2001:6f8:1ccd::1
traceroute6 to 2001:6f8:1ccd::1 (2001:6f8:1ccd::1) from 2001:8a8:1005:1::3, 64 hops max, 12 byte packets
 1  2001:8a8:1005:1::1  0.722 ms  0.823 ms  0.616 ms
 2  2001:8a8:0:185::1  4.417 ms  3.548 ms  4.357 ms
 3  2001:8a8:1:33::35  4.484 ms  3.484 ms  4.239 ms
 4  2001:8a8:1:1::34  4.928 ms  3.771 ms  5.611 ms
 5  2a01:f8:2006:6::1  3.733 ms  3.978 ms  5.486 ms
 6  2a01:f8:1:2:1:1:65:1  23.599 ms  22.726 ms  24.346 ms
 7  2a01:f8:1:2:1:1:4:3  36.091 ms  36.841 ms  36.093 ms
 8  2001:7f8::11ed:0:1  26.469 ms  25.718 ms  25.242 ms
 9  2001:6f8:1:0:87:86:77:248  28.078 ms  27.460 ms  27.598 ms
10  2001:6f8:1:0:87:86:71:237  24.723 ms  25.471 ms  25.479 ms
11  * * *
12  * * *
13  2001:6f8:891:1::c2e9:c724  36.971 ms  34.695 ms  39.099 ms
14  2001:6f8:891:1::c2e9:c721  33.288 ms  35.227 ms  35.216 ms
15  2001:6f8:1c00:18a::1  33.588 ms  33.215 ms  36.711 ms
16  2001:6f8:1ccd::1  63.601 ms  63.443 ms  64.057 ms

real    17m2.864s
user    0m0.011s
sys     0m0.022s
fabian@superman:~ $

This was from my FreeBSD Server, but from my Mac client it was faster, but took still longer then usual with over 1 minute:

fabian@flashback:~ $ time traceroute6 -n 2001:6f8:1ccd::1
traceroute6 to 2001:6f8:1ccd::1 (2001:6f8:1ccd::1) from 2001:8a8:1005:1:223:dfff:fedf:13c9, 64 hops max, 12 byte packets
 1  2001:8a8:1005:1::1  0.627 ms  0.597 ms  0.612 ms
 2  2001:8a8:0:185::1  4.772 ms  3.563 ms  4.338 ms
 3  2001:8a8:1:33::35  8.132 ms  4.299 ms  4.562 ms
 4  2001:8a8:1:1::34  4.480 ms  3.716 ms  4.621 ms
 5  2a01:f8:2006:6::1  4.806 ms  4.725 ms  4.675 ms
 6  2a01:f8:1:2:1:1:65:1  23.786 ms  24.524 ms  23.570 ms
 7  2a01:f8:1:2:1:1:4:3  36.288 ms  35.492 ms  36.428 ms
 8  2001:7f8::11ed:0:1  25.840 ms  25.517 ms  25.276 ms
 9  2001:6f8:1::87:86:77:248  27.132 ms  28.877 ms  30.326 ms
10  2001:6f8:1::87:86:71:237  25.253 ms  27.505 ms  24.782 ms
11  * * *
12  * * *
13  2001:6f8:891:1::c2e9:c724  36.564 ms  35.396 ms  33.232 ms
14  2001:6f8:891:1::c2e9:c721  35.351 ms  34.630 ms  33.921 ms
15  2001:6f8:1c00:18a::1  35.332 ms  34.432 ms  34.930 ms
16  2001:6f8:1ccd::1  65.496 ms  64.506 ms  64.588 ms

real    1m7.988s
user    0m0.001s
sys     0m0.006s
fabian@flashback:~ $

 IPv6 connections from your system to other places working without
 any problems? Eventually it is probably a good idea to talk to
 your tunnel broker. ;)

I did that and he claimed that he had problems reaching the LA monitoring
station from a bunch of different systems so he suspects the problem at the
LA end ... (https://www.sixxs.net/tickets/?msg=tickets-7635746)

Eventually he did only try from sixxs.net IP addresses. When I do testing from here, it looks very good. So it could still be something on the SixXS side or their connection to the network of the monitoring station:

fabian@superman:~ $ time traceroute6 -n ntppool.net
traceroute6 to ntppool.net (2607:f238:2::4) from 2001:8a8:1005:1::3, 64 hops max, 12 byte packets
 1  2001:8a8:1005:1::1  0.744 ms  0.576 ms  0.613 ms
 2  2001:8a8:0:185::1  4.484 ms  3.482 ms  4.365 ms
 3  2001:8a8:1:33::35  4.362 ms  3.476 ms  4.362 ms
 4  2001:7f8:24::aa  4.489 ms  13.723 ms  4.488 ms
 5  2001:470:0:21c::1  19.604 ms  11.725 ms  13.429 ms
 6  2001:470:0:1d2::1  35.423 ms  30.149 ms  40.710 ms
 7  2001:470:0:128::1  112.096 ms  97.503 ms  105.047 ms
 8  2001:470:0:10e::1  162.225 ms  158.646 ms  163.863 ms
 9  2001:470:0:72::2  157.889 ms  164.128 ms  160.883 ms
10  2001:504:13::11  163.611 ms  164.872 ms  159.854 ms
11  2607:f238::cfab:1e01  164.033 ms  161.498 ms  164.616 ms
12  2607:f238:0:6::2  164.382 ms  161.148 ms  164.725 ms
13  2607:f238:2::4  161.411 ms !P  165.739 ms !P  160.887 ms !P

real    0m3.545s
user    0m0.004s
sys     0m0.000s
fabian@superman:~ $ time traceroute6 ntppool.net
traceroute6 to ntppool.net (2607:f238:2::4) from 2001:8a8:1005:1::3, 64 hops max, 12 byte packets
 1  gate1.home4u.ch  0.600 ms  0.653 ms  0.598 ms
 2  2001:8a8:0:185::1  3.481 ms  3.630 ms  3.469 ms
 3  glbix-br1-glbix-pe2.cyberlink.ch  4.356 ms  3.509 ms  3.468 ms
4 10gigabitethernet1-4.core1.zrh1.he.net 6.604 ms 9.358 ms 4.468 ms 5 10gigabitethernet5-1.core1.fra1.he.net 18.850 ms 13.545 ms 10.338 ms 6 10gigabitethernet5-3.core1.lon1.he.net 29.968 ms 35.540 ms 31.939 ms 7 10gigabitethernet7-4.core1.nyc4.he.net 97.453 ms 102.185 ms 102.510 ms 8 10gigabitethernet5-3.core1.lax1.he.net 158.279 ms 162.071 ms 159.341 ms 9 10gigabitethernet1-3.core1.lax2.he.net 160.839 ms 161.437 ms 167.327 ms
10  2001:504:13::11  172.907 ms  160.462 ms  163.989 ms
11  2607:f238::cfab:1e01  160.505 ms  165.072 ms  160.992 ms
12  xe9-4.hr01.lax2.phyber.com  161.655 ms  165.556 ms  160.266 ms
13  2607:f238:2::4  164.851 ms !P  162.320 ms !P  165.135 ms !P

real    0m27.683s
user    0m0.009s
sys     0m0.008s
fabian@superman:~ $


bye
Fabian
_______________________________________________
pool mailing list
[email protected]
http://lists.ntp.org/listinfo/pool

Reply via email to