SixXS::Sunset 2017-06-06

Ticket ID: SIXXS #1234276
Ticket Status: User

PoP: ittrn01 - ITgate (Torino)

Tunnel down for a long time
[it] Shadow Hawkins on Monday, 19 October 2009 16:54:27
Dear SixXS staff, It's a long time that my tunnel T22720 is down. about a month ago, the tunnel suddently stopped working, and it never went up again. I'm sure I don't have firewalling problems, for two reasons: * no changes to rulesets were made before the tunnel stopped working * if I configure the aiccu client to use T21580 on the machine that normally handles T22720, all works perfectly, but T22720 still don't work on the machine that handles T21580. Since T22720 was ayiya and T21580 is heartbeat, I decided to spend 15 credits to move also T22720 to heartbeat, in the hope it started working again, but with no luck. Below the output of "aiccu autotest" Any hints? Thank you. ****************************************** # sixxs-aiccu autotest /usr/local/etc/aiccu.conf ####### ####### AICCU Quick Connectivity Test ####### ####### [1/8] Ping the IPv4 Local/Your Outer Endpoint (172.16.0.1) PING 172.16.0.1 (172.16.0.1): 56 data bytes 64 bytes from 172.16.0.1: icmp_seq=0 ttl=64 time=0.103 ms 64 bytes from 172.16.0.1: icmp_seq=1 ttl=64 time=0.047 ms 64 bytes from 172.16.0.1: icmp_seq=2 ttl=64 time=0.038 ms --- 172.16.0.1 ping statistics --- 3 packets transmitted, 3 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 0.038/0.063/0.103/0.029 ms ###### ####### [2/8] Ping the IPv4 Remote/PoP Outer Endpoint (213.254.12.34) PING 213.254.12.34 (213.254.12.34): 56 data bytes 64 bytes from 213.254.12.34: icmp_seq=0 ttl=56 time=41.756 ms 64 bytes from 213.254.12.34: icmp_seq=1 ttl=56 time=23.835 ms 64 bytes from 213.254.12.34: icmp_seq=2 ttl=56 time=23.218 ms --- 213.254.12.34 ping statistics --- 3 packets transmitted, 3 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 23.218/29.603/41.756/8.597 ms ###### ####### [3/8] Traceroute to the PoP (213.254.12.34) over IPv4 traceroute to 213.254.12.34 (213.254.12.34), 64 hops max, 52 byte packets 1 rfc-1918 (172.16.0.30) 1.527 ms 0.609 ms 0.860 ms 2 xdsl-gw.net.ngi.it (81.174.0.1) 25.207 ms 17.453 ms 17.710 ms 3 core1-v6.net.ngi.it (81.174.0.188) 32.314 ms 18.453 ms 18.940 ms 4 212.239.110.45 (212.239.110.45) 19.008 ms 18.956 ms 19.452 ms 5 itgate.mix-it.net (217.29.66.65) 21.720 ms 19.908 ms 19.979 ms 6 if-0-3.scooby-monster.core.TRN.itgate.net (213.254.31.241) 127.166 ms 185.521 ms 213.555 ms 7 if-0-0.charleston.CBQ.TRN.itgate.net (213.254.0.13) 23.453 ms 21.875 ms 23.356 ms 8 frejus.ITgate.net (213.254.12.34) 22.838 ms 22.439 ms 23.426 ms ###### ###### [4/8] Checking if we can ping IPv6 localhost (::1) PING6(56=40+8+8 bytes) ::1 --> ::1 16 bytes from ::1: Echo Request 16 bytes from ::1, icmp_seq=0 hlim=64 dst=::1%3 time=0.301 ms 16 bytes from ::1: Echo Request 16 bytes from ::1, icmp_seq=1 hlim=64 dst=::1%3 time=0.153 ms 16 bytes from ::1: Echo Request 16 bytes from ::1, icmp_seq=2 hlim=64 dst=::1%3 time=0.140 ms --- ::1 ping6 statistics --- 3 packets transmitted, 3 packets received, 0.0% packet loss round-trip min/avg/max/std-dev = 0.140/0.198/0.301/0.073 ms ###### ###### [5/8] Ping the IPv6 Local/Your Inner Tunnel Endpoint (2001:1418:100:2fb::2) PING6(56=40+8+8 bytes) 2001:1418:100:2fb::2 --> 2001:1418:100:2fb::2 16 bytes from 2001:1418:100:2fb::2: Echo Request 16 bytes from 2001:1418:100:2fb::2, icmp_seq=0 hlim=64 dst=2001:1418:100:2fb::2%4 time=0.254 ms 16 bytes from 2001:1418:100:2fb::2: Echo Request 16 bytes from 2001:1418:100:2fb::2, icmp_seq=1 hlim=64 dst=2001:1418:100:2fb::2%4 time=0.127 ms 16 bytes from 2001:1418:100:2fb::2: Echo Request 16 bytes from 2001:1418:100:2fb::2, icmp_seq=2 hlim=64 dst=2001:1418:100:2fb::2%4 time=0.119 ms --- 2001:1418:100:2fb::2 ping6 statistics --- 3 packets transmitted, 3 packets received, 0.0% packet loss round-trip min/avg/max/std-dev = 0.119/0.167/0.254/0.062 ms ###### ###### [6/8] Ping the IPv6 Remote/PoP Inner Tunnel Endpoint (2001:1418:100:2fb::1) PING6(56=40+8+8 bytes) 2001:1418:100:2fb::2 --> 2001:1418:100:2fb::1 --- 2001:1418:100:2fb::1 ping6 statistics --- 3 packets transmitted, 0 packets received, 100.0% packet loss ###### ###### [7/8] Traceroute6 to the central SixXS machine (noc.sixxs.net) traceroute6 to noc.sixxs.net (2001:838:1:1:210:dcff:fe20:7c7c) from 2001:1418:100:2fb::2, 64 hops max, 12 byte packets 1 * * * 2 * * * ^C ###### ###### [8/8] Traceroute6 to (www.kame.net) traceroute6 to www.kame.net (2001:200:0:8002:203:47ff:fea5:3085) from 2001:1418:100:2fb::2, 64 hops max, 12 byte packets 1 * * * 2 * * * ^C
State change: user Locked
[ch] Jeroen Massar SixXS Staff on Monday, 19 October 2009 16:56:04
Message is Locked
The state of this ticket has been changed to user
Tunnel down for a long time
[ch] Jeroen Massar SixXS Staff on Monday, 19 October 2009 16:57:07
Please use the forums for your issues with setups. Also note that you are using RFC1918 addresses, as such if you use heartbeat you will need to configure your NAT stuff properly.

Please note Posting is only allowed when you are logged in.

Static Sunset Edition of SixXS
©2001-2017 SixXS - IPv6 Deployment & Tunnel Broker