Forum - tunnel suddently stopped working :: SixXS - IPv6 Deployment & Tunnel Broker

tunnel suddently stopped working

Shadow Hawkins on Wednesday, 15 January 2014 22:39:14

I do generally create the tunnels with the following: ip tunnel add sixxs mode sit local 192.168.2.2 remote 213.254.12.34 ttl 64 dev eno1 ip link set sixxs mtu 1472 ip link set sixxs up ip addr add 2001:1418:100:558::2/64 dev sixxs ip -6 route add default via 2001:1418:100:558::1 dev sixxs My provider is FastWeb and the external ip is 93.51.227.140 (natted from a router I don't own). The tunnel has worked for a few days, but suddently it stopped working, it's now impossible to ping the gateway 2001:1418:100:558::1, it miss all. everything however seem to be ok, the configuration has not changed since it was working, _and_I_can_reach_ 2001:1418:100:558::1 from other tunnels or from native ipv6. Other tunnels on trn-01.it.sixxs.net work well, with similar configuration. ping6 does work on internal ipv6 what I've tryed: - disable firewal - switching to AICCU for tunnel setup - reboots :-p - switching tunnel type to AYIYA (and back) when the tunnel is setup by AICCU the ping answer with an error, it's silent if direct ip commands are used: monfi ~ # ping6 2001:1418:100:558::1 PING 2001:1418:100:558::1(2001:1418:100:558::1) 56 data bytes From 2001:1418:100:558::2 icmp_seq=1 Destination unreachable: Address unreachable From 2001:1418:100:558::2 icmp_seq=2 Destination unreachable: Address unreachable From 2001:1418:100:558::2 icmp_seq=3 Destination unreachable: Address unreachable From 2001:1418:100:558::2 icmp_seq=4 Destination unreachable: Address unreachable monfi ~ # tracepath6 -n 2001:1418:100:558::1 1?: [LOCALHOST] 0.027ms pmtu 1480 1: 2001:1418:100:558::2 0.054ms !H 1: 2001:1418:100:558::2 0.021ms !H Resume: pmtu 1480 Please suggest something to try, I've no idea what to do try now

tunnel suddently stopped working

Shadow Hawkins on Wednesday, 15 January 2014 23:24:08

Francesco Riosa wrote:

aiccu test sock_getline() : "200 SixXS TIC Service on nlams01.sixxs.net ready (http://www.sixxs.net)" sock_printf() : "client TIC/draft-00 AICCU/2007.01.15-console-linux Linux/3.12.7-monfi" sock_getline() : "200 Client Identity accepted" sock_printf() : "get unixtime" sock_getline() : "200 1389828078" sock_printf() : "starttls" sock_getline() : "200 Go ahead, we are now talking securely" TLS Handshake completed succesfully sock_printf() : "username FR15-6BONE" sock_getline() : "200 FR15-6BONE choose your authentication challenge please" sock_printf() : "challenge md5" sock_getline() : "200 74935c1c9836d67197088aee018de0e5" sock_printf() : "authenticate md5 959a3d11aa4a28810509b0f78af1ef49" sock_getline() : "200 Successfully logged in using md5 as FR15-6BONE (Francesco Riosa)" sock_printf() : "tunnel show T134622" sock_getline() : "201 Showing tunnel information for T134622" sock_getline() : "TunnelId: T134622" sock_getline() : "Type: 6in4-static" sock_getline() : "IPv6 Endpoint: 2001:1418:100:558::2" sock_getline() : "IPv6 POP: 2001:1418:100:558::1" sock_getline() : "IPv6 PrefixLength: 64" sock_getline() : "Tunnel MTU: 1480" sock_getline() : "Tunnel Name: home tunnel" sock_getline() : "POP Id: ittrn01" sock_getline() : "IPv4 Endpoint: 93.51.227.140" sock_getline() : "IPv4 POP: 213.254.12.34" sock_getline() : "UserState: enabled" sock_getline() : "AdminState: enabled" sock_getline() : "202 Done" Succesfully retrieved tunnel information for T134622 sock_printf() : "QUIT We will be the only two people left in the world, Yes--Adam and Evil!" Tunnel Information for T134622: POP Id : ittrn01 IPv6 Local : 2001:1418:100:558::2/64 IPv6 Remote : 2001:1418:100:558::1/64 Tunnel Type : 6in4-static Adminstate : enabled Userstate : enabled ####### ####### AICCU Quick Connectivity Test ####### ####### [1/8] Ping the IPv4 Local/Your Outer Endpoint (93.51.227.140) ### 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 93.51.227.140 (93.51.227.140) 56(84) bytes of data. 64 bytes from 93.51.227.140: icmp_seq=1 ttl=61 time=27.4 ms 64 bytes from 93.51.227.140: icmp_seq=2 ttl=61 time=27.4 ms 64 bytes from 93.51.227.140: icmp_seq=3 ttl=61 time=27.9 ms --- 93.51.227.140 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2003ms rtt min/avg/max/mdev = 27.440/27.637/27.976/0.240 ms ###### Did this work? [Y/n] y ####### [2/8] Ping the IPv4 Remote/PoP Outer Endpoint (213.254.12.34) ### 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 213.254.12.34 (213.254.12.34) 56(84) bytes of data. 64 bytes from 213.254.12.34: icmp_seq=1 ttl=56 time=19.3 ms 64 bytes from 213.254.12.34: icmp_seq=2 ttl=56 time=19.0 ms 64 bytes from 213.254.12.34: icmp_seq=3 ttl=56 time=180 ms --- 213.254.12.34 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2002ms rtt min/avg/max/mdev = 19.016/73.006/180.637/76.106 ms ###### Did this work? [Y/n] y ####### [3/8] Traceroute to the PoP (213.254.12.34) 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 213.254.12.34 (213.254.12.34), 30 hops max, 60 byte packets 1 192.168.2.254 (192.168.2.254) 0.695 ms 0.930 ms 0.926 ms 2 10.1.101.165 (10.1.101.165) 16.293 ms 16.321 ms 16.316 ms 3 89.96.200.210 (89.96.200.210) 17.096 ms 89.96.200.118 (89.96.200.118) 17.346 ms 17.586 ms 4 89.96.200.117 (89.96.200.117) 17.322 ms 89.96.200.209 (89.96.200.209) 17.565 ms 17.838 ms 5 itgate-pub.topix.it (194.116.96.4) 20.959 ms 20.953 ms 21.294 ms 6 po1.Tango-Monster.edge.TRN.itgate.net (213.254.0.13) 21.601 ms 18.717 ms 18.713 ms 7 frejus.ITgate.net (213.254.12.34) 19.416 ms 19.399 ms 19.395 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.042 ms 64 bytes from ::1: icmp_seq=2 ttl=64 time=0.029 ms 64 bytes from ::1: icmp_seq=3 ttl=64 time=0.034 ms --- ::1 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 1999ms rtt min/avg/max/mdev = 0.029/0.035/0.042/0.005 ms ###### Did this work? [Y/n] y ###### [5/8] Ping the IPv6 Local/Your Inner Tunnel Endpoint (2001:1418:100:558::2) ### This confirms that your tunnel is configured ### If it doesn't reply then check your interface and routing tables PING 2001:1418:100:558::2(2001:1418:100:558::2) 56 data bytes 64 bytes from 2001:1418:100:558::2: icmp_seq=1 ttl=64 time=0.033 ms 64 bytes from 2001:1418:100:558::2: icmp_seq=2 ttl=64 time=0.032 ms 64 bytes from 2001:1418:100:558::2: icmp_seq=3 ttl=64 time=0.040 ms --- 2001:1418:100:558::2 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 1999ms rtt min/avg/max/mdev = 0.032/0.035/0.040/0.003 ms ###### Did this work? [Y/n] y ###### [6/8] Ping the IPv6 Remote/PoP Inner Tunnel Endpoint (2001:1418:100:558::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:1418:100:558::1(2001:1418:100:558::1) 56 data bytes From 2001:1418:100:558::2 icmp_seq=1 Destination unreachable: Address unreachable From 2001:1418:100:558::2 icmp_seq=2 Destination unreachable: Address unreachable From 2001:1418:100:558::2 icmp_seq=3 Destination unreachable: Address unreachable --- 2001:1418:100:558::1 ping statistics --- 3 packets transmitted, 0 received, +3 errors, 100% packet loss, time 1999ms ###### Did this work? [Y/n] n

tunnel suddently stopped working

Shadow Hawkins on Wednesday, 15 January 2014 23:43:52

Shrug* it does work again now

tunnel suddently stopped working

Jeroen Massar SixXS Staff

on Thursday, 16 January 2014 08:25:38

ip tunnel add sixxs mode sit local 192.168.2.2 remote 213.254.12.34 ttl 64 dev eno1

...

My provider is FastWeb and the external ip is 93.51.227.140 (natted from a router I don't own).

That combination is the problem. It is only with luck that this NAT You should be using AYIYA because of the NAT issue. (FastWeb was one of the scenarios that caused AYIYA to be designed btw)

From 2001:1418:100:558::2 icmp_seq=1 Destination unreachable: Address unreachable

That indicates a local issue, either routes are not set up properly, an interface is down, a firewall is causing packets to be rejected etc. Without all the details that are requested on the contact page, little one can say which one it is.

tunnel suddently stopped working

Shadow Hawkins on Friday, 31 January 2014 14:14:34

Jeroen Massar wrote:

> ip tunnel add sixxs mode sit local 192.168.2.2 remote 213.254.12.34 ttl 64 dev eno1

...

My provider is FastWeb and the external ip is 93.51.227.140 (natted from a router I don't own).

That combination is the problem. It is only with luck that this NAT You should be using AYIYA because of the NAT issue. (FastWeb was one of the scenarios that caused AYIYA to be designed btw)

switched to AYIYA, a bit sorry for the lower MTU but better than nothing

tunnel suddently stopped working

Shadow Hawkins on Friday, 31 January 2014 14:15:03

thanks for the answer

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