SixXS::Sunset 2017-06-06

Ticket ID: SIXXS #8651146
Ticket Status: User

PoP: frmrs01 - Jaguar Network SARL (Marseille)

no connectivity on tunnel T111434
[fr] Shadow Hawkins on Sunday, 20 January 2013 09:34:49
Hello Since Friday the 18th our tunnel isn't working anymore (it worked well during the few weeks before). I am using a Ubuntu 12.04 and either with the following configuration in /etc/network/interface : auto sixxs iface sixxs inet6 v4tunnel address 2a01:240:fe00:21e::2 netmask 64 endpoint 78.153.240.201 ttl 64 up ip link set mtu 1280 dev sixxs up ip route add default via 2a01:240:fe00:21e::1 dev sixxs or by using aiccu, i have the same problem : the ipv6 network is unreeachable. For example I've got the following answer from a ping : ping6 -c 5 www.free.fr PING www.free.fr(www.free.fr) 56 data bytes From cl-543.mrs-01.fr.sixxs.net icmp_seq=1 Destination unreachable: Address unreachable From cl-543.mrs-01.fr.sixxs.net icmp_seq=2 Destination unreachable: Address unreachable From cl-543.mrs-01.fr.sixxs.net icmp_seq=3 Destination unreachable: Address unreachable From cl-543.mrs-01.fr.sixxs.net icmp_seq=4 Destination unreachable: Address unreachable From cl-543.mrs-01.fr.sixxs.net icmp_seq=5 Destination unreachable: Address unreachable ping6 -c 5 2a01:240:fe00:21e::1 PING 2a01:240:fe00:21e::1(2a01:240:fe00:21e::1) 56 data bytes From 2a01:240:fe00:21e::2 icmp_seq=1 Destination unreachable: Address unreachable From 2a01:240:fe00:21e::2 icmp_seq=2 Destination unreachable: Address unreachable From 2a01:240:fe00:21e::2 icmp_seq=3 Destination unreachable: Address unreachable From 2a01:240:fe00:21e::2 icmp_seq=4 Destination unreachable: Address unreachable From 2a01:240:fe00:21e::2 icmp_seq=5 Destination unreachable: Address unreachable Again it worked well during the last few weeks and the configuration on my server didn't change... Cordialy
State change: user Locked
[ch] Jeroen Massar SixXS Staff on Sunday, 20 January 2013 09:48:09
Message is Locked
The state of this ticket has been changed to user
no connectivity on tunnel T111434
[ch] Jeroen Massar SixXS Staff on Sunday, 20 January 2013 09:53:43
I am using a Ubuntu 12.04 and either with the following configuration in /etc/network/interface :
Please verify your RUNNING configuration. Please also read that big yellow box while posting and provide the details as requested on the contact page. Also note that you can check the live tunnel status which shows that the tunnel is configured properly. Thirdly note that Free provides IPv6 using 6rd which maybe interferes with your setup.
no connectivity on tunnel T111434
[fr] Shadow Hawkins on Friday, 01 February 2013 14:55:48
a few hours after my last message it suddenly worked again... And now again I lost IPv6 connectivity about two hours ago. Run some tests and found that I cannot ping my remote IPv6 tunnel endpoint. Here last lines of "aiccu test" output: ####### [3/8] Traceroute to the PoP (78.153.240.201) 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 78.153.240.201 (78.153.240.201), 30 hops max, 60 byte packets 1 192.168.0.254 (192.168.0.254) 1.087 ms 1.470 ms 1.883 ms 2 192.168.254.254 (192.168.254.254) 34.476 ms 35.177 ms 36.597 ms 3 bzn-6k-5-v201.routers.proxad.net (212.27.55.126) 36.905 ms * * 4 th2-crs16-1-be1200.intf.routers.proxad.net (212.27.50.193) 40.312 ms 41.193 ms 42.207 ms 5 th2-6k-3-po21.intf.routers.proxad.net (212.27.58.29) 42.604 ms * * 6 jaguar-pni.routers.proxad.net (212.27.40.122) 45.402 ms 33.616 ms 33.680 ms 7 sixxs.cust.jaguar-network.net (78.153.224.50) 47.610 ms 47.869 ms 54.539 ms 8 78.153.240.201 (78.153.240.201) 48.701 ms 50.649 ms 50.918 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.022 ms 64 bytes from ::1: icmp_seq=2 ttl=64 time=0.012 ms 64 bytes from ::1: icmp_seq=3 ttl=64 time=0.010 ms --- ::1 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 1999ms rtt min/avg/max/mdev = 0.010/0.014/0.022/0.006 ms ###### Did this work? [Y/n] y ###### [5/8] Ping the IPv6 Local/Your Inner Tunnel Endpoint (2a01:240:fe00:21e::2) ### This confirms that your tunnel is configured ### If it doesn't reply then check your interface and routing tables PING 2a01:240:fe00:21e::2(2a01:240:fe00:21e::2) 56 data bytes 64 bytes from 2a01:240:fe00:21e::2: icmp_seq=1 ttl=64 time=0.021 ms 64 bytes from 2a01:240:fe00:21e::2: icmp_seq=2 ttl=64 time=0.016 ms 64 bytes from 2a01:240:fe00:21e::2: icmp_seq=3 ttl=64 time=0.014 ms --- 2a01:240:fe00:21e::2 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 1999ms rtt min/avg/max/mdev = 0.014/0.017/0.021/0.003 ms ###### Did this work? [Y/n] y ###### [6/8] Ping the IPv6 Remote/PoP Inner Tunnel Endpoint (2a01:240:fe00:21e::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 2a01:240:fe00:21e::1(2a01:240:fe00:21e::1) 56 data bytes --- 2a01:240:fe00:21e::1 ping statistics --- 3 packets transmitted, 0 received, 100% packet loss, time 1999ms ###### Did this work? [Y/n] n Thanks PS free doesn't provide ipv6 to my type of subscription (unboudled)
no connectivity on tunnel T111434
[ch] Jeroen Massar SixXS Staff on Friday, 01 February 2013 15:10:36
Your pinging only shows that it does not work, not where it goes wrong. Please read the "Reporting Problems" section on the contact page and provide the details requested.

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

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