I have read and followed the "Reporting Problems" section on the Contact page. I am removing these five pre-filled lines to demonstrate that I really read it. I am providing the full details as requested on the mentioned Contact page. If I do not remove this, then please ignore this message as I didn't read it anyway. ------------------------------------------------------------------------------>8 I am having a similar problem, T29321, albeit I have other tunnels on the same PoP that are working fine. Any chance that your IPv4 connectivity is on comcast ?

bah, what I get for not reading boilerplate... Anyway, as I said, having similar issues... albeit now none of my tunnels (on this PoP) are working, after restarting aiccu. was working a bit ago... thinking maybe I should move to uschi03

I am having the same issue with both of my tunnels (T17875 and T17876). I am commenting on this ticket since it's likely that our problem has the same cause, but if it's determined that something else is causing my connectivity issues then I can open a separate ticket. From the machine running T17875: ####### ####### AICCU Quick Connectivity Test ####### ####### [1/8] Ping the IPv4 Local/Your Outer Endpoint (192.168.3.12) ### 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 192.168.3.12 (192.168.3.12) 56(84) bytes of data. 64 bytes from 192.168.3.12: icmp_req=1 ttl=64 time=0.071 ms 64 bytes from 192.168.3.12: icmp_req=2 ttl=64 time=0.037 ms 64 bytes from 192.168.3.12: icmp_req=3 ttl=64 time=0.034 ms --- 192.168.3.12 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 1998ms rtt min/avg/max/mdev = 0.034/0.047/0.071/0.017 ms ###### ####### [2/8] Ping the IPv4 Remote/PoP Outer Endpoint (216.14.98.22) ### 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 216.14.98.22 (216.14.98.22) 56(84) bytes of data. 64 bytes from 216.14.98.22: icmp_req=1 ttl=52 time=26.1 ms 64 bytes from 216.14.98.22: icmp_req=2 ttl=52 time=25.1 ms 64 bytes from 216.14.98.22: icmp_req=3 ttl=52 time=27.0 ms --- 216.14.98.22 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2002ms rtt min/avg/max/mdev = 25.165/26.120/27.010/0.777 ms ###### ####### [3/8] Traceroute to the PoP (216.14.98.22) 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 216.14.98.22 (216.14.98.22), 30 hops max, 60 byte packets 1 router.home.chrishowie.com (192.168.3.1) 0.733 ms 1.626 ms 2.024 ms 2 98.222.136.1 (98.222.136.1) 15.554 ms 15.943 ms 29.502 ms 3 te-8-3-ur02.anderson.in.indiana.comcast.net (68.85.177.137) 17.426 ms 17.721 ms 18.002 ms 4 te-8-1-ur01.richmond.in.indiana.comcast.net (68.85.177.6) 18.463 ms 18.885 ms 19.171 ms 5 po-100-ur02.richmond.in.indiana.comcast.net (68.85.176.254) 19.664 ms 19.958 ms 23.230 ms 6 be-30-ar01.elmhurst.il.chicago.comcast.net (68.85.176.221) 40.749 ms 40.181 ms 39.938 ms 7 pos-0-1-0-0-ar01.area4.il.chicago.comcast.net (68.87.230.237) 32.650 ms 25.086 ms 24.198 ms 8 pos-1-10-0-0-cr01.chicago.il.ibone.comcast.net (68.86.95.237) 28.576 ms 28.994 ms 29.278 ms 9 68.86.89.58 (68.86.89.58) 29.902 ms 30.803 ms 31.669 ms 10 your.org.ge2-5.br02.chc01.pccwbtn.net (63.218.5.38) 32.886 ms 33.177 ms 33.845 ms 11 sixxs.cx01.chi.bb.your.org (216.14.98.22) 34.699 ms 35.852 ms 35.159 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.056 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.052 ms --- ::1 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 1998ms rtt min/avg/max/mdev = 0.052/0.056/0.062/0.009 ms ###### ###### [5/8] Ping the IPv6 Local/Your Inner Tunnel Endpoint (2001:4978:f:1dc::2) ### This confirms that your tunnel is configured ### If it doesn't reply then check your interface and routing tables PING 2001:4978:f:1dc::2(2001:4978:f:1dc::2) 56 data bytes 64 bytes from 2001:4978:f:1dc::2: icmp_seq=1 ttl=64 time=0.062 ms 64 bytes from 2001:4978:f:1dc::2: icmp_seq=2 ttl=64 time=0.061 ms 64 bytes from 2001:4978:f:1dc::2: icmp_seq=3 ttl=64 time=0.060 ms --- 2001:4978:f:1dc::2 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 1998ms rtt min/avg/max/mdev = 0.060/0.061/0.062/0.000 ms ###### ###### [6/8] Ping the IPv6 Remote/PoP Inner Tunnel Endpoint (2001:4978:f:1dc::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 successful then this could be both ### a firewalling and a routing/interface problem PING 2001:4978:f:1dc::1(2001:4978:f:1dc::1) 56 data bytes --- 2001:4978:f:1dc::1 ping statistics --- 3 packets transmitted, 0 received, 100% packet loss, time 2016ms ###### ###### [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:4978:f:1dc::2, port 33434, from port 58770, 30 hops max, 60 byte packets 1 * * * 2 * * * 3 * * * 4 * * * 5 * * * 6 * * * 7 * * * 8 * * * 9 * * * 10 * * * 11 * * * 12 * * * 13 * * * 14 * * * 15 * * * 16 * * * 17 * * * 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 * * * 24 * * * 25 * * * 26 * * * 27 * * * 28 * * * 29 * * * 30 * * * ###### ###### [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:dff:fff1:216:3eff:feb1:44d7) from 2001:4978:f:1dc::2, port 33434, from port 58722, 30 hops max, 60 byte packets 1 * * * 2 * * * 3 * * * 4 * * * 5 * * * 6 * * * 7 * * * 8 * * * 9 * * * 10 * * * 11 * * * 12 * * * 13 * * * 14 * * * 15 * * * 16 * * * 17 * * * 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 * * * 24 * * * 25 * * * 26 * * * 27 * * * 28 * * * 29 * * * 30 * * * ###### ###### ACCU Quick Connectivity Test (done)

The state of this ticket has been changed to confirmed

There is major clock skew on the host, unfortunately not something that seems to be fixable, thus awaiting Your.org to resolve this, should not take too long. This thus affects all non-static tunnels, thus heartbeat + AYIYA.

The state of this ticket has been changed to resolved