SixXS::Sunset 2017-06-06

Ticket ID: SIXXS #973604
Ticket Status: User

PoP: simbx01 - Amis (Maribor)

Tunnel built up, but PoP IPv6 unreachable
[hu] Shadow Hawkins on Thursday, 12 February 2009 19:25:11
Hello My tunnel T17947 seems to have problems. I did an aiccu test, and test 6/8 (Ping6 the PoP) fails. "[6/8] Ping the IPv6 Remote/PoP Inner Tunnel Endpoint (2001:15c0:65ff:1ca::1) PING 2001:15c0:65ff:1ca::1(2001:15c0:65ff:1ca::1) 56 data bytes --- 2001:15c0:65ff:1ca::1 ping statistics --- 3 packets transmitted, 0 received, 100% packet loss, time 2008ms" I also did a ping from an other IPv6 server: "PING cl-459.mbx-01.si.sixxs.net(cl-459.mbx-01.si.sixxs.net) 56 data bytes From simbx01.sixxs.net icmp_seq=1 Destination unreachable: No route From simbx01.sixxs.net icmp_seq=2 Destination unreachable: No route" route -6 gives on last line: "::/0 2001:15c0:65ff:1ca::1 UG 1024 0 0 sixxs0" I had to stop aiccu to send this ticket :) Any ideas? regards Greg
Tunnel built up, but PoP IPv6 unreachable
[hu] Shadow Hawkins on Thursday, 12 February 2009 19:27:56
Oh and one thing more syslog tells me at aiccu start: Feb 12 19:23:19 gna aiccu: Succesfully retrieved tunnel information for T17947 Feb 12 19:23:19 gna aiccu: AICCU running as PID 3470 Feb 12 19:23:19 gna kernel: [4443804.937241] sixxs0: Disabled Privacy Extensions Feb 12 19:23:19 gna aiccu: [AYIYA-start] : Anything in Anything (draft-02) Feb 12 19:23:19 gna aiccu: [AYIYA-tun->tundev] : (Socket to TUN) started Feb 12 19:23:28 gna kernel: [4443813.946585] sixxs0: no IPv6 routers present
Tunnel built up, but PoP IPv6 unreachable
[ro] Shadow Hawkins on Thursday, 12 February 2009 19:55:35
I can confirm this. Tunnel is UP, I can ping my local end of the link, but not the other end. Windows error message is "Destination host unreachable."
Tunnel built up, but PoP IPv6 unreachable
[cz] Shadow Hawkins on Thursday, 12 February 2009 22:11:41
i got the same problem under my linux machine...
Tunnel built up, but PoP IPv6 unreachable
[sk] Shadow Hawkins on Friday, 13 February 2009 05:33:46
Same problem here...
Tunnel built up, but PoP IPv6 unreachable
[ch] Jeroen Massar SixXS Staff on Thursday, 26 February 2009 15:06:19
"Same problem" "me too". But where are the details requested in "Reporting Problems checklist" ? Without that, we can't help.
State change: user Locked
[ch] Jeroen Massar SixXS Staff on Friday, 13 February 2009 09:06:39
Message is Locked
The state of this ticket has been changed to user
Tunnel built up, but PoP IPv6 unreachable
[ch] Jeroen Massar SixXS Staff on Friday, 13 February 2009 09:08:05
For you, and the other "me toos", please actually follow the FULL "Reporting Problems" checklist and supply all the details. A traceroute over IPv4, to see if you can reach the PoP (which indicates that your tunnel has not sent a proper AYIYA packet for quite some while) would for instance already help a lot.
Tunnel built up, but PoP IPv6 unreachable
[hu] Shadow Hawkins on Friday, 13 February 2009 11:47:58
As i mentioned i DID an aiccu test, and only after test 6/8 failed, it means i can ping and traceroute the PoP, the IPv4 commmunication works, because the tunnel is setup, but there was no traffic flowing trough. I did a ping in screen yesterday evening, so i can see what happened: 52238 packets transmitted, 316 received, +51134 errors, 99% packet loss, time 52786603ms rtt min/avg/max/mdev = 75.239/93.625/574.098/56.131 ms This means to me, now that i did the test with aiccu verbose, now it works. But to provide data: root@gna:~# aiccu start Tunnel Information for T17947: POP Id : simbx01 IPv6 Local : 2001:15c0:65ff:1ca::2/64 IPv6 Remote : 2001:15c0:65ff:1ca::1/64 Tunnel Type : ayiya Adminstate : enabled Userstate : enabled OS: Ubuntu 7.10 aiccu version: 20070115-3 from APT repositories SYSLOG after aiccu verbose: Feb 13 11:18:03 gna aiccu: sock_getline() : "200 SixXS TIC Service on noc.sixxs.net ready (http://www.sixxs.net)" Feb 13 11:18:03 gna aiccu: sock_printf() : "client TIC/draft-00 AICCU/2007.01.15-console-linux Linux/2.6.22-16-generic" Feb 13 11:18:03 gna aiccu: sock_getline() : "200 Client Identity accepted" Feb 13 11:18:03 gna aiccu: sock_printf() : "get unixtime" Feb 13 11:18:03 gna aiccu: sock_getline() : "200 1234520282" Feb 13 11:18:03 gna aiccu: sock_printf() : "starttls" Feb 13 11:18:03 gna aiccu: sock_getline() : "400 This service is not SSL enabled (yet)" Feb 13 11:18:03 gna aiccu: TIC Server does not support TLS but TLS is not required, continuing Feb 13 11:18:03 gna aiccu: sock_printf() : "username GNR1-SIXXS" Feb 13 11:18:03 gna aiccu: sock_getline() : "200 Choose your authentication challenge please" Feb 13 11:18:03 gna aiccu: sock_printf() : "challenge md5" Feb 13 11:18:04 gna aiccu: sock_getline() : "200 (MASKED)" Feb 13 11:18:04 gna aiccu: sock_printf() : "authenticate md5 (MASKED)" Feb 13 11:18:04 gna aiccu: sock_getline() : "200 Succesfully logged in using md5 as GNR1-SIXXS (Gergely Nagy) from 2001:7b8:3:4f:202:b3ff:fe46:bec" Feb 13 11:18:04 gna aiccu: sock_printf() : "tunnel list" Feb 13 11:18:04 gna aiccu: sock_getline() : "201 Listing tunnels" Feb 13 11:18:04 gna aiccu: sock_getline() : "T17947 2001:15c0:65ff:1ca::2 ayiya simbx01" Feb 13 11:18:04 gna aiccu: sock_getline() : "202 <tunnel_id> <ipv6_endpoint> <ipv4_endpoint> <pop_name>" Feb 13 11:18:04 gna aiccu: sock_printf() : "tunnel show T17947" Feb 13 11:18:04 gna aiccu: sock_getline() : "201 Showing tunnel information for T17947" Feb 13 11:18:04 gna aiccu: sock_getline() : "TunnelId: T17947" Feb 13 11:18:04 gna aiccu: sock_getline() : "Type: ayiya" Feb 13 11:18:04 gna aiccu: sock_getline() : "IPv6 Endpoint: 2001:15c0:65ff:1ca::2" Feb 13 11:18:04 gna aiccu: sock_getline() : "IPv6 POP: 2001:15c0:65ff:1ca::1" Feb 13 11:18:04 gna aiccu: sock_getline() : "IPv6 PrefixLength: 64" Feb 13 11:18:04 gna aiccu: sock_getline() : "Tunnel MTU: 1280" Feb 13 11:18:04 gna aiccu: sock_getline() : "Tunnel Name: My First Tunnel" Feb 13 11:18:04 gna aiccu: sock_getline() : "POP Id: simbx01" Feb 13 11:18:04 gna aiccu: sock_getline() : "IPv4 Endpoint: ayiya" Feb 13 11:18:04 gna aiccu: sock_getline() : "IPv4 POP: 212.18.63.73" Feb 13 11:18:04 gna aiccu: sock_getline() : "UserState: enabled" Feb 13 11:18:04 gna aiccu: sock_getline() : "AdminState: enabled" Feb 13 11:18:04 gna aiccu: sock_getline() : "Password: (MASKED)" Feb 13 11:18:04 gna aiccu: sock_getline() : "Heartbeat_Interval: 60" Feb 13 11:18:04 gna aiccu: sock_getline() : "202 Done" Feb 13 11:18:04 gna aiccu: Succesfully retrieved tunnel information for T17947 Feb 13 11:18:04 gna aiccu: sock_printf() : "QUIT Forsaken" Feb 13 11:18:04 gna aiccu: AICCU running as PID 8061 Feb 13 11:18:04 gna aiccu: [AYIYA-start] : Anything in Anything (draft-02) Feb 13 11:18:04 gna aiccu: [AYIYA-tun->tundev] : (Socket to TUN) started i am really sorry that i didnt include my tracepath6 from outside yesterday, but it ended somehow like this: N: simbx01.sixxs.net X ms !N Notice the "N!" which means network unreachable and now it shows: tracepath6 ip6six.gnanet.net 1?: [LOCALHOST] pmtu 1480 1: gnanet-1.tunnel.tserv6.fra1.ipv6.he.net 21.907ms 1: gnanet-1.tunnel.tserv6.fra1.ipv6.he.net 20.755ms 2: gige-g2-4.core1.fra1.he.net 19.709ms 3: Cisco-F-VI-Gi2-5.Space.Net 25.156ms 4: Cisco-M-XLII-Te1-2.Space.Net 28.302ms 5: Cisco-M-XVI-Te1-4-v23.Space.Net 28.096ms 6: Cisco-M-VI-E5.Space.Net 34.416ms 7: maribor3-po-1.amis.net 53.196ms asymm 8 8: simbx01.sixxs.net 44.512ms asymm 9 9: simbx01.sixxs.net 44.975ms pmtu 1280 9: cl-459.mbx-01.si.sixxs.net 562.534ms reached 9: cl-459.mbx-01.si.sixxs.net 596.592ms reached The ipv4 tracepath reached both yesterday and now the PoP. So except the communication log (sock_ lines..), there is no difference in the output of aiccu, so aiccu did its job every time. Because my tunnel is on a PC that runs 24x7 and aiccu does it too, i am 99% sure this was not my / user problem, and i think both 3 "meetoos" have their tunnel up again without doing anythin new to their systems.
Tunnel built up, but PoP IPv6 unreachable
[ch] Jeroen Massar SixXS Staff on Friday, 13 February 2009 12:53:33
As i mentioned i DID an aiccu test, and only after test 6/8 failed,
it means i can ping and traceroute the PoP, the IPv4 commmunication works,
because the tunnel is setup, but there was no traffic flowing trough.
It doesn't say that at all. It only states that it fails, not WHAT the problem is and there can be legions of them. We hope to improve that in the next upcoming edition of AICCU though.
I did a ping in screen yesterday evening, so i can see what happened:
52238 packets transmitted, 316 received, +51134 errors, 99% packet loss, time 52786603ms
And what are these 'errors' supposed to mean and where did they come from, who generated those errors? Which path did the packets take etc etc etc... There are a lot possibilities here. Also, please note that ICMP is ratelimmited in a lot of networks.
i am really sorry that i didnt include my tracepath6 from outside yesterday,
but it ended somehow like this:
N: simbx01.sixxs.net X ms !N
Notice the "N!" which means network unreachable
Which is correct for the case when a tunnel is not up, which, as I mentioned already, was the case.
Tunnel built up, but PoP IPv6 unreachable
[hu] Shadow Hawkins on Friday, 13 February 2009 15:21:19
I see your points, and agree. Because currently the tunnel is up, i think this case should be closed as invalid. And for next time my checklist for my kind of problem: 1) Set aiccu.conf: Verbose True 1.1) get all relevant syslog lines on aiccu start, and paste it 2) do an aiccu stop 2.1) do an aiccu test and paste all output (traceroutes, pings etc) 3) do a route 6 and paste all output anything i left off?
Tunnel built up, but PoP IPv6 unreachable
[ch] Jeroen Massar SixXS Staff on Friday, 13 February 2009 15:48:11
The rest of the Reporting Problems list?
Tunnel built up, but PoP IPv6 unreachable
[hu] Shadow Hawkins on Friday, 13 February 2009 15:54:38
:) There are of course the identification things: userid, tunnelid, system data, version numbers which i didin't mention. But for diagnostic data maybe tcpdumps (but for a channel "not funciotning" what data could flow there?)
Tunnel built up, but PoP IPv6 unreachable
[at] Shadow Hawkins on Wednesday, 25 February 2009 19:59:24
Hello, I have the same problem as of this afternoon. After being up for more than 3 weeks with little breaks (dynamic ADSL) the connection just stopped working this afternoon. The IPv6 endpoint is not reachable ####### ####### AICCU Quick Connectivity Test ####### ####### [1/8] Ping the IPv4 Local/Your Outer Endpoint (85.124.99.152) ### 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 85.124.99.152 (85.124.99.152) 56(84) bytes of data. 64 bytes from 85.124.99.152: icmp_seq=1 ttl=64 time=0.246 ms 64 bytes from 85.124.99.152: icmp_seq=2 ttl=64 time=0.216 ms 64 bytes from 85.124.99.152: icmp_seq=3 ttl=64 time=0.219 ms --- 85.124.99.152 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 1998ms rtt min/avg/max/mdev = 0.216/0.227/0.246/0.013 ms ###### Did this work? [Y/n] y ####### [2/8] Ping the IPv4 Remote/PoP Outer Endpoint (212.18.63.73) ### 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.18.63.73 (212.18.63.73) 56(84) bytes of data. 64 bytes from 212.18.63.73: icmp_seq=1 ttl=59 time=64.9 ms 64 bytes from 212.18.63.73: icmp_seq=2 ttl=59 time=29.7 ms 64 bytes from 212.18.63.73: icmp_seq=3 ttl=59 time=62.5 ms --- 212.18.63.73 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2002ms rtt min/avg/max/mdev = 29.740/52.439/64.989/16.083 ms ###### Did this work? [Y/n] y ####### [3/8] Traceroute to the PoP (212.18.63.73) 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.18.63.73 (212.18.63.73), 30 hops max, 60 byte packets 1 mac3-fe-00-000.shuttle.vien.inode.at (213.229.45.251) 113.947 ms 113.360 ms 112.868 ms 2 bord-vl-00-510.shuttle.vien.inode.at (83.64.142.113) 112.386 ms 111.701 ms 111.214 ms 3 vie2-gb-03-003.shuttle.vien.inode.at (62.99.171.41) 110.720 ms 110.234 ms 109.753 ms 4 otta-po-00-002.shuttle.vien.inode.at (62.99.170.213) 109.235 ms 108.708 ms 108.216 ms 5 vix.amis.net (193.203.0.117) 107.651 ms 107.171 ms 107.427 ms 6 maribor3-po-1.amis.net (212.18.41.137) 106.943 ms 84.269 ms 83.751 ms 7 simbx01.sixxs.net (212.18.63.73) 83.199 ms 82.718 ms 82.245 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.226 ms 64 bytes from ::1: icmp_seq=2 ttl=64 time=0.226 ms 64 bytes from ::1: icmp_seq=3 ttl=64 time=0.228 ms --- ::1 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 1998ms rtt min/avg/max/mdev = 0.226/0.226/0.228/0.017 ms ###### Did this work? [Y/n] y ###### [5/8] Ping the IPv6 Local/Your Inner Tunnel Endpoint (2001:15c0:65ff:1f7::2) ### This confirms that your tunnel is configured ### If it doesn't reply then check your interface and routing tables PING 2001:15c0:65ff:1f7::2(2001:15c0:65ff:1f7::2) 56 data bytes 64 bytes from 2001:15c0:65ff:1f7::2: icmp_seq=1 ttl=64 time=0.244 ms 64 bytes from 2001:15c0:65ff:1f7::2: icmp_seq=2 ttl=64 time=0.240 ms 64 bytes from 2001:15c0:65ff:1f7::2: icmp_seq=3 ttl=64 time=0.245 ms --- 2001:15c0:65ff:1f7::2 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 1998ms rtt min/avg/max/mdev = 0.240/0.243/0.245/0.002 ms ###### Did this work? [Y/n] y ###### [6/8] Ping the IPv6 Remote/PoP Inner Tunnel Endpoint (2001:15c0:65ff:1f7::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:15c0:65ff:1f7::1(2001:15c0:65ff:1f7::1) 56 data bytes --- 2001:15c0:65ff:1f7::1 ping statistics --- 3 packets transmitted, 0 received, 100% packet loss, time 2016ms ###### Did this work? [Y/n] n Looking at the syslog output with verbose I see the following entries: <snip> Feb 25 19:53:25 zaphod aiccu: heartbeat_socket() - IPv4 : 85.124.99.152 Feb 25 19:53:25 zaphod aiccu: sock_getline() : "IPv6 POP: 2001:15c0:65ff:1f7::1" Feb 25 19:53:25 zaphod aiccu: sock_getline() : "IPv6 PrefixLength: 64" Feb 25 19:53:25 zaphod aiccu: sock_getline() : "Tunnel MTU: 1440" Feb 25 19:53:25 zaphod aiccu: sock_getline() : "Tunnel Name: IPV6" Feb 25 19:53:25 zaphod aiccu: sock_getline() : "POP Id: simbx01" Feb 25 19:53:25 zaphod aiccu: sock_getline() : "IPv4 Endpoint: heartbeat" Feb 25 19:53:25 zaphod aiccu: sock_getline() : "IPv4 POP: 212.18.63.73" Feb 25 19:53:25 zaphod aiccu: sock_getline() : "UserState: enabled" Feb 25 19:53:25 zaphod aiccu: sock_getline() : "AdminState: enabled" Feb 25 19:53:25 zaphod aiccu: sock_getline() : "Password: efd08f6c3c967987dbf6c7a1c5818dfa" Feb 25 19:53:25 zaphod aiccu: sock_getline() : "Heartbeat_Interval: 60" Feb 25 19:53:25 zaphod aiccu: sock_getline() : "202 Done" Feb 25 19:53:25 zaphod aiccu: Succesfully retrieved tunnel information for T19128 Feb 25 19:53:25 zaphod aiccu: sock_printf() : "QUIT Under the weeping moon" Feb 25 19:53:25 zaphod aiccu: AICCU running as PID 1474 Feb 25 19:53:25 zaphod kernel: [ 2579.393831] sixxs: Disabled Privacy Extensions Feb 25 19:53:25 zaphod aiccu: heartbeat_socket() - IPv4 : 85.124.99.152 Feb 25 19:53:25 zaphod aiccu: [HB] HEARTBEAT TUNNEL 2001:15c0:65ff:1f7::2 sender 1235588005 e1543b064060f2eb560fe96cdbaf4cda Feb 25 19:53:25 zaphod aiccu: [HB] HEARTBEAT TUNNEL 2001:15c0:65ff:1f7::2 sender 1235588005 e1543b064060f2eb560fe96cdbaf4cda Feb 25 19:54:25 zaphod aiccu: [HB] HEARTBEAT TUNNEL 2001:15c0:65ff:1f7::2 sender 1235588065 60acfd7b3d3e9ca8bb0b3cf2a03caf4e from then on the heartbeat is repeated every minute. Nevertheless the endpoint does not answer. It looks like it thinks that the tunnel is down, although there are heartbeat packets been sent out by aiccu.
Tunnel built up, but PoP IPv6 unreachable
[at] Shadow Hawkins on Wednesday, 25 February 2009 20:12:46
I forgot to mention something. According to the Tunnel Information page the tunnel was last active at 17:08. Tunnel Name IPV6 PoP Name simbx01 PoP Location Maribor, Slovenia PoP IPv4 212.18.63.73 Your IPv4 Heartbeat, currently 85.124.97.185 This is interesting since I got assigned a new ip address after my box restarted, but the info here still shows the IP I had before. Last Alive 2009-02-25 17:08:37 CET State Heartbeat (automatically enabled on the fly)
Tunnel built up, but PoP IPv6 unreachable
[at] Shadow Hawkins on Wednesday, 25 February 2009 22:10:00
Just a heads up, as of 22:00 the tunnel works again.
Tunnel built up, but PoP IPv6 unreachable
[ch] Jeroen Massar SixXS Staff on Thursday, 26 February 2009 15:00:37
The PoP only activates your tunnel (and thus updates that address) when it receives properly formatted + signed + timed heartbeat packets.
Tunnel built up, but PoP IPv6 unreachable
[cz] Shadow Hawkins on Thursday, 26 February 2009 14:59:23
Still not works for me: # aiccu test Tunnel Information for T19838: POP Id : simbx01 IPv6 Local : 2001:15c0:65ff:219::2/64 IPv6 Remote : 2001:15c0:65ff:219::1/64 Tunnel Type : 6in4-heartbeat Adminstate : enabled Userstate : enabled ####### ####### AICCU Quick Connectivity Test ####### ####### [1/8] Ping the IPv4 Local/Your Outer Endpoint (10.20.0.1) ### 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.20.0.1 (10.20.0.1) 56(84) bytes of data. 64 bytes from 10.20.0.1: icmp_seq=1 ttl=64 time=0.123 ms 64 bytes from 10.20.0.1: icmp_seq=2 ttl=64 time=0.037 ms 64 bytes from 10.20.0.1: icmp_seq=3 ttl=64 time=0.072 ms --- 10.20.0.1 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2006ms rtt min/avg/max/mdev = 0.037/0.077/0.123/0.036 ms ###### Did this work? [Y/n] y ####### [2/8] Ping the IPv4 Remote/PoP Outer Endpoint (212.18.63.73) ### 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.18.63.73 (212.18.63.73) 56(84) bytes of data. 64 bytes from 212.18.63.73: icmp_seq=1 ttl=52 time=23.0 ms 64 bytes from 212.18.63.73: icmp_seq=2 ttl=52 time=23.2 ms 64 bytes from 212.18.63.73: icmp_seq=3 ttl=52 time=23.0 ms --- 212.18.63.73 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2000ms rtt min/avg/max/mdev = 23.020/23.129/23.278/0.206 ms ###### Did this work? [Y/n] y ####### [3/8] Traceroute to the PoP (212.18.63.73) 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.18.63.73 (212.18.63.73), 30 hops max, 40 byte packets 1 10.20.0.254 (10.20.0.254) 0.793 ms 1.044 ms 0.635 ms 2 radiogw-int01-193-0.blue4.cz (77.236.193.1) 1.362 ms 1.390 ms 1.460 ms 3 agrsw01-ptp-radiogw-ext01.blue4.cz (77.236.192.65) 5.248 ms 4.753 ms 16.551 ms 4 asbrsv.blue4.cz (77.236.192.17) 6.549 ms 4.382 ms 4.369 ms 5 xe-10-0-0-300.prg-001-score-1-re0.interoute.net (212.23.50.229) 2.986 ms 3.178 ms 3.100 ms 6 ae2-0.fra-006-score-2-re0.interoute.net (84.233.138.210) 11.263 ms 11.301 ms 11.107 ms 7 decix-aon.highway.telekom.at (80.81.192.69) 16.675 ms 76.337 ms 16.476 ms 8 195.3.118.49 (195.3.118.49) 17.093 ms 17.293 ms 53.670 ms 9 195.3.68.34 (195.3.68.34) 16.621 ms 16.349 ms 16.993 ms 10 195.3.70.66 (195.3.70.66) 25.126 ms 26.273 ms 19.772 ms 11 80.120.176.182 (80.120.176.182) 17.489 ms 16.944 ms 16.943 ms 12 maribor3-po-1.amis.net (212.18.41.137) 22.902 ms 23.289 ms 22.937 ms 13 simbx01.sixxs.net (212.18.63.73) 23.516 ms 23.278 ms 24.063 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.088 ms 64 bytes from ::1: icmp_seq=2 ttl=64 time=0.095 ms 64 bytes from ::1: icmp_seq=3 ttl=64 time=0.092 ms --- ::1 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 1999ms rtt min/avg/max/mdev = 0.088/0.091/0.095/0.011 ms ###### Did this work? [Y/n] y ###### [5/8] Ping the IPv6 Local/Your Inner Tunnel Endpoint (2001:15c0:65ff:219::2) ### This confirms that your tunnel is configured ### If it doesn't reply then check your interface and routing tables PING 2001:15c0:65ff:219::2(2001:15c0:65ff:219::2) 56 data bytes 64 bytes from 2001:15c0:65ff:219::2: icmp_seq=1 ttl=64 time=0.090 ms 64 bytes from 2001:15c0:65ff:219::2: icmp_seq=2 ttl=64 time=0.097 ms 64 bytes from 2001:15c0:65ff:219::2: icmp_seq=3 ttl=64 time=0.088 ms --- 2001:15c0:65ff:219::2 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 1998ms rtt min/avg/max/mdev = 0.088/0.091/0.097/0.011 ms ###### Did this work? [Y/n] y ###### [6/8] Ping the IPv6 Remote/PoP Inner Tunnel Endpoint (2001:15c0:65ff:219::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:15c0:65ff:219::1(2001:15c0:65ff:219::1) 56 data bytes --- 2001:15c0:65ff:219::1 ping statistics --- 3 packets transmitted, 0 received, 100% packet loss, time 2008ms ###### Did this work? [Y/n] n Output of ip addr show: 14: sixxs@NONE: <POINTOPOINT,NOARP,UP,10000> mtu 1280 qdisc noqueue link/sit 10.20.0.1 peer 212.18.63.73 inet6 2001:15c0:65ff:219::2/64 scope global valid_lft forever preferred_lft forever inet6 fe80::a14:1/64 scope link valid_lft forever preferred_lft forever Output of ip -6 route show: 2001:15c0:65ff:219::/64 via :: dev sixxs metric 256 expires 21334328sec mtu 1280 advmss 1220 hoplimit 4294967295 2001:15c0:66ed:1::/64 dev eth0 metric 256 expires 21253849sec mtu 1500 advmss 1220 hoplimit 4294967295 fe80::/64 dev eth0 metric 256 expires 17884848sec mtu 1500 advmss 1220 hoplimit 4294967295 fe80::/64 via :: dev sixxs metric 256 expires 21334328sec mtu 1280 advmss 1220 hoplimit 4294967295 ff00::/8 dev eth0 metric 256 expires 17884848sec mtu 1500 advmss 1220 hoplimit 4294967295 ff00::/8 dev sixxs metric 256 expires 21334328sec mtu 1280 advmss 1220 hoplimit 4294967295 default via 2001:15c0:65ff:219::1 dev sixxs metric 1024 expires 21334328sec mtu 1280 advmss 1220 hoplimit 4294967295 Relevant part of syslog: Feb 26 14:48:14 ptakopysk aiccu: sock_getline() : "200 SixXS TIC Service on noc.sixxs.net ready (http://www.sixxs.net)" Feb 26 14:48:14 ptakopysk aiccu: sock_printf() : "client TIC/draft-00 AICCU/2007.01.15-console-linux Linux/2.6.22-3-k7" Feb 26 14:48:14 ptakopysk aiccu: sock_getline() : "200 Client Identity accepted" Feb 26 14:48:14 ptakopysk aiccu: sock_printf() : "get unixtime" Feb 26 14:48:14 ptakopysk aiccu: sock_getline() : "200 1235656094" Feb 26 14:48:14 ptakopysk aiccu: sock_printf() : "starttls" Feb 26 14:48:14 ptakopysk aiccu: sock_getline() : "400 This service is not SSL enabled (yet)" Feb 26 14:48:14 ptakopysk aiccu: TIC Server does not support TLS but TLS is not required, continuing Feb 26 14:48:14 ptakopysk aiccu: sock_printf() : "username JBC6-SIXXS" Feb 26 14:48:14 ptakopysk aiccu: sock_getline() : "200 Choose your authentication challenge please" Feb 26 14:48:14 ptakopysk aiccu: sock_printf() : "challenge md5" Feb 26 14:48:14 ptakopysk aiccu: sock_getline() : "200 2c9b19a8138106fe7ff51cfc1f8d6019" Feb 26 14:48:14 ptakopysk aiccu: sock_printf() : "authenticate md5 088f920dfa58b14d6ab14be7df38f263" Feb 26 14:48:14 ptakopysk aiccu: sock_getline() : "200 Succesfully logged in using md5 as JBC6-SIXXS (Jaroslav Barton) from 2001:7b8:3:4f:202:b3ff:fe46:bec" Feb 26 14:48:14 ptakopysk aiccu: sock_printf() : "tunnel show T19838" Feb 26 14:48:14 ptakopysk aiccu: sock_getline() : "201 Showing tunnel information for T19838" Feb 26 14:48:14 ptakopysk aiccu: sock_getline() : "TunnelId: T19838" Feb 26 14:48:14 ptakopysk aiccu: sock_getline() : "Type: 6in4-heartbeat" Feb 26 14:48:14 ptakopysk aiccu: sock_getline() : "IPv6 Endpoint: 2001:15c0:65ff:219::2" Feb 26 14:48:14 ptakopysk aiccu: sock_getline() : "IPv6 POP: 2001:15c0:65ff:219::1" Feb 26 14:48:14 ptakopysk aiccu: sock_getline() : "IPv6 PrefixLength: 64" Feb 26 14:48:14 ptakopysk aiccu: sock_getline() : "Tunnel MTU: 1280" Feb 26 14:48:14 ptakopysk aiccu: sock_getline() : "Tunnel Name: My First Tunnel" Feb 26 14:48:14 ptakopysk aiccu: sock_getline() : "POP Id: simbx01" Feb 26 14:48:14 ptakopysk aiccu: sock_getline() : "IPv4 Endpoint: heartbeat" Feb 26 14:48:14 ptakopysk aiccu: sock_getline() : "IPv4 POP: 212.18.63.73" Feb 26 14:48:14 ptakopysk aiccu: sock_getline() : "UserState: enabled" Feb 26 14:48:14 ptakopysk aiccu: sock_getline() : "AdminState: enabled" Feb 26 14:48:14 ptakopysk aiccu: sock_getline() : "Password: ***" Feb 26 14:48:14 ptakopysk aiccu: sock_getline() : "Heartbeat_Interval: 60" Feb 26 14:48:14 ptakopysk aiccu: sock_getline() : "202 Done" Feb 26 14:48:14 ptakopysk aiccu: Succesfully retrieved tunnel information for T19838 Feb 26 14:48:14 ptakopysk aiccu: sock_printf() : "QUIT Stranded" Feb 26 14:48:14 ptakopysk aiccu: AICCU running as PID 32250 Feb 26 14:48:14 ptakopysk kernel: sixxs: Disabled Privacy Extensions Feb 26 14:48:14 ptakopysk aiccu: heartbeat_socket() - IPv4 : 10.20.0.1 Feb 26 14:48:14 ptakopysk aiccu: [HB] HEARTBEAT TUNNEL 2001:15c0:65ff:219::2 sender 1235656094 843b96739c0d0920a6aa78516aafc66d Feb 26 14:48:14 ptakopysk aiccu: [HB] HEARTBEAT TUNNEL 2001:15c0:65ff:219::2 sender 1235656094 843b96739c0d0920a6aa78516aafc66d
Tunnel built up, but PoP IPv6 unreachable
[ch] Jeroen Massar SixXS Staff on Thursday, 26 February 2009 14:58:34
####### [1/8] Ping the IPv4 Local/Your Outer Endpoint (10.20.0.1)
Unless you properly configure the device that is doing NAT for you to forward protocol-41 packets to your host, proto-41 and proto-41/heartbeat tunnels won't work behind a NAT. If you need to cross a NAT, then use AYIYA.
Tunnel built up, but PoP IPv6 unreachable
[cz] Shadow Hawkins on Thursday, 26 February 2009 15:25:30
Proto 41 packets are redirected to my server.
Tunnel built up, but PoP IPv6 unreachable
[ch] Jeroen Massar SixXS Staff on Thursday, 26 February 2009 15:29:10
Are you sure? Do a tcpdump/wireshark (of the underlying interface of course) and you know where what goes wrong. Next to that, always check your firewall tables (both IPv4+IPv6). See the "Reporting Problems checklist" for more of these tips.
Tunnel built up, but PoP IPv6 unreachable
[cz] Shadow Hawkins on Thursday, 26 February 2009 15:41:29
Device which do NAT is Edimax BR6104-KP (small SoC router) without tcpdump. Tcpdump on server shows: 15:38:25.925023 IP 10.20.0.1 > simbx01.sixxs.net: IP6 cl-538.mbx-01.si.sixxs.net > gw-538.mbx-01.si.sixxs.net: ICMP6, echo request, seq 38, length 64 Tunnel works for 2 days. Problem starts at 17:08:37 without any changes in configuration on my side.
Tunnel built up, but PoP IPv6 unreachable
[ch] Jeroen Massar SixXS Staff on Friday, 27 February 2009 13:41:47
You are also supposed to see packets coming from the PoP. 64 bytes from 2001:15c0:65ff:219::2: icmp_seq=1 ttl=50 time=58.7 ms And as I can ping6 <tun>::2 all should be fine.

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