SixXS::Sunset 2017-06-06

Ticket ID: SIXXS #3217685
Ticket Status: User

PoP: noosl01 - Availo (Oslo)

Can't reach remote host
[no] Shadow Hawkins on Thursday, 16 December 2010 10:39:48
My tunnel seems to start up, but I can't reach anything further than the IPv6 Remote/PoP Inner Tunnel Endpoint (2001:16d8:ee00:f1::1). There is no firewall in use. username KTM3-SIXXS tunnel_id T38513 root@vimes:~# aiccu test ####### ####### AICCU Quick Connectivity Test ####### ####### [1/8] Ping the IPv4 Local/Your Outer Endpoint (10.0.2.2) ### 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 10.0.2.2 (10.0.2.2) 56(84) bytes of data. 64 bytes from 10.0.2.2: icmp_seq=1 ttl=64 time=0.035 ms 64 bytes from 10.0.2.2: icmp_seq=2 ttl=64 time=0.025 ms 64 bytes from 10.0.2.2: icmp_seq=3 ttl=64 time=0.023 ms --- 10.0.2.2 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 1999ms rtt min/avg/max/mdev = 0.023/0.027/0.035/0.008 ms ###### Did this work? [Y/n] ####### [2/8] Ping the IPv4 Remote/PoP Outer Endpoint (83.140.3.18) ### 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 83.140.3.18 (83.140.3.18) 56(84) bytes of data. 64 bytes from 83.140.3.18: icmp_seq=1 ttl=57 time=17.6 ms 64 bytes from 83.140.3.18: icmp_seq=2 ttl=57 time=8.14 ms 64 bytes from 83.140.3.18: icmp_seq=3 ttl=57 time=7.93 ms --- 83.140.3.18 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2009ms rtt min/avg/max/mdev = 7.932/11.234/17.630/4.524 ms ###### Did this work? [Y/n] ####### [3/8] Traceroute to the PoP (83.140.3.18) 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 83.140.3.18 (83.140.3.18), 30 hops max, 40 byte packets 1 Router.lan (10.0.2.1) 1.667 ms 1.972 ms 2.272 ms 2 10.12.67.1 (10.12.67.1) 6.541 ms 6.663 ms 14.758 ms 3 88.87.63.193 (88.87.63.193) 18.761 ms 27.733 ms 25.016 ms 4 80.65.48.61 (80.65.48.61) 41.379 ms 27.471 ms 31.084 ms 5 83.140.255.89.biz.sta.port80.se (83.140.255.89) 41.218 ms 20.571 ms 31.265 ms 6 83.140.255.82.biz.sta.port80.se (83.140.255.82) 21.025 ms 28.772 ms 15.334 ms 7 83.140.3.18 (83.140.3.18) 21.035 ms 15.109 ms 21.221 ms ###### Did this work? [Y/n] ###### [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.026 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.032 ms --- ::1 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 1998ms rtt min/avg/max/mdev = 0.026/0.028/0.032/0.006 ms ###### Did this work? [Y/n] ###### [5/8] Ping the IPv6 Local/Your Inner Tunnel Endpoint (2001:16d8:ee00:f1::2) ### This confirms that your tunnel is configured ### If it doesn't reply then check your interface and routing tables PING 2001:16d8:ee00:f1::2(2001:16d8:ee00:f1::2) 56 data bytes 64 bytes from 2001:16d8:ee00:f1::2: icmp_seq=1 ttl=64 time=0.027 ms 64 bytes from 2001:16d8:ee00:f1::2: icmp_seq=2 ttl=64 time=0.035 ms 64 bytes from 2001:16d8:ee00:f1::2: icmp_seq=3 ttl=64 time=0.034 ms --- 2001:16d8:ee00:f1::2 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 1998ms rtt min/avg/max/mdev = 0.027/0.032/0.035/0.003 ms ###### Did this work? [Y/n] ###### [6/8] Ping the IPv6 Remote/PoP Inner Tunnel Endpoint (2001:16d8:ee00: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 succesful then this could be both ### a firewalling and a routing/interface problem PING 2001:16d8:ee00:f1::1(2001:16d8:ee00:f1::1) 56 data bytes 64 bytes from 2001:16d8:ee00:f1::1: icmp_seq=1 ttl=64 time=17.1 ms 64 bytes from 2001:16d8:ee00:f1::1: icmp_seq=2 ttl=64 time=8.42 ms 64 bytes from 2001:16d8:ee00:f1::1: icmp_seq=3 ttl=64 time=8.17 ms --- 2001:16d8:ee00:f1::1 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2004ms rtt min/avg/max/mdev = 8.170/11.262/17.189/4.192 ms ###### Did this work? [Y/n] ###### [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), 30 hops max, 40 byte packets 1 * * * 2 * * * 3 * * * 4 * * * 5 * * * 6 * * * 7 * * * 8 * * * 9 * * * 10 * * * 11 * * * 12 * * * 13 * * * 14 * * * 15 * * * 16 * * * 17 * * * 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 * * * 24 * * * 25 * * * 26 * * * 27 * * * 28 * * * 29 * * * 30 * * * ###### Did this work? [Y/n] n root@vimes:~# uname -a Linux vimes 2.6.26-2-amd64 #1 SMP Thu Sep 16 15:56:38 UTC 2010 x86_64 GNU/Linux root@vimes:~# lsb_release -a No LSB modules are available. Distributor ID: Debian Description: Debian GNU/Linux 5.0.6 (lenny) Release: 5.0.6 Codename: lenny root@vimes:~# tail -6 /var/log/syslog Dec 16 10:09:41 vimes kernel: [178688.472139] sixxs: Disabled Privacy Extensions Dec 16 10:09:41 vimes aiccu: Succesfully retrieved tunnel information for T38513 Dec 16 10:09:41 vimes aiccu: AICCU running as PID 7335 Dec 16 10:09:41 vimes aiccu: [AYIYA-start] : Anything in Anything (draft-02) Dec 16 10:09:41 vimes aiccu: [AYIYA-tun->tundev] : (Socket to TUN) started Dec 16 10:09:50 vimes kernel: [178699.189821] sixxs: no IPv6 routers present
State change: user Locked
[ch] Jeroen Massar SixXS Staff on Thursday, 16 December 2010 13:39:22
Message is Locked
The state of this ticket has been changed to user
Can't reach remote host
[ch] Jeroen Massar SixXS Staff on Thursday, 16 December 2010 13:40:49
64 bytes from 2001:16d8:ee00:f1::1: icmp_seq=2 ttl=64 time=8.42 ms
As you seem to be able to reach the PoP, you'll have to check the other variables. See that big orange box for the details we'd like to see. Just as a note, AICCU does not fix routing tables, firewall rules and all kinds of other such factors, as it does not know about a number of things and maybe that is the way you want to configure it. Please use the forums for solving your problem.

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

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