Tickets - Cannot reach PoP endpoint :: SixXS - IPv6 Deployment & Tunnel Broker

Ticket ID: SIXXS #5873894
Ticket Status: Resolved

PoP: deham01 - Easynet (Hamburg)

Cannot reach PoP endpoint

Shadow Hawkins on Wednesday, 09 November 2011 22:07:06

Dear sixxs people, for some time I cannot reach the PoP endpoint (2001:6f8:900:cc8::1) of my tunnel (T21385) whereas I can ping my own end of the tunnel locally. The PoP endpoint is also not reachable from the outside ipv6 world. Please find more information below. Cheers, Manuel

# aiccu test Tunnel Information for T21385: POP Id : deham01 IPv6 Local : 2001:6f8:900:cc8::2/64 IPv6 Remote : 2001:6f8:900:cc8::1/64 Tunnel Type : ayiya Adminstate : enabled Userstate : enabled ####### ####### AICCU Quick Connectivity Test ####### ####### [1/8] Ping the IPv4 Local/Your Outer Endpoint (192.168.178.21) ### 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 192.168.178.21 (192.168.178.21) 56(84) bytes of data. 64 bytes from 192.168.178.21: icmp_req=1 ttl=64 time=0.056 ms 64 bytes from 192.168.178.21: icmp_req=2 ttl=64 time=0.043 ms 64 bytes from 192.168.178.21: icmp_req=3 ttl=64 time=0.044 ms --- 192.168.178.21 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 1998ms rtt min/avg/max/mdev = 0.043/0.047/0.056/0.009 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_req=1 ttl=55 time=93.1 ms 64 bytes from 212.224.0.188: icmp_req=2 ttl=55 time=102 ms 64 bytes from 212.224.0.188: icmp_req=3 ttl=55 time=63.8 ms --- 212.224.0.188 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2002ms rtt min/avg/max/mdev = 63.874/86.634/102.902/16.584 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, 60 byte packets 1 192.168.178.1 (192.168.178.1) 1.268 ms 9.165 ms 9.169 ms 2 bras1.stg.qsc.de (213.148.133.7) 41.414 ms 45.664 ms 50.282 ms 3 core4.stg.qsc.de (87.234.13.225) 54.581 ms 59.940 ms 65.032 ms 4 core1.fra.qsc.de (87.234.10.253) 83.250 ms 83.926 ms 85.355 ms 5 core4.fra.qsc.de (87.234.10.6) 89.117 ms 93.607 ms 137.754 ms 6 ipctgw-easynet.fra.qsc.de (212.202.213.114) 110.496 ms 44.407 ms 44.015 ms 7 ge7-1.cr20.isham.de.easynet.net (212.224.4.89) 57.802 ms 62.296 ms 68.235 ms 8 ge7-1.cr20.isham.de.easynet.net (212.224.4.89) 72.256 ms 78.839 ms 83.431 ms 9 deham01.sixxs.net (212.224.0.188) 89.357 ms 94.771 ms 100.018 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.034 ms 64 bytes from ::1: icmp_seq=2 ttl=64 time=0.042 ms 64 bytes from ::1: icmp_seq=3 ttl=64 time=0.042 ms --- ::1 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 1998ms rtt min/avg/max/mdev = 0.034/0.039/0.042/0.006 ms ###### Did this work? [Y/n] y ###### [5/8] Ping the IPv6 Local/Your Inner Tunnel Endpoint (2001:6f8:900:cc8::2) ### This confirms that your tunnel is configured ### If it doesn't reply then check your interface and routing tables PING 2001:6f8:900:cc8::2(2001:6f8:900:cc8::2) 56 data bytes 64 bytes from 2001:6f8:900:cc8::2: icmp_seq=1 ttl=64 time=0.036 ms 64 bytes from 2001:6f8:900:cc8::2: icmp_seq=2 ttl=64 time=0.045 ms 64 bytes from 2001:6f8:900:cc8::2: icmp_seq=3 ttl=64 time=0.045 ms --- 2001:6f8:900:cc8::2 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 1998ms rtt min/avg/max/mdev = 0.036/0.042/0.045/0.004 ms ###### Did this work? [Y/n] y ###### [6/8] Ping the IPv6 Remote/PoP Inner Tunnel Endpoint (2001:6f8:900:cc8::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:cc8::1(2001:6f8:900:cc8::1) 56 data bytes --- 2001:6f8:900:cc8::1 ping statistics --- 3 packets transmitted, 0 received, 100% packet loss, time 2014ms ###### Did this work? [Y/n] n

from some outside ipv6 host

IPv6 Ping Output: PING 2001:6f8:900:cc8::1(2001:6f8:900:cc8::1) 32 data bytes From 2001:6f8:800:1003::2 icmp_seq=0 Destination unreachable: No route From 2001:6f8:800:1003::2 icmp_seq=1 Destination unreachable: No route From 2001:6f8:800:1003::2 icmp_seq=2 Destination unreachable: No route From 2001:6f8:800:1003::2 icmp_seq=3 Destination unreachable: No route --- 2001:6f8:900:cc8::1 ping statistics --- 4 packets transmitted, 0 received, +4 errors, 100% packet loss, time 3007ms

more information

# ifconfig eth0 Protokoll:Ethernet Hardware Adresse 00:1d:60:76:6e:e7 inet Adresse:192.168.178.21 Bcast:192.168.178.255 Maske:255.255.255.0 inet6 Adresse: fe80::21d:60ff:fe76:6ee7/64 Gltigkeitsbereich:Verbindung UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:727358 errors:0 dropped:0 overruns:0 frame:0 TX packets:564067 errors:0 dropped:0 overruns:0 carrier:0 Kollisionen:0 Sendewarteschlangenlnge:1000 RX bytes:724138585 (690.5 MiB) TX bytes:126109520 (120.2 MiB) Interrupt:42 Basisadresse:0xc000 lo Protokoll:Lokale Schleife inet Adresse:127.0.0.1 Maske:255.0.0.0 inet6 Adresse: ::1/128 Gltigkeitsbereich:Maschine UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:325 errors:0 dropped:0 overruns:0 frame:0 TX packets:325 errors:0 dropped:0 overruns:0 carrier:0 Kollisionen:0 Sendewarteschlangenlnge:0 RX bytes:103835 (101.4 KiB) TX bytes:103835 (101.4 KiB) sixxs Protokoll:UNSPEC Hardware Adresse 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 inet6 Adresse: fe80::4f8:900:cc8:2/64 Gltigkeitsbereich:Verbindung inet6 Adresse: 2001:6f8:900:cc8::2/64 Gltigkeitsbereich:Global UP PUNKTZUPUNKT RUNNING NOARP MULTICAST MTU:1280 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 Kollisionen:0 Sendewarteschlangenlnge:500 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) # route -6 Kernel IPv6 Routentabelle Destination Next Hop Flag Met Ref Use If ::1/128 :: Un 0 1 20 lo fe80::/128 :: Un 0 1 0 lo fe80::21d:60ff:fe76:6ee7/128 :: Un 0 1 0 lo fe80::/64 :: U 256 0 0 eth0 ff00::/8 :: U 256 0 0 eth0 ::/0 :: !n -1 1 519 lo # uname -a Linux xenserver 3.0.4-gentoo #1 SMP Tue Sep 20 22:02:30 CEST 2011 x86_64 AMD Athlon(tm) 64 X2 Dual Core Processor 4800+ AuthenticAMD GNU/Linux # ntpdate ntp1.ptb.de 9 Nov 21:54:30 ntpdate[18131]: adjust time server 192.53.103.108 offset 0.000332 sec

messages during startup of aiccu

Nov 9 21:57:29 xenserver aiccu: sock_getline() : "200 SixXS TIC Service on nlams04.sixxs.net ready (http://www.sixxs.net)" Nov 9 21:57:29 xenserver aiccu: sock_printf() : "client TIC/draft-00 AICCU/2007.01.15-console-linux Linux/3.0.4-gentoo" Nov 9 21:57:30 xenserver aiccu: sock_getline() : "200 Client Identity accepted" Nov 9 21:57:30 xenserver aiccu: sock_printf() : "get unixtime" Nov 9 21:57:30 xenserver aiccu: sock_getline() : "200 1320872250" Nov 9 21:57:30 xenserver aiccu: sock_printf() : "starttls" Nov 9 21:57:30 xenserver aiccu: sock_getline() : "400 This service is not SSL enabled (yet)" Nov 9 21:57:30 xenserver aiccu: TIC Server does not support TLS but TLS is not required, continuing Nov 9 21:57:30 xenserver aiccu: sock_printf() : "username MZEI53-RIPE" Nov 9 21:57:30 xenserver aiccu: sock_getline() : "200 MZEI53-RIPE choose your authentication challenge please" Nov 9 21:57:30 xenserver aiccu: sock_printf() : "challenge md5" Nov 9 21:57:30 xenserver aiccu: sock_getline() : "200 <hex>" Nov 9 21:57:30 xenserver aiccu: sock_printf() : "authenticate md5 <hex>" Nov 9 21:57:30 xenserver aiccu: sock_getline() : "200 Successfully logged in using md5 as MZEI53-RIPE (Manuel Zeise)" Nov 9 21:57:30 xenserver aiccu: sock_printf() : "tunnel list" Nov 9 21:57:30 xenserver aiccu: sock_getline() : "201 Listing tunnels" Nov 9 21:57:30 xenserver aiccu: sock_getline() : "T21385 2001:6f8:900:cc8::2 ayiya deham01" Nov 9 21:57:30 xenserver aiccu: sock_getline() : "202 <tunnel_id> <ipv6_endpoint> <ipv4_endpoint> <pop_name>" Nov 9 21:57:30 xenserver aiccu: sock_printf() : "tunnel show T21385" Nov 9 21:57:30 xenserver aiccu: sock_getline() : "201 Showing tunnel information for T21385" Nov 9 21:57:31 xenserver aiccu: sock_getline() : "TunnelId: T21385" Nov 9 21:57:31 xenserver aiccu: sock_getline() : "Type: ayiya" Nov 9 21:57:31 xenserver aiccu: sock_getline() : "IPv6 Endpoint: 2001:6f8:900:cc8::2" Nov 9 21:57:31 xenserver aiccu: sock_getline() : "IPv6 POP: 2001:6f8:900:cc8::1" Nov 9 21:57:31 xenserver aiccu: sock_getline() : "IPv6 PrefixLength: 64" Nov 9 21:57:31 xenserver aiccu: sock_getline() : "Tunnel MTU: 1280" Nov 9 21:57:31 xenserver aiccu: sock_getline() : "Tunnel Name: My First Tunnel" Nov 9 21:57:31 xenserver aiccu: sock_getline() : "POP Id: deham01" Nov 9 21:57:31 xenserver aiccu: sock_getline() : "IPv4 Endpoint: ayiya" Nov 9 21:57:31 xenserver aiccu: sock_getline() : "IPv4 POP: 212.224.0.188" Nov 9 21:57:31 xenserver aiccu: sock_getline() : "UserState: enabled" Nov 9 21:57:31 xenserver aiccu: sock_getline() : "AdminState: enabled" Nov 9 21:57:31 xenserver aiccu: sock_getline() : "Password: <hex>" Nov 9 21:57:31 xenserver aiccu: sock_getline() : "Heartbeat_Interval: 60" Nov 9 21:57:31 xenserver aiccu: sock_getline() : "202 Done" Nov 9 21:57:31 xenserver aiccu: Succesfully retrieved tunnel information for T21385 Nov 9 21:57:31 xenserver aiccu: sock_printf() : "QUIT And All That Could Have Been..." Nov 9 21:57:31 xenserver aiccu: AICCU running as PID 22578 Nov 9 21:57:31 xenserver aiccu: [AYIYA-start] : Anything in Anything (draft-02) Nov 9 21:57:31 xenserver aiccu: [AYIYA-tun->tundev] : (Socket to TUN) started

State change: user Locked

Jeroen Massar SixXS Staff

on Wednesday, 09 November 2011 22:30:35

The state of this ticket has been changed to user

Cannot reach PoP endpoint

Jeroen Massar SixXS Staff

on Wednesday, 09 November 2011 22:34:15

AYIYA tunnels that are not sending valid packets are not configured on the PoP, thus indeed it won't be reachable from the outside then either. Check that routing table you pasted, there are no useful routes there. You might want to use: ip -6 ro show Your tunnel interface also does not show any packets tat have been sent.

Cannot reach PoP endpoint

Shadow Hawkins on Thursday, 10 November 2011 08:53:08

Hi Jeroen, the route settings seem to be reasonable to me:

# ip -6 ro show 2001:6f8:900:cc8::/64 dev sixxs proto kernel metric 256 fe80::/64 dev eth0 proto kernel metric 256 fe80::/64 dev sixxs proto kernel metric 256 ff00::/8 dev eth0 metric 256 ff00::/8 dev sixxs metric 256 default via 2001:6f8:900:cc8::1 dev sixxs metric 1024

I can also see the heartbeat activity going to deham01

# tcpdump -Xns 1500 host 212.224.0.188 -i eth0 tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on eth0, link-type EN10MB (Ethernet), capture size 1500 bytes 08:44:08.798703 IP 192.168.178.21.33951 > 212.224.0.188.5072: UDP, length 44 0x0000: 4500 0048 c81a 4000 4011 2a30 c0a8 b215 E..H..@.@.*0.... 0x0010: d4e0 00bc 849f 13d0 0034 e782 4152 103b .........4..AR.; 0x0020: 4ebb 80c8 2001 06f8 0900 0cc8 0000 0000 N............... 0x0030: 0000 0002 2414 a2a9 7fb3 11cb 501d dfbc ....$.......P... 0x0040: 07dd 02d9 8951 bd46 .....Q.F 08:44:08.799361 IP 192.168.178.21.33951 > 212.224.0.188.5072: UDP, length 44 0x0000: 4500 0048 c81b 4000 4011 2a2f c0a8 b215 E..H..@.@.*/.... 0x0010: d4e0 00bc 849f 13d0 0034 e782 4152 103b .........4..AR.; 0x0020: 4ebb 80c8 2001 06f8 0900 0cc8 0000 0000 N............... 0x0030: 0000 0002 2414 a2a9 7fb3 11cb 501d dfbc ....$.......P... 0x0040: 07dd 02d9 8951 bd46 .....Q.F 08:44:08.799586 IP 192.168.178.21.33951 > 212.224.0.188.5072: UDP, length 44 0x0000: 4500 0048 c81c 4000 4011 2a2e c0a8 b215 E..H..@.@.*..... 0x0010: d4e0 00bc 849f 13d0 0034 e782 4152 103b .........4..AR.; 0x0020: 4ebb 80c8 2001 06f8 0900 0cc8 0000 0000 N............... 0x0030: 0000 0002 2414 a2a9 7fb3 11cb 501d dfbc ....$.......P... 0x0040: 07dd 02d9 8951 bd46 .....Q.F 08:44:11.498900 IP 192.168.178.21.33951 > 212.224.0.188.5072: UDP, length 140 0x0000: 4500 00a8 c81d 4000 4011 29cd c0a8 b215 E.....@.@.)..... 0x0010: d4e0 00bc 849f 13d0 0094 c254 4152 1129 ...........TAR.) 0x0020: 4ebb 80cb 2001 06f8 0900 0cc8 0000 0000 N............... 0x0030: 0000 0002 c26e 960d 771e 74ae e8a8 75f6 .....n..w.t...u. 0x0040: eb9e 2123 2a98 b16f 6000 0000 0038 1140 ..!#*..o`....8.@ 0x0050: 2001 06f8 0900 0cc8 0000 0000 0000 0002 ................ 0x0060: 2001 0638 0504 2000 0000 0000 0000 0035 ...8...........5 0x0070: 007b 007b 0038 1861 2303 06ec 0000 12d1 .{.{.8.a#....... 0x0080: 0000 0d24 55d6 e6f7 d265 ff0e 8e2e 251f ...$U....e....%. 0x0090: 0000 0000 0000 0000 0000 0000 0000 0000 ................ 0x00a0: d265 ff4b 7fad 011e .e.K.... 08:45:08.799860 IP 192.168.178.21.33951 > 212.224.0.188.5072: UDP, length 44 0x0000: 4500 0048 c81e 4000 4011 2a2c c0a8 b215 E..H..@.@.*,.... 0x0010: d4e0 00bc 849f 13d0 0034 7676 4152 103b .........4vvAR.; 0x0020: 4ebb 8104 2001 06f8 0900 0cc8 0000 0000 N............... 0x0030: 0000 0002 f7bc 5951 cb28 05a7 b7f2 fcef ......YQ.(...... 0x0040: 1f2f 8e47 81fe 43ff ./.G..C. 08:46:08.800034 IP 192.168.178.21.33951 > 212.224.0.188.5072: UDP, length 44 0x0000: 4500 0048 c81f 4000 4011 2a2b c0a8 b215 E..H..@.@.*+.... 0x0010: d4e0 00bc 849f 13d0 0034 eb2d 4152 103b .........4.-AR.; 0x0020: 4ebb 8140 2001 06f8 0900 0cc8 0000 0000 N..@............ 0x0030: 0000 0002 07d9 798f 98c3 5e45 3d2a b362 ......y...^E=*.b 0x0040: 6fdf 6d94 d2ca bc04 o.m.....

and a traceroute gives reasonable results as well:

# traceroute -U -p 5072 deham01.sixxs.net traceroute to deham01.sixxs.net (212.224.0.188), 30 hops max, 60 byte packets 1 192.168.178.1 (192.168.178.1) 0.880 ms 1.996 ms 14.007 ms 2 bras1.stg.qsc.de (213.148.133.7) 96.154 ms 96.370 ms 96.345 ms 3 core4.stg.qsc.de (87.234.13.225) 57.429 ms 61.402 ms 65.697 ms 4 core1.fra.qsc.de (87.234.10.253) 136.218 ms 137.571 ms 137.727 ms 5 core4.fra.qsc.de (213.148.139.42) 92.736 ms 96.803 ms 104.810 ms 6 ipctgw-easynet.fra.qsc.de (212.202.213.114) 109.916 ms 41.520 ms 41.949 ms 7 ge7-1.cr20.isham.de.easynet.net (212.224.4.89) 56.041 ms 62.247 ms 66.514 ms 8 ge7-1.cr20.isham.de.easynet.net (212.224.4.89) 72.306 ms 77.333 ms 81.624 ms 9 * * * 10 * * * # traceroute deham01.sixxs.net traceroute to deham01.sixxs.net (212.224.0.188), 30 hops max, 60 byte packets 1 192.168.178.1 (192.168.178.1) 0.980 ms 1.411 ms 18.456 ms 2 bras1.stg.qsc.de (213.148.133.7) 42.694 ms 47.503 ms 51.659 ms 3 core4.stg.qsc.de (87.234.13.225) 56.223 ms 62.257 ms 66.367 ms 4 core1.fra.qsc.de (87.234.10.253) 75.823 ms 81.712 ms 85.824 ms 5 core4.fra.qsc.de (213.148.139.42) 90.239 ms 95.108 ms 101.264 ms 6 ipctgw-easynet.fra.qsc.de (212.202.213.114) 111.887 ms 44.428 ms 43.277 ms 7 ge7-1.cr20.isham.de.easynet.net (212.224.4.89) 58.460 ms 64.133 ms 67.709 ms 8 ge7-1.cr20.isham.de.easynet.net (212.224.4.89) 72.333 ms 77.978 ms 83.051 ms 9 deham01.sixxs.net (212.224.0.188) 92.159 ms 101.940 ms 102.285 ms

Cheers, Manuel PS. although the latest statistics shows no activity, the tunnel actually worked in the past: https://www.sixxs.net/home/tunnelinfo/latency/?type=latency&graphtime=1year&pop=deham01&ip=2001:6f8:900:cc8::2

Cannot reach PoP endpoint

Jeroen Massar SixXS Staff

on Thursday, 10 November 2011 10:33:09

the route settings seem to be reasonable to me:

Indeed, that one seems quite reasonable, the one you pasted above did not have any global addresses though. The PoP reports: Last Beat : 2011-11-10 06:52:23 (5967 seconds ago) When there are no heartbeats (and every valid AYIYA packet counts as one) the tunnel won't be up.

Cannot reach PoP endpoint

Shadow Hawkins on Thursday, 10 November 2011 18:09:30

Hi Jeroen, I am a bit puzzled: after starting aiccu, the route settings are apparently okay and the heartbeat is measurable, even for the PoP. However, I get neither a response from the PoP endpoint nor a route to the subnet from the outside. So, I cannot see where I can fix something on my side :/ Cheers, Manuel PS. There were no more heartbeats during the day as I had to switch it off to reach sixxs.net and other ipv6-ready sites.

Cannot reach PoP endpoint