Article View: alt.pl.telefonia.dialog
Article #27929Czy ktoś może testuje IPv6 na sieci dialogu ?
From: pb158
Date: Wed, 08 Jun 2011 11:50
Date: Wed, 08 Jun 2011 11:50
128 lines
6248 bytes
6248 bytes
Witam, Mój router obsługuje IPv6 , dialog nie obsługuje dla końcowego usera, ale mam takie ciekawe rezultaty dzisiejszego dnia (zresztą dzisiaj jest dzień testu IPv6 ) z adresem www.google.com (router ma ustawiony mój adres IPv6 po zamianie adresu IPv4 nadanego przez dialog i mam dwa adresy w tej chwili zewnętrzne w routerze i lokalną sieć też w dwóch standardach): xxxx@xxxx:~$ ping6 www.google.com PING www.google.com(ber01s02-in-x6a.1e100.net) 56 data bytes 64 bytes from ber01s02-in-x6a.1e100.net: icmp_seq=1 ttl=56 time=77.7 ms 64 bytes from ber01s02-in-x6a.1e100.net: icmp_seq=2 ttl=56 time=78.5 ms 64 bytes from ber01s02-in-x6a.1e100.net: icmp_seq=3 ttl=56 time=77.4 ms 64 bytes from ber01s02-in-x6a.1e100.net: icmp_seq=4 ttl=56 time=81.4 ms 64 bytes from ber01s02-in-x6a.1e100.net: icmp_seq=5 ttl=56 time=79.7 ms --- www.google.com ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 4006ms rtt min/avg/max/mdev = 77.479/79.006/81.479/1.514 ms Ping IPv6 jest OK xxxx@xxxx:~$ host www.google.com www.google.com is an alias for www.l.google.com. www.l.google.com has address 209.85.149.104 www.l.google.com has address 209.85.149.99 www.l.google.com has address 209.85.149.106 www.l.google.com has address 209.85.149.105 www.l.google.com has address 209.85.149.103 www.l.google.com has address 209.85.149.147 www.l.google.com has IPv6 address 2a00:1450:4008:c00::67 Polecenie host pokazuje jedno adresowanie IPv6 w DNS, no to testujemy dalej : xxxx@xxxx:~$ ping6 2a00:1450:4008:c00::67 PING 2a00:1450:4008:c00::67(2a00:1450:4008:c00::67) 56 data bytes 64 bytes from 2a00:1450:4008:c00::67: icmp_seq=1 ttl=56 time=77.8 ms 64 bytes from 2a00:1450:4008:c00::67: icmp_seq=2 ttl=56 time=80.1 ms 64 bytes from 2a00:1450:4008:c00::67: icmp_seq=3 ttl=56 time=78.7 ms 64 bytes from 2a00:1450:4008:c00::67: icmp_seq=4 ttl=56 time=81.4 ms 64 bytes from 2a00:1450:4008:c00::67: icmp_seq=5 ttl=56 time=112 ms 64 bytes from 2a00:1450:4008:c00::67: icmp_seq=6 ttl=56 time=85.9 ms 64 bytes from 2a00:1450:4008:c00::67: icmp_seq=7 ttl=56 time=99.5 ms --- 2a00:1450:4008:c00::67 ping statistics --- 7 packets transmitted, 7 received, 0% packet loss, time 6006ms rtt min/avg/max/mdev = 77.891/88.050/112.645/12.172 ms Ping IPv6 działa bezpośrednio na adresie IPv6 :) No to jeszcze sprawdzimy odwrotnie hosta z adresu IPv6 na nazwę xxxx@xxxx:~$ host 2a00:1450:4008:c00::67 7.6.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.c.0.8.0.0.4.0.5.4.1.0.0.a.2.ip6.arpa domain name pointer ber01s02-in-x67.1e100.net. Jak już to może jeszcze traceroute : xxxx@xxxx:~$ traceroute6 2a00:1450:4008:c00::67 traceroute to 2a00:1450:4008:c00::67 (2a00:1450:4008:c00::67), 30 hops max, 80 byte packets 1 fritz.box (2002:4e09:47fe:0:224:feff:fe61:f16) 12.896 ms 12.836 ms 12.789 ms 2 2002:c058:6301::1 (2002:c058:6301::1) 64.432 ms 64.275 ms 66.146 ms 3 gige-g2-6.core1.fra1.he.net (2001:470:0:150::1) 68.020 ms 69.866 ms 72.083 ms 4 de-cix10.net.google.com (2001:7f8::3b41:0:1) 74.191 ms 121.837 ms 81.793 ms 5 2001:4860::1:0:11 (2001:4860::1:0:11) 78.686 ms 81.647 ms 82.498 ms 6 2001:4860::1:0:fdd (2001:4860::1:0:fdd) 95.494 ms 81.926 ms 81.802 ms 7 2001:4860::1:0:60d (2001:4860::1:0:60d) 88.383 ms 77.688 ms 79.232 ms 8 2001:4860:0:1::217 (2001:4860:0:1::217) 76.169 ms 89.692 ms 89.650 ms 9 ber01s02-in-x67.1e100.net (2a00:1450:4008:c00::67) 83.336 ms 83.100 ms 84.900 ms Teraz z nazwą : xxxx@xxxx:~$ traceroute6 www.google.com traceroute to www.google.com (2a00:1450:4008:c00::63), 30 hops max, 80 byte packets 1 fritz.box (2002:4e09:47fe:0:224:feff:fe61:f16) 12.773 ms 12.737 ms 12.717 ms 2 2002:c058:6301::1 (2002:c058:6301::1) 62.735 ms 64.751 ms 66.843 ms 3 gige-g2-6.core1.fra1.he.net (2001:470:0:150::1) 68.517 ms 69.332 ms 82.116 ms 4 de-cix10.net.google.com (2001:7f8::3b41:0:1) 74.246 ms 77.411 ms 76.405 ms 5 2001:4860::1:0:11 (2001:4860::1:0:11) 78.309 ms 81.877 ms 83.433 ms 6 2001:4860::1:0:fdd (2001:4860::1:0:fdd) 94.237 ms 80.698 ms 83.054 ms 7 2001:4860::1:0:60d (2001:4860::1:0:60d) 90.459 ms 76.074 ms 79.842 ms 8 2001:4860:0:1::215 (2001:4860:0:1::215) 86.284 ms 81.129 ms 80.746 ms 9 ber01s02-in-x63.1e100.net (2a00:1450:4008:c00::63) 78.384 ms 79.760 ms 80.954 ms Jakoś to ładnie wszystko działa, bez faktycznego zakończenia łącza dialogu w IPv6. Na koniec zwykły traceroute po IPv4: xxxx@xxxx:~$ traceroute www.google.com traceroute to www.google.com (209.85.149.103), 30 hops max, 60 byte packets 1 fritz.box (192.168.10.1) 0.414 ms 0.625 ms 0.742 ms 2 static-87-105-24-1.ssp.dialog.net.pl (87.105.24.1) 24.041 ms 29.054 ms 29.035 ms 3 r-1-br-10GE100-war.warszawa.dialog.net.pl (217.30.128.78) 45.134 ms 45.128 ms 48.759 ms 4 de-cix20.net.google.com (80.81.193.108) 98.326 ms 73.608 ms 73.520 ms 5 209.85.255.176 (209.85.255.176) 72.437 ms 75.155 ms 77.873 ms 6 216.239.48.11 (216.239.48.11) 88.266 ms 82.186 ms 84.211 ms 7 216.239.48.5 (216.239.48.5) 92.883 ms 83.729 ms 78.028 ms 8 209.85.254.21 (209.85.254.21) 77.893 ms 209.85.254.29 (209.85.254.29) 87.818 ms 87.817 ms 9 ber01s02-in-f103.1e100.net (209.85.149.103) 80.898 ms 82.244 ms 84.545 ms Może ktoś jeszcze poeksperymentuje. PZDR
Technical Details
Message-ID:
<isnnll$c97$1@news.dialog.net.pl>Path:
mbox-mo1.pugleaf.net!news-archive.icm.edu.pl!news.gazeta.pl!newsfeed.pionier.net.pl!news.dialog.net.pl!not-for-mailShow Full Headers
Complete Article Headers
Path: mbox-mo1.pugleaf.net!news-archive.icm.edu.pl!news.gazeta.pl!newsfeed.pionier.net.pl!news.dialog.net.pl!not-for-mail From: pb158 <pb158@interia.pl> Newsgroups: alt.pl.telefonia.dialog Subject: Czy ktoś może testuje IPv6 na sieci dialogu ? Date: Wed, 08 Jun 2011 13:50:12 +0200 Organization: Dialog Net Lines: 128 Message-ID: <isnnll$c97$1@news.dialog.net.pl> NNTP-Posting-Host: static-78-9-71-254.ssp.dialog.net.pl Mime-Version: 1.0 X-Trace: news.dialog.net.pl 1307533813 12583 78.9.71.254 (8 Jun 2011 11:50:13 GMT) X-Complaints-To: abuse@dialog.net.pl NNTP-Posting-Date: Wed, 8 Jun 2011 11:50:13 +0000 (UTC) User-Agent: Mozilla/5.0 (X11; Linux i686; rv:5.0) Gecko/20110528 Thunderbird/5.0b1 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit