[ipv6-tf] opóźnienia w polskim światku ipv6
Marcin Gondek
drixter w e-utp.net
Czw, 6 Sty 2011, 22:42:04 CET
Wiadomość napisana przez Andrzej 'The Undefined' Dopierała w dniu 2011-01-06, o godz. 22:21:
> traceroute to ipv6.l.google.com (2a00:1450:8007::93) from 2a02:848:a:0:221:6bff:fe51:fd24, 30 hops max, 16 byte packets
> 1 2a02:848:a:0:20c:42ff:fe2a:302 (2a02:848:a:0:20c:42ff:fe2a:302) 6.121 ms 1.38 ms 1.06 ms
> 2 2a02:848:120:1::1 (2a02:848:120:1::1) 3.677 ms 24.113 ms 4.777 ms
> 3 2a02:848:110:1::1 (2a02:848:110:1::1) 12.726 ms 12.783 ms 34.855 ms
> 4 2a02:848:100:1::1 (2a02:848:100:1::1) 5.614 ms 27.05 ms 4.3 ms
> 5 z-atman-ipv6.perfekt.pl (2001:1a68:0:17::1) 10.53 ms 28.912 ms 18.696 ms
> 6 2001:4860:1:1:0:6094:: (2001:4860:1:1:0:6094::) 49.415 ms 46.662 ms 59.83 ms
> 7 2001:4860::1:0:11 (2001:4860::1:0:11) 39.449 ms 46.087 ms 59.537 ms
> 8 2001:4860::2:0:48c (2001:4860::2:0:48c) 39.715 ms 47.553 ms 79.461 ms
> 9 2001:4860:0:1::c9 (2001:4860:0:1::c9) 60.205 ms 45.478 ms 40.407 ms
> 10 2a00:1450:8007::93 (2a00:1450:8007::93) 42.592 ms 85.004 ms 61.226 ms
>
traceroute6 to 2a00:1450:8007::93 (2a00:1450:8007::93) from 2001:16b0:1007:ffee:21e:c2ff:fead:c353, 64 hops max, 12 byte packets
1 r1-waw-mt433-fe1-vlan100.core.pl.ipv6.e-utp.net 0.971 ms 0.730 ms 0.739 ms
2 e-utp-2-crowley.ipv6.crowley.pl 17.465 ms 20.104 ms 18.251 ms
3 m120waw-2-mx1waw.ipv6.crowley.pl 18.101 ms 17.769 ms 17.478 ms
4 de-cix10.net.google.com 43.717 ms 44.710 ms 44.634 ms
5 2001:4860::1:0:10 47.041 ms 45.369 ms 89.567 ms
6 2001:4860::2:0:48c 179.272 ms
2001:4860::2:0:48d 44.415 ms 45.191 ms
7 2001:4860:0:1::c9 52.206 ms
2001:4860:0:1::c7 45.045 ms 56.304 ms
8 2a00:1450:8007::93 44.854 ms 45.397 ms 45.283 ms
>
> traceroute to plum.ipv6.man.poznan.pl (2001:808::2) from 2a02:848:a:0:221:6bff:fe51:fd24, 30 hops max, 16 byte packets
> 1 2a02:848:a:0:20c:42ff:fe2a:302 (2a02:848:a:0:20c:42ff:fe2a:302) 1.511 ms 1.305 ms 1.115 ms
> 2 2a02:848:120:1::1 (2a02:848:120:1::1) 48.871 ms 23.954 ms 19.682 ms
> 3 2a02:848:110:1::1 (2a02:848:110:1::1) 39.602 ms 26.002 ms 39.703 ms
> 4 2a02:848:100:1::1 (2a02:848:100:1::1) 4.274 ms 21.326 ms 20.787 ms
> 5 z-atman-ipv6.perfekt.pl (2001:1a68:0:17::1) 41.234 ms 30.508 ms 51.594 ms
> 6 r7-glo.ipv6-core.atman.pl (2001:1a68::6) 59.81 ms 71.415 ms 87.296 ms
> 7 ix-9-2.har1.w1t-warsaw.ipv6.as6453.net (2001:5a0:900:100::d) 61.312 ms 52.298 ms 59.988 ms
> 8 pos2-0-0.mcore3.ldn-london.ipv6.as6453.net (2001:5a0:c00:300::3d) 60.051 ms 60.957 ms 59.16 ms
> 9 2001:450:2008:48::1 (2001:450:2008:48::1) 120.134 ms 146.559 ms 140.155 ms
> 10 2001:450:2002:70::2 (2001:450:2002:70::2) 59.165 ms 66.977 ms 60.207 ms
> 11 so-1-0-0.rt1.poz.pl.geant2.net (2001:798:cc:1401:2301::2) 79.785 ms 74.243 ms 79.711 ms
> 12 pionier-bckp-gw.rt1.poz.pl.geant2.net (2001:798:23:10aa::6) 119.878 ms 83.556 ms 99.627 ms
> 13 z-poznan-gw1.pozman.10gb.pol34.pl (2001:b10:c000:2::2) 123.307 ms 70.715 ms 89.996 ms
> 14 plum.ipv6.man.poznan.pl (2001:808::2) 79.156 ms 69.844 ms 80.714 ms
traceroute6 to 2001:808::2 (2001:808::2) from 2001:16b0:1007:ffee:21e:c2ff:fead:c353, 64 hops max, 12 byte packets
1 r1-waw-mt433-fe1-vlan100.core.pl.ipv6.e-utp.net 0.760 ms 0.532 ms 0.494 ms
2 e-utp-2-crowley.ipv6.crowley.pl 17.914 ms 17.680 ms 20.587 ms
3 xe-3-4-902.r00.wrswpl01.pl.bb.gin.ntt.net 166.913 ms 205.800 ms 203.894 ms
4 xe-4-3.r01.frnkge03.de.bb.gin.ntt.net 41.710 ms 40.657 ms 38.853 ms
5 ffm-b2-link.telia.net 40.570 ms 41.484 ms 39.554 ms
6 ffm-b7-v6.telia.net 69.675 ms 40.184 ms 40.671 ms
7 as0.rt1.gen.ch.geant2.net 52.005 ms 52.584 ms 52.188 ms
8 so-4-0-0.rt1.fra.de.geant2.net 51.937 ms 52.533 ms 51.807 ms
9 so-1-0-0.rt1.poz.pl.geant2.net 64.591 ms 65.006 ms 64.860 ms
10 pionier-bckp-gw.rt1.poz.pl.geant2.net 64.986 ms 66.811 ms 65.351 ms
11 z-poznan-gw1.pozman.10gb.pol34.pl 64.752 ms * 65.578 ms
12 plum.ipv6.man.poznan.pl 65.773 ms 65.433 ms 64.896 ms
To pewnie polityczne, chyba że PCSS/Pionier zapnie sesje w RS IPv6 w PLIX.
> undefine w uml:~$ traceroute6 plwaw01.sixxs.net
> traceroute to plwaw01.sixxs.net (2001:6a0:1:1::2) from 2a02:848:a:0:221:6bff:fe51:fd24, 30 hops max, 16 byte packets
> 1 2a02:848:a:0:20c:42ff:fe2a:302 (2a02:848:a:0:20c:42ff:fe2a:302) 1.517 ms 1.426 ms 1.144 ms
> 2 2a02:848:120:1::1 (2a02:848:120:1::1) 37.93 ms 25.962 ms 2.375 ms
> 3 2a02:848:110:1::1 (2a02:848:110:1::1) 2.929 ms 80.919 ms 2.925 ms
> 4 2a02:848:100:1::1 (2a02:848:100:1::1) 14.893 ms 8.371 ms 36.623 ms
> 5 z-atman-ipv6.perfekt.pl (2001:1a68:0:17::1) 40.311 ms 53.788 ms 19.429 ms
> 6 r7-glo.ipv6-core.atman.pl (2001:1a68::6) 39.935 ms 32.523 ms 19.98 ms
> 7 ix-9-2.har1.w1t-warsaw.ipv6.as6453.net (2001:5a0:900:100::d) 41.095 ms 52.297 ms 40.387 ms
> 8 pos2-0-0.mcore3.ldn-london.ipv6.as6453.net (2001:5a0:c00:300::3d) 59.237 ms 83.427 ms 40.324 ms
> 9 2001:450:2008:48::1 (2001:450:2008:48::1) 149.98 ms 122.174 ms 119.562 ms
> 10 2001:450:2002:70::2 (2001:450:2002:70::2) 60.022 ms 64.451 ms 61.197 ms
> 11 so-1-0-0.rt1.poz.pl.geant2.net (2001:798:cc:1401:2301::2) 72.566 ms 110.764 ms 60.255 ms
> 12 pionier-bckp-gw.rt1.poz.pl.geant2.net (2001:798:23:10aa::6) 59.922 ms 92.748 ms 100.37 ms
> 13 2001:b10:c000:1::23 (2001:b10:c000:1::23) 69.977 ms 74.942 ms 69.682 ms
> 14 2001:b10:c000:3::6 (2001:b10:c000:3::6) 80.627 ms 92.614 ms 60.602 ms
> 15 2001:6a0:1:1::2 (2001:6a0:1:1::2) 69.054 ms 85.867 ms 99.164 ms
traceroute6 to plwaw01.sixxs.net (2001:6a0:1:1::2) from 2001:16b0:1007:ffee:21e:c2ff:fead:c353, 64 hops max, 12 byte packets
1 r1-waw-mt433-fe1-vlan100.core.pl.ipv6.e-utp.net 0.846 ms 0.518 ms 0.654 ms
2 e-utp-2-crowley.ipv6.crowley.pl 22.138 ms 20.385 ms 18.636 ms
3 icm.link1.rs1.ipv6.plix.pl 21.911 ms 24.645 ms 27.481 ms
4 2001:6a0:1:1::2 18.128 ms 19.741 ms 18.126 ms
Brak ATMAN w PLIX.
> traceroute to 2A02:2448:FFFF::1 (2a02:2448:ffff::1) from 2a02:848:a:0:221:6bff:fe51:fd24, 30 hops max, 16 byte packets
> 1 2a02:848:a:0:20c:42ff:fe2a:302 (2a02:848:a:0:20c:42ff:fe2a:302) 1.365 ms 1.36 ms 2.356 ms
> 2 2a02:848:120:1::1 (2a02:848:120:1::1) 7.122 ms 5.695 ms 2.69 ms
> 3 2a02:848:110:1::1 (2a02:848:110:1::1) 3.454 ms 9.492 ms 19.577 ms
> 4 2a02:848:100:1::1 (2a02:848:100:1::1) 22.819 ms 22.111 ms 39.162 ms
> 5 z-atman-ipv6.perfekt.pl (2001:1a68:0:17::1) 40.559 ms 33.554 ms 39.598 ms
> 6 r5-prg.ipv6-core.atman.pl (2001:1a68::bb) 27.906 ms 34.717 ms 8.57 ms
> 7 v6-decix-to-tkk.tkk.net.pl (2001:7f8::78ff:0:1) 60.776 ms 77.192 ms 76.144 ms
> 8 2a02:2448:ffff::1 (2a02:2448:ffff::1) 100.072 ms 64.358 ms 89.798 ms
>
traceroute6 to 2a02:2448:ffff::1 (2a02:2448:ffff::1) from 2001:16b0:1007:ffee:21e:c2ff:fead:c353, 64 hops max, 12 byte packets
1 r1-waw-mt433-fe1-vlan100.core.pl.ipv6.e-utp.net 0.733 ms 0.757 ms 0.474 ms
2 e-utp-2-crowley.ipv6.crowley.pl 25.420 ms 17.961 ms 17.804 ms
3 tkk.link1.rs1.ipv6.plix.pl 26.580 ms 27.181 ms 27.628 ms
4 2a02:2448:ffff::1 28.478 ms 27.776 ms 27.533 ms
Jak wyżej. Brak ATMAN w PLIX.
> Ogolnie - gdzie nie patrze to opoznienia/jitter spory. Wina mojego isp? Czy
> wszedzie kroluja egzotyczne trasy? :)
>
Chyba mam lepiej po ostatnich poprawkach w CDP :-)
--
Marcin Gondek / Drixter
e-utp.net
_______________________________________________
ipv6-tf mailing list
ipv6-tf w pl.ipv6tf.org
http://www.pl.ipv6tf.org/cgi-bin/mailman/listinfo/ipv6-tf
Więcej informacji o liście ipv6-tf