I have read and followed the "Reporting Problems" section on the Contact page and am providing the following details for this report based on the list of items stated there: - I am HK19-6BONE - My POP is fihel01 - My tunnel is T6157 - I am using Debian 4.0 -- 2.6.10 #1 Sat Jul 30 21:38:11 EEST 2005 i686 GNU/Linux The last six days I have been receiving emails about my tunnel being down. This is the mail I get: --- This is the tunnelrobot at SixXS, mailing you to inform you that your tunnel to DNA Oy has not been replying to pings for a period of time Here's the information regarding the tunnel: Handle : HK19-6BONE PoP Name : fihel01 (fi.suomen2g [AS16086]) Your Location: Espoo, fi SixXS IPv6 : 2001:14b8:100:125::1/64 Your IPv6 : 2001:14b8:100:125::2/64 SixXS IPv4 : 62.78.96.38 Your IPv4 : 82.130.36.74 Last known responding: 2008-02-13 19:03:59 --- Here is the output from aiccu autotest: ####### ####### AICCU Quick Connectivity Test ####### ####### [1/8] Ping the IPv4 Local/Your Outer Endpoint (82.130.36.74) ### 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 82.130.36.74 (82.130.36.74) 56(84) bytes of data. 64 bytes from 82.130.36.74: icmp_seq=1 ttl=64 time=0.173 ms 64 bytes from 82.130.36.74: icmp_seq=2 ttl=64 time=0.109 ms 64 bytes from 82.130.36.74: icmp_seq=3 ttl=64 time=0.107 ms --- 82.130.36.74 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2000ms rtt min/avg/max/mdev = 0.107/0.129/0.173/0.033 ms ###### ####### [2/8] Ping the IPv4 Remote/PoP Outer Endpoint (62.78.96.38) ### 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 62.78.96.38 (62.78.96.38) 56(84) bytes of data. 64 bytes from 62.78.96.38: icmp_seq=1 ttl=59 time=1.18 ms 64 bytes from 62.78.96.38: icmp_seq=2 ttl=59 time=1.44 ms 64 bytes from 62.78.96.38: icmp_seq=3 ttl=59 time=1.14 ms --- 62.78.96.38 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2001ms rtt min/avg/max/mdev = 1.141/1.255/1.443/0.136 ms ###### ####### [3/8] Traceroute to the PoP (62.78.96.38) 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 62.78.96.38 (62.78.96.38), 30 hops max, 40 byte packets 1 gw-v347 (82.130.36.126) 0.572 ms 0.478 ms 0.387 ms 2 funet-tky-gw.tky.fi (82.130.63.253) 0.476 ms 0.534 ms 0.419 ms 3 dna.ficix1-ge.ficix.fi (193.110.226.20) 0.571 ms 0.639 ms 0.535 ms 4 van5r6.k.fv.fi (217.78.198.239) 1.131 ms 1.045 ms 1.004 ms 5 fihel01.sixxs.net (62.78.96.38) 1.107 ms 1.100 ms 1.051 ms ###### ###### [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.074 ms 64 bytes from ::1: icmp_seq=2 ttl=64 time=0.062 ms 64 bytes from ::1: icmp_seq=3 ttl=64 time=0.062 ms --- ::1 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 1999ms rtt min/avg/max/mdev = 0.062/0.066/0.074/0.005 ms ###### ###### [5/8] Ping the IPv6 Local/Your Inner Tunnel Endpoint (2001:14b8:100:125::2) ### This confirms that your tunnel is configured ### If it doesn't reply then check your interface and routing tables PING 2001:14b8:100:125::2(2001:14b8:100:125::2) 56 data bytes 64 bytes from 2001:14b8:100:125::2: icmp_seq=1 ttl=64 time=0.077 ms 64 bytes from 2001:14b8:100:125::2: icmp_seq=2 ttl=64 time=0.063 ms 64 bytes from 2001:14b8:100:125::2: icmp_seq=3 ttl=64 time=0.064 ms --- 2001:14b8:100:125::2 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 1999ms rtt min/avg/max/mdev = 0.063/0.068/0.077/0.006 ms ###### ###### [6/8] Ping the IPv6 Remote/PoP Inner Tunnel Endpoint (2001:14b8:100:125::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:14b8:100:125::1(2001:14b8:100:125::1) 56 data bytes 64 bytes from 2001:14b8:100:125::1: icmp_seq=1 ttl=64 time=1.27 ms 64 bytes from 2001:14b8:100:125::1: icmp_seq=2 ttl=64 time=1.24 ms 64 bytes from 2001:14b8:100:125::1: icmp_seq=3 ttl=64 time=1.30 ms --- 2001:14b8:100:125::1 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2001ms rtt min/avg/max/mdev = 1.249/1.274/1.305/0.047 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:14b8:100:125::2, 30 hops max, 16 byte packets 1 * * * 2 van5r5.ip6.fv.fi (2001:14b8:0:3007::2) 1.788 ms 1.518 ms 1.455 ms 3 hki1r5.ip6.fv.fi (2001:14b8::4) 1.991 ms 2.061 ms 1.925 ms 4 hki2r5.ip6.fv.fi (2001:14b8::5) 2.094 ms 2.007 ms 2.022 ms 5 tuk2r2.ip6.fv.fi (2001:14b8::22) 17.998 ms 8.707 ms 15.064 ms 6 2001:7f8:d:fe::43 (2001:7f8:d:fe::43) 10.945 ms 9.133 ms 8.938 ms 7 so-0-0-0.stk30.ip6.tiscali.net (2001:668:0:2::121) 83.357 ms 9.13 ms 8.962 ms 8 so-4-1-0.ams22.ip6.tiscali.net (2001:668:0:2::1:351) 34.482 ms 34.508 ms 34.464 ms 9 so-6-0-0.ams11.ip6.tiscali.net (2001:668:0:2::1:271) 34.736 ms 34.548 ms 34.644 ms 10 xe-1-0-0.ams10.ip6.tiscali.net (2001:668:0:2::1:791) 34.468 ms 34.816 ms 34.594 ms 11 ge6-2-0.br0.ams3.nl.gbxs.net (2001:7f8:1::a500:9009:1) 31.203 ms 31.447 ms 31.2 ms 12 ams-ix2.ipv6.concepts.nl (2001:7f8:1::a501:2871:2) 35.107 ms 35.22 ms 35.082 ms 13 2001:838:0:13::1 (2001:838:0:13::1) 35.687 ms 35.367 ms 35.352 ms 14 2001:838:0:12::2 (2001:838:0:12::2) 37.871 ms 37.969 ms 38.044 ms 15 noc.sixxs.net (2001:838:1:1:210:dcff:fe20:7c7c) 38.1 ms 37.801 ms 37.796 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:14b8:100:125::2, 30 hops max, 16 byte packets 1 * * * 2 van5r5.ip6.fv.fi (2001:14b8:0:3007::2) 1.794 ms 1.487 ms 1.611 ms 3 hki1r5.ip6.fv.fi (2001:14b8::4) 2.065 ms 2.005 ms 2.105 ms 4 hki2r5.ip6.fv.fi (2001:14b8::5) 2.17 ms 1.994 ms 2.394 ms 5 tuk2r2.ip6.fv.fi (2001:14b8::22) 8.803 ms 8.876 ms 8.748 ms 6 2001:5012:100:5::1 (2001:5012:100:5::1) 8.608 ms 8.75 ms 8.537 ms 7 so-5-2-0-dcr2.amd.cw.net (2001:5000:0:7e::1) 30.76 ms 30.937 ms 30.807 ms 8 so-7-0-0-dcr1.ash.cw.net (2001:5000:0:f0::1) 122.854 ms 122.999 ms 122.95 ms 9 so-5-0-0-dcr1.was.cw.net (2001:5000:0:55::1) 120.275 ms 120.213 ms 120.327 ms 10 so-5-0-0-ecr1.was.cw.net (2001:5000:0:3e::1) 119.933 ms 119.935 ms 120.213 ms 11 so-0-0-0-ecr1.lax.cw.net (2001:5000:0:53::2) 187.916 ms 188.122 ms 187.757 ms 12 2001:504:a::a500:2500:1 (2001:504:a::a500:2500:1) 187.991 ms 188.11 ms 187.793 ms 13 hitachi1.otemachi.wide.ad.jp (2001:200:0:4401::3) 299.593 ms 297.624 ms 297.455 ms 14 2001:200:0:1802:20c:dbff:fe1f:7200 (2001:200:0:1802:20c:dbff:fe1f:7200) 293.899 ms 293.723 ms 293.318 ms 15 vlan44.cisco2.fujisawa.wide.ad.jp (2001:200:0:3::105) 300.439 ms 298.656 ms 299.695 ms 16 ve-4.nec2.yagami.wide.ad.jp (2001:200:0:1c04:230:13ff:feae:5b) 300.243 ms 296.636 ms 298.22 ms 17 lo0.alaxala1.k2.wide.ad.jp (2001:200:0:4800::7800:1) 296.981 ms 299.373 ms 296.972 ms 18 orange.kame.net (2001:200:0:8002:203:47ff:fea5:3085) 295.173 ms 295.09 ms 298.625 ms ###### ###### ACCU Quick Connectivity Test (done) If I use the traceroute tool on the sixxs website (https://noc.sixxs.net/tools/traceroute/) and traceroute from fihel01 (my POP) to 2001:14b8:100:125::2 (that would be me) it seems to work just fine. --- Hop Node Loss% Sent Last Avg Best Worst StDev ASN Organisation 1. 2001:14b8:100:125::2 0.0% 5 1.8 1.9 1.8 2.0 0.1 [.fi] Finland 16086 DNA Oy cl-294.hel-01.fi.sixxs.net. --- I am not certain what could be wrong, and I hope you can help point me in the right direction. Thank you!