jako "zjišťovače" adres jsem použil např.
http://www.showmyip.com/ a
http://ipv4.whatismyv6.com/. Při pokusu otevřít
http://ipv6.whatismyv6.com/ dostanu error 404.
//Při instalaci jsem se řídil návodem na
http://wiki.ubuntu.cz/ipv6. Vše proběhlo v pořádku až do věty "To je vše, nyní máte veřejnou IPv6 adresu."
//EDIT
přikládám výpis z aiccu test
####### AICCU Quick Connectivity Test
#######
####### [1/8] Ping the IPv4 Local/Your Outer Endpoint (85.161.104.94)
### This should return so called 'echo replies'
### If it doesn't then check your firewall settings
### Your local endpoint should always be pingable
### It could also indicate problems with your IPv4 stack
PING 85.161.104.94 (85.161.104.94) 56(84) bytes of data.
64 bytes from 85.161.104.94: icmp_seq=1 ttl=64 time=0.021 ms
64 bytes from 85.161.104.94: icmp_seq=2 ttl=64 time=0.049 ms
64 bytes from 85.161.104.94: icmp_seq=3 ttl=64 time=0.048 ms
--- 85.161.104.94 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 1998ms
rtt min/avg/max/mdev = 0.021/0.039/0.049/0.013 ms
######
####### [2/8] Ping the IPv4 Remote/PoP Outer Endpoint (212.18.63.73)
### These pings should reach the PoP and come back to you
### In case there are problems along the route between your
### host and the PoP this could not return replies
### Check your firewall settings if problems occur
PING 212.18.63.73 (212.18.63.73) 56(84) bytes of data.
64 bytes from 212.18.63.73: icmp_seq=1 ttl=51 time=239 ms
64 bytes from 212.18.63.73: icmp_seq=2 ttl=51 time=239 ms
64 bytes from 212.18.63.73: icmp_seq=3 ttl=51 time=291 ms
--- 212.18.63.73 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2001ms
rtt min/avg/max/mdev = 239.017/256.689/291.142/24.364 ms
######
####### [3/8] Traceroute to the PoP (212.18.63.73) over IPv4
### This traceroute should reach the PoP
### In case this traceroute fails then you have no connectivity
### to the PoP and this is most probably the problem
sh: traceroute: not found
######
###### [4/8] Checking if we can ping IPv6 localhost (::1)
### This confirms if your IPv6 is working
### If ::1 doesn't reply then something is wrong with your IPv6 stack
PING ::1(::1) 56 data bytes
64 bytes from ::1: icmp_seq=1 ttl=64 time=0.039 ms
64 bytes from ::1: icmp_seq=2 ttl=64 time=0.053 ms
64 bytes from ::1: icmp_seq=3 ttl=64 time=0.050 ms
--- ::1 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 1998ms
rtt min/avg/max/mdev = 0.039/0.047/0.053/0.008 ms
######
###### [5/8] Ping the IPv6 Local/Your Inner Tunnel Endpoint (2001:15c0:65ff:379::2)
### This confirms that your tunnel is configured
### If it doesn't reply then check your interface and routing tables
PING 2001:15c0:65ff:379::2(2001:15c0:65ff:379::2) 56 data bytes
64 bytes from 2001:15c0:65ff:379::2: icmp_seq=1 ttl=64 time=0.035 ms
64 bytes from 2001:15c0:65ff:379::2: icmp_seq=2 ttl=64 time=0.058 ms
64 bytes from 2001:15c0:65ff:379::2: icmp_seq=3 ttl=64 time=0.060 ms
--- 2001:15c0:65ff:379::2 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 1998ms
rtt min/avg/max/mdev = 0.035/0.051/0.060/0.011 ms
######
###### [6/8] Ping the IPv6 Remote/PoP Inner Tunnel Endpoint (2001:15c0:65ff:379::1)
### This confirms the reachability of the other side of the tunnel
### If it doesn't reply then check your interface and routing tables
### Don't forget to check your firewall of course
### If the previous test was succesful then this could be both
### a firewalling and a routing/interface problem
PING 2001:15c0:65ff:379::1(2001:15c0:65ff:379::1) 56 data bytes
64 bytes from 2001:15c0:65ff:379::1: icmp_seq=1 ttl=64 time=303 ms
64 bytes from 2001:15c0:65ff:379::1: icmp_seq=2 ttl=64 time=287 ms
64 bytes from 2001:15c0:65ff:379::1: icmp_seq=3 ttl=64 time=318 ms
--- 2001:15c0:65ff:379::1 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2001ms
rtt min/avg/max/mdev = 287.070/303.035/318.138/12.706 ms
######
###### [7/8] Traceroute6 to the central SixXS machine (noc.sixxs.net)
### This confirms that you can reach the central machine of SixXS
### If that one is reachable you should be able to reach most IPv6 destinations
### Also check
http://www.sixxs.net/ipv6calc/ which should show an IPv6 connection
### If your browser supports IPv6 and uses it of course.
traceroute to noc.sixxs.net (2001:838:1:1:210:dcff:fe20:7c7c) from 2001:15c0:65ff:379::2, 30 hops max, 16 byte packets
1 gw-890.mbx-01.si.sixxs.net (2001:15c0:65ff:379::1) 683.744 ms 299.956 ms 281.101 ms
2 maribor3-vlan-4.amis.net (2001:15c0:ffff:7::1) 310.881 ms 272.084 ms 271.96 ms
3 vienna1-te-2-2.amis.net (2001:15c0:ffff:d::6) 499.955 ms 372.996 ms 474.959 ms
4 de-cix.he.net (2001:7f8::1b1b:0:1) 303.933 ms 323.967 ms 297.002 ms
5 10g-1-4.core1.ams1.ipv6.he.net (2001:470:0:47::1) 274.908 ms 298.36 ms 272.996 ms
6 ams-ix.ipv6.concepts.nl (2001:7f8:1::a501:2871:1) 298.901 ms 375.995 ms 295.969 ms
7 2001:838:5:a::2 (2001:838:5:a::2) 271.942 ms 328.806 ms 326.879 ms
8 noc.sixxs.net (2001:838:1:1:210:dcff:fe20:7c7c) 323.971 ms 328.596 ms 320.888 ms
######
###### [8/8] Traceroute6 to (
www.kame.net)
### This confirms that you can reach a Japanese IPv6 destination
### If that one is reachable you should be able to reach most IPv6 destinations
### You should also check
http://www.kame.net which should display
### a animated kame (turtle), of course only when your browser supports and uses IPv6
traceroute to
www.kame.net (2001:200:0:8002:203:47ff:fea5:3085) from 2001:15c0:65ff:379::2, 30 hops max, 16 byte packets
1 gw-890.mbx-01.si.sixxs.net (2001:15c0:65ff:379::1) 281.453 ms 283.917 ms 324.234 ms
2 maribor3-vlan-4.amis.net (2001:15c0:ffff:7::1) 251.67 ms 275.999 ms 283.953 ms
3 vienna1-te-2-2.amis.net (2001:15c0:ffff:d::6) 299.964 ms 295.995 ms 287.964 ms
4 de-cix.he.net (2001:7f8::1b1b:0:1) 271.94 ms 323.986 ms 303.968 ms
5 10g-1-4.core1.ams1.ipv6.he.net (2001:470:0:47::1) 303.942 ms 319.717 ms 271.951 ms
6 10g-1-4.core1.lon1.ipv6.he.net (2001:470:0:3f::1) 331.954 ms 323.988 ms 323.957 ms
7 10gigabitethernet4-4.core1.nyc4.he.net (2001:470:0:128::1) 407.952 ms 371.976 ms 359.908 ms
8 10gigabitethernet5-3.core1.lax1.he.net (2001:470:0:10e::1) 431.986 ms 451.988 ms 436.158 ms
9 10g-1-3.core1.pao1.ipv6.he.net (2001:470:0:34::1) 451.674 ms 486.111 ms 449.739 ms
10 3ffe:80a::b2 (3ffe:80a::b2) 424.034 ms 475.856 ms 424.418 ms
11 hitachi1.otemachi.wide.ad.jp (2001:200:0:4401::3) 552.503 ms 586.943 ms 559.946 ms
12 2001:200:0:1c04::251 (2001:200:0:1c04::251) 595.869 ms 636 ms 551.946 ms
13 2001:200:0:4803:212:e2ff:fe28:1ca2 (2001:200:0:4803:212:e2ff:fe28:1ca2) 559.943 ms 571.528 ms 555.954 ms
14 orange.kame.net (2001:200:0:8002:203:47ff:fea5:3085) 571.946 ms 579.985 ms 575.952 ms
######
###### ACCU Quick Connectivity Test (done)
-----
a také toto:
tom@tom-laptop:~$ sudo tcpdump -Xns 1500 -i sixxs
tcpdump: WARNING: sixxs: no IPv4 address assigned
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on sixxs, link-type RAW (Raw IP), capture size 1500 bytes
11:42:15.080861 IP6 :: > ff02::1: HBH ICMP6, multicast listener queryv2 [gaddr ::], length 28
0x0000: 6000 0000 0024 0001 0000 0000 0000 0000 `....$..........
0x0010: 0000 0000 0000 0000 ff02 0000 0000 0000 ................
0x0020: 0000 0000 0000 0001 3a00 0502 0000 0100 ........:.......
0x0030: 8200 7458 07d0 0000 0000 0000 0000 0000 ..tX............
0x0040: 0000 0000 0000 0000 027d 0000 .........}..
11:44:22.211603 IP6 :: > ff02::1: HBH ICMP6, multicast listener queryv2 [gaddr ::], length 28
0x0000: 6000 0000 0024 0001 0000 0000 0000 0000 `....$..........
0x0010: 0000 0000 0000 0000 ff02 0000 0000 0000 ................
0x0020: 0000 0000 0000 0001 3a00 0502 0000 0100 ........:.......
0x0030: 8200 7458 07d0 0000 0000 0000 0000 0000 ..tX............
0x0040: 0000 0000 0000 0000 027d 0000 .........}..
11:46:25.283611 IP6 fe80::14c0:65ff:379:1 > ff02::1: HBH ICMP6, multicast listener queryv2 [gaddr ::], length 28
0x0000: 6000 0000 0024 0001 fe80 0000 0000 0000 `....$..........
0x0010: 14c0 65ff 0379 0001 ff02 0000 0000 0000 ..e..y..........
0x0020: 0000 0000 0000 0001 3a00 0502 0000 0100 ........:.......
0x0030: 8200 f79d 07d0 0000 0000 0000 0000 0000 ................
0x0040: 0000 0000 0000 0000 027d 0000 .........}..
^C
3 packets captured
3 packets received by filter
0 packets dropped by kernel
-----------
//EDIT: doplněn test
//EDIT2
asi jsem měl hned na úvod napsat že jsem s linuxem začátečník, ta chyba v bodu tři je moje blbost, neměl jsem nainstalován program traceroute...
přikládám tedy výpis:
####### [3/8] Traceroute to the PoP (212.18.63.73) over IPv4
### This traceroute should reach the PoP
### In case this traceroute fails then you have no connectivity
### to the PoP and this is most probably the problem
traceroute to 212.18.63.73 (212.18.63.73), 30 hops max, 60 byte packets
1 172.18.52.14 (172.18.52.14) 117.527 ms 117.460 ms 117.419 ms
2 * * *
3 ge-1-1-0-31.prg11.ip4.tinet.net (77.67.66.41) 117.267 ms 117.235 ms 117.205 ms
4 xe-4-2-0.fra60.ip4.tinet.net (89.149.184.157) 129.148 ms xe-1-0-0.fra60.ip4.tinet.net (89.149.185.101) 129.116 ms xe-0-0-0.fra60.ip4.tinet.net (89.149.185.105) 118.128 ms
5 as1299.ip4.tinet.net (77.67.67.194) 118.146 ms as1299.ip4.tinet.net (77.67.72.14) 118.082 ms 118.121 ms
6 ffm-bb2-link.telia.net (80.91.247.188) 118.102 ms ffm-bb1-link.telia.net (80.91.251.121) 118.094 ms ffm-bb1-link.telia.net (80.91.251.249) 118.077 ms
7 win-b2-link.telia.net (80.91.252.77) 125.960 ms 125.945 ms win-b2-link.telia.net (80.91.253.128) 125.939 ms
8 amis-ic-124784-win-b2.c.telia.net (213.248.94.134) 257.934 ms amis-ic-124783-win-b2.c.telia.net (213.248.72.106) 475.712 ms amis-ic-124784-win-b2.c.telia.net (213.248.94.134) 475.656 ms
9 simbx01.sixxs.net (212.18.63.73) 343.651 ms 359.626 ms 343.576 ms
//EDIT2 - doplněn traceroute