Hi My tunnel has gone dead. Happened some time in the past 48 hours. I've made no changes on my end. I ran an aiccu test. Results are below, along with other details. Tunnel Information for T84002 The configuration for this tunnel looks like: Tunnel NameMy First Tunnel PoP Nameuschi03 PoP LocationChicago, Illinois, United States United States PoP IPv438.229.76.3 TIC Servertic.sixxs.net (default in AICCU) Your LocationToronto, Canada Canada Your IPv4Heartbeat, currently 72.138.45.224 IPv6 Prefix2604:8800:100:111::1/64 PoP IPv62604:8800:100:111::1 Your IPv62604:8800:100:111::2 Created2011-12-03 01:05:10 UTC Last Alive2013-06-22 15:31:05 UTC Last Dead2013-02-03 17:41:37 UTC Uptime0 days (based on latency check) Config StateHeartbeat (automatically enabled on the fly) PoP StatusLive Tunnel Status on the PoP Heartbeat This tunnel requires AICCU to function. ettin:/etc/shorewall6# aiccu test Tunnel Information for T84002: POP Id : uschi03 IPv6 Local : 2604:8800:100:111::2/64 IPv6 Remote : 2604:8800:100:111::1/64 Tunnel Type : 6in4-heartbeat Adminstate : enabled Userstate : enabled add tunnel sit0 failed: No buffer space available RTNETLINK answers: File exists RTNETLINK answers: File exists ####### ####### AICCU Quick Connectivity Test ####### ####### [1/8] Ping the IPv4 Local/Your Outer Endpoint (172.16.100.1) ### 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 172.16.100.1 (172.16.100.1) 56(84) bytes of data. 64 bytes from 172.16.100.1: icmp_req=1 ttl=64 time=0.067 ms 64 bytes from 172.16.100.1: icmp_req=2 ttl=64 time=0.061 ms 64 bytes from 172.16.100.1: icmp_req=3 ttl=64 time=0.062 ms --- 172.16.100.1 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 1999ms rtt min/avg/max/mdev = 0.061/0.063/0.067/0.007 ms ###### Did this work? [Y/n] Y ####### [2/8] Ping the IPv4 Remote/PoP Outer Endpoint (38.229.76.3) ### 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 38.229.76.3 (38.229.76.3) 56(84) bytes of data. 64 bytes from 38.229.76.3: icmp_req=1 ttl=55 time=34.4 ms 64 bytes from 38.229.76.3: icmp_req=2 ttl=55 time=31.4 ms 64 bytes from 38.229.76.3: icmp_req=3 ttl=55 time=34.5 ms --- 38.229.76.3 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2003ms rtt min/avg/max/mdev = 31.488/33.514/34.572/1.449 ms ###### Did this work? [Y/n] Y ####### [3/8] Traceroute to the PoP (38.229.76.3) 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 38.229.76.3 (38.229.76.3), 30 hops max, 60 byte packets 1 172.16.100.254 (172.16.100.254) 0.241 ms 0.228 ms 0.276 ms 2 7.18.24.1 (7.18.24.1) 8.787 ms 9.715 ms 9.782 ms 3 67.231.221.113 (67.231.221.113) 10.634 ms 10.661 ms 10.689 ms 4 69.63.253.78 (69.63.253.78) 13.723 ms 17.544 ms 18.491 ms 5 gw01.mtmc.phub.net.cable.rogers.com (66.185.81.137) 18.532 ms * 18.559 ms 6 * * * 7 ve5.fr4.yyz.llnw.net (69.28.171.142) 25.589 ms tge22-4.fr3.ord.llnw.net (69.28.189.137) 41.023 ms 41.032 ms 8 tge1-3.fr4.ord.llnw.net (69.28.172.69) 31.358 ms 32.288 ms ve8.fr3.ord4.llnw.net (68.142.80.130) 35.331 ms 9 ve6.fr3.ord.llnw.net (69.28.172.41) 33.241 ms 40.728 ms 39.705 ms 10 uschi03.sixxs.net (38.229.76.3) 36.234 ms ve8.fr3.ord4.llnw.net (68.142.80.130) 34.135 ms uschi03.sixxs.net (38.229.76.3) 36.265 ms ###### Did this work? [Y/n] Y ###### [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.070 ms 64 bytes from ::1: icmp_seq=2 ttl=64 time=0.067 ms 64 bytes from ::1: icmp_seq=3 ttl=64 time=0.056 ms --- ::1 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 1998ms rtt min/avg/max/mdev = 0.056/0.064/0.070/0.008 ms ###### Did this work? [Y/n] Y ###### [5/8] Ping the IPv6 Local/Your Inner Tunnel Endpoint (2604:8800:100:111::2) ### This confirms that your tunnel is configured ### If it doesn't reply then check your interface and routing tables PING 2604:8800:100:111::2(2604:8800:100:111::2) 56 data bytes 64 bytes from 2604:8800:100:111::2: icmp_seq=1 ttl=64 time=0.079 ms 64 bytes from 2604:8800:100:111::2: icmp_seq=2 ttl=64 time=0.080 ms 64 bytes from 2604:8800:100:111::2: icmp_seq=3 ttl=64 time=0.078 ms --- 2604:8800:100:111::2 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2000ms rtt min/avg/max/mdev = 0.078/0.079/0.080/0.000 ms ###### Did this work? [Y/n] Y ###### [6/8] Ping the IPv6 Remote/PoP Inner Tunnel Endpoint (2604:8800:100:111::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 2604:8800:100:111::1(2604:8800:100:111::1) 56 data bytes --- 2604:8800:100:111::1 ping statistics --- 3 packets transmitted, 0 received, 100% packet loss, time 2000ms ###### Did this work? [Y/n] n netstat -6 -rn Kernel IPv6 routing table Destination Next Hop Flag Met Ref Use If 2604:8800:100:111::/64 :: Un 256 0 1 sixxs fe80::/64 :: U 256 0 0 br0 fe80::/64 :: U 256 0 0 vnet0 fe80::/64 :: Un 256 0 0 sixxs ::/0 2604:8800:100:111::1 UG 1024 0 0 sixxs ::/0 :: !n -1 1 9745 lo ::1/128 :: Un 0 1 626 lo 2604:8800:100:111::2/128 :: Un 0 1 12 lo fe80::ac10:6401/128 :: Un 0 1 0 lo fe80::2e0:81ff:feb5:ee1e/128 :: Un 0 1 0 lo fe80::fc54:ff:fea1:da35/128 :: Un 0 1 0 lo ff00::/8 :: U 256 0 0 br0 ff00::/8 :: U 256 0 0 vnet0 ff00::/8 :: U 256 0 0 sixxs ::/0 :: !n -1 1 9745 lo ifconfig sixxs sixxs Link encap:IPv6-in-IPv4 inet6 addr: fe80::ac10:6401/64 Scope:Link inet6 addr: 2604:8800:100:111::2/64 Scope:Global UP POINTOPOINT RUNNING NOARP MTU:1280 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:6 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 B) TX bytes:616 (616.0 B) # ip6tables -L -n Chain INPUT (policy ACCEPT) target prot opt source destination Chain FORWARD (policy ACCEPT) target prot opt source destination Chain OUTPUT (policy ACCEPT) target prot opt source destination