SixXS::Sunset 2017-06-06

Ticket ID: SIXXS #3688869
Ticket Status: Resolved

PoP: chzrh02 - Init7 AG (Zurich)

Tunnel T57145 not working (seems to be a pop problem)
[ch] Shadow Hawkins on Wednesday, 16 February 2011 13:06:14
Hi, after chzrh02 came up again today after about 9 hours of downtime the first 5 tests of the AICCU autotest work but no IPv6 destinations can be reached including the PoP IPv6 endpoint. tcpdump shows icmpv6 requests going through the tunnel but no replies coming back. Regards Andreas root@koala:~# ifconfig sixxs sixxs Link encap:IPv6-in-IPv4 inet6 addr: fe80::544a:5a67/128 Scope:Link inet6 addr: 2001:1620:f00:f1::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:9 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 B) TX bytes:936 (936.0 B) root@koala:~# ip -6 route list default via 2001:1620:f00:f1::1 dev sixxs metric 1024 mtu 1280 advmss 1220 hoplimit 4294967295 root@koala:~# iptables -v -n -L | grep 213.144.148.74 0 0 ACCEPT 41 -- eth0 * 213.144.148.74 0.0.0.0/0 1511 185K ACCEPT 41 -- * eth0 0.0.0.0/0 213.144.148.74 ####### ####### AICCU Quick Connectivity Test ####### ####### [1/8] Ping the IPv4 Local/Your Outer Endpoint (84.74.90.103) ### 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 84.74.90.103 (84.74.90.103) 56(84) bytes of data. 64 bytes from 84.74.90.103: icmp_req=1 ttl=64 time=0.033 ms 64 bytes from 84.74.90.103: icmp_req=2 ttl=64 time=0.018 ms 64 bytes from 84.74.90.103: icmp_req=3 ttl=64 time=0.017 ms --- 84.74.90.103 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 1998ms rtt min/avg/max/mdev = 0.017/0.022/0.033/0.009 ms ###### ####### [2/8] Ping the IPv4 Remote/PoP Outer Endpoint (213.144.148.74) ### 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.144.148.74 (213.144.148.74) 56(84) bytes of data. 64 bytes from 213.144.148.74: icmp_req=1 ttl=54 time=19.5 ms 64 bytes from 213.144.148.74: icmp_req=2 ttl=54 time=24.5 ms 64 bytes from 213.144.148.74: icmp_req=3 ttl=54 time=19.5 ms --- 213.144.148.74 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2003ms rtt min/avg/max/mdev = 19.564/21.238/24.554/2.347 ms ###### ####### [3/8] Traceroute to the PoP (213.144.148.74) 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.144.148.74 (213.144.148.74), 30 hops max, 60 byte packets 1 * * * 2 217-168-57-49.static.cablecom.ch (217.168.57.49) 27.650 ms 27.650 ms 27.633 ms 3 172.31.208.77 (172.31.208.77) 28.767 ms 28.763 ms 28.751 ms 4 ch-zrh01a-si1.aorta.net (213.46.171.18) 32.764 ms 32.791 ms 32.753 ms 5 r1gva1.core.init7.net (77.109.134.249) 32.924 ms 32.723 ms 32.898 ms 6 r1zug1.core.init7.net (77.109.128.217) 37.598 ms 19.119 ms 19.117 ms 7 r1glb1.core.init7.net (77.109.140.205) 22.320 ms 21.182 ms 21.533 ms 8 r1oer1.core.init7.net (77.109.128.177) 18.678 ms 18.328 ms 18.590 ms 9 r1zur1.core.init7.net (77.109.128.253) 18.585 ms 18.763 ms 18.541 ms 10 r1zlz1.core.init7.net (77.109.128.210) 22.194 ms 21.243 ms 20.749 ms 11 213.144.148.74 (213.144.148.74) 20.703 ms 20.004 ms 21.724 ms ###### ###### [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.037 ms 64 bytes from ::1: icmp_seq=2 ttl=64 time=0.028 ms 64 bytes from ::1: icmp_seq=3 ttl=64 time=0.026 ms --- ::1 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 1998ms rtt min/avg/max/mdev = 0.026/0.030/0.037/0.006 ms ###### ###### [5/8] Ping the IPv6 Local/Your Inner Tunnel Endpoint (2001:1620:f00:f1::2) ### This confirms that your tunnel is configured ### If it doesn't reply then check your interface and routing tables PING 2001:1620:f00:f1::2(2001:1620:f00:f1::2) 56 data bytes 64 bytes from 2001:1620:f00:f1::2: icmp_seq=1 ttl=64 time=0.024 ms 64 bytes from 2001:1620:f00:f1::2: icmp_seq=2 ttl=64 time=0.029 ms 64 bytes from 2001:1620:f00:f1::2: icmp_seq=3 ttl=64 time=0.032 ms --- 2001:1620:f00:f1::2 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2004ms rtt min/avg/max/mdev = 0.024/0.028/0.032/0.005 ms ###### ###### [6/8] Ping the IPv6 Remote/PoP Inner Tunnel Endpoint (2001:1620:f00:f1::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 2001:1620:f00:f1::1(2001:1620:f00:f1::1) 56 data bytes From 2001:1620:f00:f1::2 icmp_seq=1 Destination unreachable: Address unreachable From 2001:1620:f00:f1::2 icmp_seq=2 Destination unreachable: Address unreachable From 2001:1620:f00:f1::2 icmp_seq=3 Destination unreachable: Address unreachable --- 2001:1620:f00:f1::1 ping statistics --- 3 packets transmitted, 0 received, +3 errors, 100% packet loss, time 2008ms ###### ###### [7/8] Traceroute6 to the central SixXS machine (noc.sixxs.net) ### This confirms that you can reach the central machine of SixXS ### If that one is reachable you should be able to reach most IPv6 destinations ### Also check http://www.sixxs.net/ipv6calc/ which should show an IPv6 connection ### If your browser supports IPv6 and uses it of course. traceroute to noc.sixxs.net (2001:838:1:1:210:dcff:fe20:7c7c) from 2001:1620:f00:f1::2, 30 hops max, 24 byte packets 1 cl-242.zrh-02.ch.sixxs.net (2001:1620:f00:f1::2) 0.057 ms !H 0.044 ms !H * ###### ###### [8/8] Traceroute6 to (www.kame.net) ### This confirms that you can reach a Japanese IPv6 destination ### If that one is reachable you should be able to reach most IPv6 destinations ### You should also check http://www.kame.net which should display ### a animated kame (turtle), of course only when your browser supports and uses IPv6 traceroute to orange.kame.net (2001:200:dff:fff1:216:3eff:feb1:44d7) from 2001:1620:f00:f1::2, 30 hops max, 24 byte packets 1 cl-242.zrh-02.ch.sixxs.net (2001:1620:f00:f1::2) 0.061 ms !H 0.085 ms !H * ######
Tunnel T57145 not working (seems to be a pop problem)
[ch] Shadow Hawkins on Wednesday, 16 February 2011 13:26:17
I have the same problem with tunnel T56245 ###### [6/8] Ping the IPv6 Remote/PoP Inner Tunnel Endpoint (2001:1620:f00:ee::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:1620:f00:ee::1(2001:1620:f00:ee::1) 56 data bytes From 2001:1620:f00:ee::2 icmp_seq=2 Destination unreachable: Address unreachable From 2001:1620:f00:ee::2 icmp_seq=3 Destination unreachable: Address unreachable --- 2001:1620:f00:ee::1 ping statistics --- 3 packets transmitted, 0 received, +2 errors, 100% packet loss, time 2013ms ######
Tunnel T57145 not working (seems to be a pop problem)
[ch] Shadow Hawkins on Saturday, 19 February 2011 23:35:25
I can't ping the PoP IPv6 IP from my Tunnel again. Same problem. ###### [6/8] Ping the IPv6 Remote/PoP Inner Tunnel Endpoint (2001:1620:f00:ee::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:1620:f00:ee::1(2001:1620:f00:ee::1) 56 data bytes From 2001:1620:f00:ee::2 icmp_seq=1 Destination unreachable: Address unreachable From 2001:1620:f00:ee::2 icmp_seq=2 Destination unreachable: Address unreachable From 2001:1620:f00:ee::2 icmp_seq=3 Destination unreachable: Address unreachable --- 2001:1620:f00:ee::1 ping statistics --- 3 packets transmitted, 0 received, +3 errors, 100% packet loss, time 2014ms
Tunnel T57145 not working (seems to be a pop problem)
[ch] Jeroen Massar SixXS Staff on Sunday, 20 February 2011 00:03:31
From 2001:1620:f00:ee::2 icmp_seq=1 Destination unreachable: Address unreachable
That is your end of the tunnel telling that it does not know where presumably 2001:1620:f00:ee::1 is.
Tunnel T57145 not working (seems to be a pop problem)
[ch] Shadow Hawkins on Sunday, 20 February 2011 00:24:59
I have now rebooted the whole computer and it still doesn't work. last time I had to do nothing after it was resolved.
Tunnel T57145 not working (seems to be a pop problem)
[ch] Shadow Hawkins on Sunday, 20 February 2011 09:11:59
Hello, I have the same problem as Benjamin. The tunnel stopped working on Saturday around midnight and is still not up (2011-02-20 09:09). The first 5 tests of autotest are ok but the last three fail: ###### [6/8] Ping the IPv6 Remote/PoP Inner Tunnel Endpoint (2001:1620:f00:f1::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 2001:1620:f00:f1::1(2001:1620:f00:f1::1) 56 data bytes From 2001:1620:f00:f1::2 icmp_seq=1 Destination unreachable: Address unreachable From 2001:1620:f00:f1::2 icmp_seq=2 Destination unreachable: Address unreachable From 2001:1620:f00:f1::2 icmp_seq=3 Destination unreachable: Address unreachable --- 2001:1620:f00:f1::1 ping statistics --- 3 packets transmitted, 0 received, +3 errors, 100% packet loss, time 1999ms ###### ###### [7/8] Traceroute6 to the central SixXS machine (noc.sixxs.net) ### This confirms that you can reach the central machine of SixXS ### If that one is reachable you should be able to reach most IPv6 destinations ### Also check http://www.sixxs.net/ipv6calc/ which should show an IPv6 connection ### If your browser supports IPv6 and uses it of course. traceroute to noc.sixxs.net (2001:838:1:1:210:dcff:fe20:7c7c) from 2001:1620:f00:f1::2, 30 hops max, 24 byte packets 1 cl-242.zrh-02.ch.sixxs.net (2001:1620:f00:f1::2) 0.062 ms !H 0.069 ms !H 0.035 ms !H ###### ###### [8/8] Traceroute6 to (www.kame.net) ### This confirms that you can reach a Japanese IPv6 destination ### If that one is reachable you should be able to reach most IPv6 destinations ### You should also check http://www.kame.net which should display ### a animated kame (turtle), of course only when your browser supports and uses IPv6 traceroute to orange.kame.net (2001:200:dff:fff1:216:3eff:feb1:44d7) from 2001:1620:f00:f1::2, 30 hops max, 24 byte packets 1 cl-242.zrh-02.ch.sixxs.net (2001:1620:f00:f1::2) 0.069 ms !H 0.052 ms !H * ###### ###### ACCU Quick Connectivity Test (done) I restarted aiccu but I still cannot reach neither the 2001:1620:f00:f1::1 endpoint nor ipv6.google.com. Regards Andreas
Tunnel T57145 not working (seems to be a pop problem)
[ch] Shadow Hawkins on Sunday, 20 February 2011 10:47:19
Some additional information from tcpdump: 10:40:14.323341 IP 84.74.90.103 > 213.144.148.74: IP6 2001:1620:f00:f1::2 > 2001:1620:f00:f1::1: ICMP6, echo request, seq 1, length 64 10:40:14.344441 IP 213.144.148.74 > 84.74.90.103: ICMP 213.144.148.74 protocol 41 unreachable, length 132 10:40:15.330038 IP 84.74.90.103 > 213.144.148.74: IP6 2001:1620:f00:f1::2 > 2001:1620:f00:f1::1: ICMP6, echo request, seq 2, length 64 10:40:15.353282 IP 213.144.148.74 > 84.74.90.103: ICMP 213.144.148.74 protocol 41 unreachable, length 132 10:44:25.602410 IP 84.74.90.103 > 213.144.148.74: IP6 2001:1620:f00:f1::2.3418 > 2001:838:2:1:2a0:24ff:feab:3b53.443: Flags [S], seq 123284688, win 4880, options [mss 1220,sackOK,TS val 104357 ecr 0,nop,wscale 7], length 0 10:44:25.602645 IP 84.74.90.103 > 213.144.148.74: IP6 2001:1620:f00:f1::2.26767 > 2001:960:800::2.443: Flags [S], seq 3140989568, win 4880, options [mss 1220,sackOK,TS val 104357 ecr 0,nop,wscale 7], length 0 10:44:25.622597 IP 213.144.148.74 > 84.74.90.103: ICMP 213.144.148.74 protocol 41 unreachable, length 108 10:44:25.622623 IP 213.144.148.74 > 84.74.90.103: ICMP 213.144.148.74 protocol 41 unreachable, length 108 Andreas
Tunnel T57145 not working (seems to be a pop problem)
[ch] Shadow Hawkins on Sunday, 20 February 2011 14:06:02
IPv6 connectivity is up again. After 15 hours of downtime I'm wondering about the reliability my PoP is offering me.
Tunnel T57145 not working (seems to be a pop problem)
[ch] Jeroen Massar SixXS Staff on Sunday, 20 February 2011 14:08:33
If you require an SLA, please contact info@sixxs.net with the requirements and we will pass these on to various ISPs who can make you a great offer which will meet your requirements. We wish you a happy weekend from a free service, enjoy your Sunday.
State change: resolved Locked
[ch] Jeroen Massar SixXS Staff on Wednesday, 16 February 2011 13:34:59
Message is Locked
The state of this ticket has been changed to resolved
Tunnel T57145 not working (seems to be a pop problem)
[ch] Shadow Hawkins on Monday, 10 October 2011 20:56:43
After the downtime of the POP over the weekend (the third weekend within a month) The tunnel to the IPv4 POP endpoint 213.144.148.74 is up again but I cannot ping the IPv6 endpoint 2001:1620:f00:f1::1 nor reach any other IPv6 destination. The tunnel has been working without problems for the last 30 weeks. Best regards Andreas
Tunnel T94714 not working (seems to be a pop problem)
[ch] Shadow Hawkins on Wednesday, 20 February 2013 22:05:11
Dear SIXXS support team, I got this automatic email this morning from my server being linked to tunnel T94714 with AICCU : ---------- message ---------- From: Dynamic DNS Client <ddclient@xxx> Date: Wed, Feb 20, 2013 at 11:20 AM Subject: status report from ddclient@xxx To: root WARNING: cannot connect to www.colliard.net:80 socket: IO::Socket::INET: Bad hostname 'www.colliard.net' regards, ddclient@fitpc.colliard.net (version 3.8.1 -------- Looking into it onto www.colliard.net server itself : $ dig -6 AAAA www.colliard.net ; <<>> DiG 9.8.2rc1-RedHat-9.8.2-0.10.rc1.el6_3.6 <<>> -6 AAAA www.colliard.net ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 31280 ;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;www.colliard.net. IN AAAA ;; ANSWER SECTION: www.colliard.net. 21568 IN CNAME colliard.net. colliard.net. 21599 IN AAAA 2a02:2528:ff00:15b::2 ;; Query time: 124 msec ;; SERVER: 2001:4860:4860::8888#53(2001:4860:4860::8888) ;; WHEN: Wed Feb 20 23:03:22 2013 ;; MSG SIZE rcvd: 76 I can confirm that there is a POP issue at chzrh02 probably. The ddclient daemon is requesting an ip.php script to find its public Internet IP and it is going by default over IPv6. My default gateway 2001:1620:f00:1ab::1 is not anymore answering to ping6 echo requests. I tried to restart AICCU service - which is no complaining... tunnel is coming up but nothing can go through. A reboot did not help either. FYI this tunnel was perfectly working for weeks ! I am very happy with your service. Thank you to have a look into this. Best regards Raphael Colliard raphael.colliard@gmail.com RCK4-SIXXS
Tunnel T94714 not working (seems to be a pop problem)
[ch] Jeroen Massar SixXS Staff on Thursday, 21 February 2013 21:37:10
Please note that this ticket is more than 2 years old already...
My default gateway 2001:1620:f00:1ab::1 is not anymore answering to ping6 echo requests.
What is your configuration and other details as requested by the "Reporting Problems" page pointed to by the big yellow box shown while posting?
I tried to restart AICCU service - which is no complaining... tunnel is coming up but nothing can go through.
Where are the details of this? Also, please note that restarting AICCU does not change anything. It will configure itself exactly the same way.

Please note Posting is only allowed when you are logged in.
Static Sunset Edition of SixXS
©2001-2017 SixXS - IPv6 Deployment & Tunnel Broker