Tickets - Tunnel T13301 stopped working since about 20h :: SixXS

Ticket ID: SIXXS #1784337
Ticket Status: Resolved

PoP: deham01 - Easynet (Hamburg)

Tunnel T13301 stopped working since about 20h

Shadow Hawkins on Thursday, 27 May 2010 21:04:17

I have tested another tunnel from my account on the same router (alix/debian) and this one will work fine. The Tunnel T13301 is down. I cant ping the ipv6 pop side ip, the ipv6 ip is pingable from both sides, from my router and an another external router/server. Is there a problem with some tunnels on deham01? Of course my other Tunnel is there too, and this one T18776 works fine. For testing i removed all ipv6 local adresses/routes on the router...and after successful testing the T18776 i changed to my primary T13301 and this one "hangs". cya

State change: user Locked

Jeroen Massar SixXS Staff

on Friday, 28 May 2010 07:45:18

The state of this ticket has been changed to user

Tunnel T13301 stopped working since about 20h

Jeroen Massar SixXS Staff

on Friday, 28 May 2010 07:45:34

Please provide more details as clearly requested.

Tunnel T13301 stopped working since about 20h

Shadow Hawkins on Friday, 28 May 2010 09:29:03

Ping6 from Router to pop IPv6 IP router:# ping6 2001:6f8:900:a1d::1 PING 2001:6f8:900:a1d::1(2001:6f8:900:a1d::1) 56 data bytes ^C --- 2001:6f8:900:a1d::1 ping statistics --- 5 packets transmitted, 0 received, 100% packet loss, time 4014ms ######### Ping6 from Client in the Subnet to the router ipv6 tunnel ip macbook:# ping6 2001:6f8:900:a1d::2 PING6(56=40+8+8 bytes) 2001:6f8:9a6:23:226:b0ff:fee2:c016 --> 2001:6f8:900:a1d::2 16 bytes from 2001:6f8:900:a1d::2, icmp_seq=0 hlim=64 time=1.339 ms 16 bytes from 2001:6f8:900:a1d::2, icmp_seq=1 hlim=64 time=0.255 ms 16 bytes from 2001:6f8:900:a1d::2, icmp_seq=2 hlim=64 time=0.384 ms 16 bytes from 2001:6f8:900:a1d::2, icmp_seq=3 hlim=64 time=0.348 ms ^C --- 2001:6f8:900:a1d::2 ping6 statistics --- 4 packets transmitted, 4 packets received, 0.0% packet loss round-trip min/avg/max/std-dev = 0.255/0.581/1.339/0.440 ms ########## IPv6 Routing table on the router after aiccu is started (sixxs is the tunnel interface) router:# route -n -6 | grep sixxs 2001:6f8:900:a1d::/64 :: U 256 0 1 sixxs fe80::/64 :: U 256 0 0 sixxs ::/0 2001:6f8:900:a1d::1 UG 1024 0 6110 sixxs ff00::/8 :: U 256 0 0 sixxs ########## Local Routing works fine. The tunnel stopped working without any doing by myself.

State change: resolved Locked

Jeroen Massar SixXS Staff

on Friday, 28 May 2010 14:12:55

The state of this ticket has been changed to resolved

Tunnel T13301 stopped working since about 20h

Shadow Hawkins on Friday, 28 May 2010 14:20:39

Is it possible to get an information what happened? Because since about 14:05 it works again and running complete. Thx.

Tunnel T13301 stopped working since about 20h

Shadow Hawkins on Wednesday, 20 October 2010 16:12:58

Sorry, but it is again the same problem...every tunnel is working fine, but only this tunnel to deham01 isnt working...the v6 ip of the "gateway" isnt pingable...

Tunnel T13301 stopped working since about 20h

Shadow Hawkins on Wednesday, 20 October 2010 16:22:35

EQ6:# ping6 2001:6f8:900:a1d::1 PING 2001:6f8:900:a1d::1(2001:6f8:900:a1d::1) 56 data bytes From 2001:6f8:800:1003::2 icmp_seq=1 Destination unreachable: No route

no connect to my pop

Shadow Hawkins on Thursday, 21 October 2010 14:59:17

Sorry, but it is again the same problem...every tunnel is working fine, but only this tunnel to deham01 isnt working...the v6 ip of the "gateway" isnt pingable... EQ6:# ping6 2001:6f8:900:a1d::1 PING 2001:6f8:900:a1d::1(2001:6f8:900:a1d::1) 56 data bytes From 2001:6f8:800:1003::2 icmp_seq=1 Destination unreachable: No route And on the aiccu site the 2001:6f8:900:a1d::2 is no ping to 2001:6f8:900:a1d::1 possible... It is the same error like the last time, the tunnel stopped working.

no connect to my pop

Shadow Hawkins on Thursday, 21 October 2010 15:53:13

####### ####### AICCU Quick Connectivity Test ####### ####### [1/8] Ping the IPv4 Local/Your Outer Endpoint (89.245.130.104) ### 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 89.245.130.104 (89.245.130.104) 56(84) bytes of data. 64 bytes from 89.245.130.104: icmp_seq=1 ttl=64 time=0.121 ms 64 bytes from 89.245.130.104: icmp_seq=2 ttl=64 time=0.107 ms 64 bytes from 89.245.130.104: icmp_seq=3 ttl=64 time=0.083 ms --- 89.245.130.104 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 1998ms rtt min/avg/max/mdev = 0.083/0.103/0.121/0.019 ms ###### Did this work? [Y/n] y ####### [2/8] Ping the IPv4 Remote/PoP Outer Endpoint (212.224.0.188) ### 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.224.0.188 (212.224.0.188) 56(84) bytes of data. 64 bytes from 212.224.0.188: icmp_seq=1 ttl=56 time=19.6 ms 64 bytes from 212.224.0.188: icmp_seq=2 ttl=56 time=20.1 ms 64 bytes from 212.224.0.188: icmp_seq=3 ttl=56 time=20.4 ms --- 212.224.0.188 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2008ms rtt min/avg/max/mdev = 19.676/20.090/20.452/0.358 ms ###### Did this work? [Y/n] y ####### [3/8] Traceroute to the PoP (212.224.0.188) 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.224.0.188 (212.224.0.188), 30 hops max, 40 byte packets 1 dor002ibr010-xdsl.versatel.de (62.214.64.191) 27.184 ms 27.997 ms 29.629 ms 2 ge-2-3-551.dor002isp006.versatel.de (62.214.108.209) 8.621 ms 10.228 ms 11.147 ms 3 10g-8-1.dor002isp006.versatel.de (62.214.110.125) 12.285 ms 10g-9-1.dor002isp006.versatel.de (62.214.110.133) 13.429 ms 14.574 ms 4 10g-8-1.fra020isp006.versatel.de (62.214.110.146) 20.901 ms 10g-7-1.fra020isp006.versatel.de (62.214.110.130) 21.769 ms 10g-8-1.fra020isp006.versatel.de (62.214.110.146) 22.679 ms 5 ge3-16.er11.ixfra.de.easynet.net (80.81.193.14) 25.066 ms 26.020 ms 27.573 ms 6 ge1-11.br2.isham.de.easynet.net (87.86.69.161) 44.253 ms te0-1-0.gr11.isham.de.easynet.net (87.86.77.80) 26.860 ms 26.693 ms 7 ge7-1.cr20.isham.de.easynet.net (212.224.4.89) 30.850 ms 30.323 ms 30.123 ms 8 ge9-15.cr20.isham.de.easynet.net (212.224.4.93) 27.219 ms deham01.sixxs.net (212.224.0.188) 25.460 ms 25.960 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.078 ms 64 bytes from ::1: icmp_seq=2 ttl=64 time=0.084 ms 64 bytes from ::1: icmp_seq=3 ttl=64 time=0.083 ms --- ::1 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 1999ms rtt min/avg/max/mdev = 0.078/0.081/0.084/0.010 ms ###### Did this work? [Y/n] y ###### [5/8] Ping the IPv6 Local/Your Inner Tunnel Endpoint (2001:6f8:900:a1d::2) ### This confirms that your tunnel is configured ### If it doesn't reply then check your interface and routing tables PING 2001:6f8:900:a1d::2(2001:6f8:900:a1d::2) 56 data bytes 64 bytes from 2001:6f8:900:a1d::2: icmp_seq=1 ttl=64 time=0.088 ms 64 bytes from 2001:6f8:900:a1d::2: icmp_seq=2 ttl=64 time=0.086 ms 64 bytes from 2001:6f8:900:a1d::2: icmp_seq=3 ttl=64 time=0.093 ms --- 2001:6f8:900:a1d::2 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 1998ms rtt min/avg/max/mdev = 0.086/0.089/0.093/0.003 ms ###### Did this work? [Y/n] y ###### [6/8] Ping the IPv6 Remote/PoP Inner Tunnel Endpoint (2001:6f8:900:a1d::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:6f8:900:a1d::1(2001:6f8:900:a1d::1) 56 data bytes --- 2001:6f8:900:a1d::1 ping statistics --- 3 packets transmitted, 0 received, 100% packet loss, time 2013ms ###### Did this work? [Y/n] n router:/# ip6tables -S -P INPUT ACCEPT -P FORWARD ACCEPT -P OUTPUT ACCEPT router:/# route -6 -n 2001:6f8:900:a1d::/64 :: U 256 0 1 sixxs 2001:6f8:9a6:23::/64 :: U 256 0 0 eth0 ::/0 2001:6f8:900:a1d::1 UG 1024 0 0 sixxs Is the v6 ip 2001:6f8:900:a1d::1 only available if my aiccu client is started? Then i should be able to ping the 2001:6f8:900:a1d::1 from another nativ v6 ip host, nor?

no connect to my pop

Shadow Hawkins on Sunday, 15 January 2012 18:33:43

The Tunnel isnt working again...it stopped on December 31th 2011.

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