Tickets - Tunnel is up, but no connectivity :: SixXS

Ticket ID: SIXXS #11084806
Ticket Status: Resolved

PoP: brudi01 - (Uberlandia)

Tunnel is up, but no connectivity

Shadow Hawkins on Saturday, 15 February 2014 15:43:06

Hello! My name is Thiago Martins, my e-mail is thiagocmartinsc@gmail.com. My account is TMG11-SIXXS and my tunnel ID is T110410. The tunnel is up but, no IPv6 connectivity, look: -- root@firewall-1:~# service aiccu restart aiccu stop/waiting aiccu start/running root@firewall-1:~# grep aiccu /var/log/syslog Feb 15 13:37:40 firewall-1 aiccu[10114]: Already running instance signaled, exiting Feb 15 13:37:44 firewall-1 aiccu[10142]: Successfully retrieved tunnel information for T110410 Feb 15 13:37:44 firewall-1 aiccu[10147]: AICCU running as PID 10147 root@firewall-1:~# ip -6 r | grep sixxs 2001:1291:200:3f6::/64 dev sixxs proto kernel metric 256 fe80::/64 dev sixxs proto kernel metric 256 default via 2001:1291:200:3f6::1 dev sixxs metric 1024 root@firewall-1:~# ping6 -c 5 2001:1291:200:3f6::1 PING 2001:1291:200:3f6::1(2001:1291:200:3f6::1) 56 data bytes --- 2001:1291:200:3f6::1 ping statistics --- 5 packets transmitted, 0 received, 100% packet loss, time 4033ms root@firewall-1:~# ping6 -c 5 google.com PING google.com(2800:3f0:4001:814::100e) 56 data bytes --- google.com ping statistics --- 5 packets transmitted, 0 received, 100% packet loss, time 4031ms -- It was working until this morning! Please, help! Thanks! Thiago

Tunnel is up, but no connectivity

Jeroen Massar SixXS Staff

on Saturday, 15 February 2014 17:07:35

If you can't ping the other side of the tunnel, then your tunnel, by definition, is not 'up'. Please read the big yellow/orange box while posting and/or the "Reporting Problems" section of the contact page, and provide the requested details.

Tunnel is up, but no connectivity

Shadow Hawkins on Saturday, 15 February 2014 22:53:03

Restarting aiccu daemon with "verbose = true": --- Feb 15 19:38:30 firewall-1 aiccu[11249]: Already running instance signaled, exiting Feb 15 19:38:32 firewall-1 aiccu[11277]: sock_getline() : "200 SixXS TIC Service on nlams01.sixxs.net ready (http://www.sixxs.net)" Feb 15 19:38:32 firewall-1 aiccu[11277]: sock_printf() : "client TIC/draft-00 AICCU/2007.01.15-console-linux Linux/3.13.0-8-generic" Feb 15 19:38:32 firewall-1 aiccu[11277]: sock_getline() : "200 Client Identity accepted" Feb 15 19:38:32 firewall-1 aiccu[11277]: sock_printf() : "get unixtime" Feb 15 19:38:33 firewall-1 aiccu[11277]: sock_getline() : "200 1392500313" Feb 15 19:38:33 firewall-1 aiccu[11277]: sock_printf() : "starttls" Feb 15 19:38:33 firewall-1 aiccu[11277]: sock_getline() : "200 Go ahead, we are now talking securely" Feb 15 19:38:34 firewall-1 aiccu[11277]: TLS Handshake completed successfully Feb 15 19:38:34 firewall-1 aiccu[11277]: sock_printf() : "username TMG11-SIXXS" Feb 15 19:38:34 firewall-1 aiccu[11277]: sock_getline() : "200 TMG11-SIXXS choose your authentication challenge please" Feb 15 19:38:34 firewall-1 aiccu[11277]: sock_printf() : "challenge md5" Feb 15 19:38:34 firewall-1 aiccu[11277]: sock_getline() : "200 94532e356a125fade78f55f6386ebdde" Feb 15 19:38:34 firewall-1 aiccu[11277]: sock_printf() : "authenticate md5 c95cc5189dccb505878d87d1a77f1d0a" Feb 15 19:38:34 firewall-1 aiccu[11277]: sock_getline() : "200 Successfully logged in using md5 as TMG11-SIXXS (Thiago Martins)" Feb 15 19:38:34 firewall-1 aiccu[11277]: sock_printf() : "tunnel show T110410" Feb 15 19:38:35 firewall-1 aiccu[11277]: sock_getline() : "201 Showing tunnel information for T110410" Feb 15 19:38:35 firewall-1 aiccu[11277]: sock_getline() : "TunnelId: T110410" Feb 15 19:38:35 firewall-1 aiccu[11277]: sock_getline() : "Type: 6in4-heartbeat" Feb 15 19:38:35 firewall-1 aiccu[11277]: sock_getline() : "IPv6 Endpoint: 2001:1291:200:3f6::2" Feb 15 19:38:35 firewall-1 aiccu[11277]: sock_getline() : "IPv6 POP: 2001:1291:200:3f6::1" Feb 15 19:38:35 firewall-1 aiccu[11277]: sock_getline() : "IPv6 PrefixLength: 64" Feb 15 19:38:35 firewall-1 aiccu[11277]: sock_getline() : "Tunnel MTU: 1280" Feb 15 19:38:35 firewall-1 aiccu[11277]: sock_getline() : "Tunnel Name: Interface do roteador IPv6 SixxS.net, blocos roteados por aqui" Feb 15 19:38:35 firewall-1 aiccu[11277]: sock_getline() : "POP Id: brudi01" Feb 15 19:38:35 firewall-1 aiccu[11277]: sock_getline() : "IPv4 Endpoint: heartbeat" Feb 15 19:38:35 firewall-1 aiccu[11277]: sock_getline() : "IPv4 POP: 201.48.254.14" Feb 15 19:38:35 firewall-1 aiccu[11277]: sock_getline() : "UserState: enabled" Feb 15 19:38:35 firewall-1 aiccu[11277]: sock_getline() : "AdminState: enabled" Feb 15 19:38:35 firewall-1 aiccu[11277]: sock_getline() : "Password: ..." Feb 15 19:38:35 firewall-1 aiccu[11277]: sock_getline() : "Heartbeat_Interval: 60" Feb 15 19:38:35 firewall-1 aiccu[11277]: sock_getline() : "202 Done" Feb 15 19:38:35 firewall-1 aiccu[11277]: Successfully retrieved tunnel information for T110410 Feb 15 19:38:35 firewall-1 aiccu[11277]: sock_printf() : "QUIT Zij die gaan, groeten u" Feb 15 19:38:35 firewall-1 aiccu[11282]: AICCU running as PID 11282 Feb 15 19:38:35 firewall-1 aiccu[11282]: heartbeat_socket() - IPv4 : 187.57.159.94 Feb 15 19:38:35 firewall-1 aiccu[11282]: [HB] HEARTBEAT TUNNEL 2001:1291:200:3f6::2 sender 1392500315 48aaxxxxxx52bee0b --- Still no IPv6 connectivity, I can not ping my PoP: --- root@fdquaf-1:~# ping -c 3 201.48.254.14 PING 201.48.254.14 (201.48.254.14) 56(84) bytes of data. --- 201.48.254.14 ping statistics --- 3 packets transmitted, 0 received, 100% packet loss, time 1999ms --- I need help! Regards, Thiago

Tunnel is up, but no connectivity

Shadow Hawkins on Saturday, 15 February 2014 21:21:45

That's true... Sorry... Weird is that I can ping the PoP, look: --- root@firewall-1:~# ping -c 3 tic.sixxs.net PING tic.sixxs.net (213.197.27.252) 56(84) bytes of data. 64 bytes from tunnelserver.concepts-ict.net (213.197.27.252): icmp_seq=1 ttl=49 time=250 ms 64 bytes from tunnelserver.concepts-ict.net (213.197.27.252): icmp_seq=2 ttl=49 time=241 ms 64 bytes from tunnelserver.concepts-ict.net (213.197.27.252): icmp_seq=3 ttl=49 time=241 ms --- But, as you said, tunnel isn't up. My IPv4 ISP is working, I can browse the web normally... I'll read "Reporting Problems" to debug it. Tks! Thiago

Tunnel is up, but no connectivity

Shadow Hawkins on Saturday, 15 February 2014 21:23:13

I mean, this isn't the PoP, sorry ("tic server")... I'll follow the test instruction according. Tks

Tunnel is up, but no connectivity

Shadow Hawkins on Saturday, 15 February 2014 21:34:17

ERRATA: I _can not_ ping PoP (got it from "Tunnel Information for T110410" sixxs.net page): -- root@firewall-1:~# ping -c 5 201.48.254.14 PING 201.48.254.14 (201.48.254.14) 56(84) bytes of data. --- 201.48.254.14 ping statistics --- 5 packets transmitted, 0 received, 100% packet loss, time 4033ms -- I can not reach PoP with traceroute: -- root@firewall-1:~# traceroute 201.48.254.14 traceroute to 201.48.254.14 (201.48.254.14), 30 hops max, 60 byte packets 1 * * * 2 187-100-62-17.dsl.telesp.net.br (187.100.62.17) 2.886 ms 2.809 ms 2.726 ms 3 201-0-5-1.dsl.telesp.net.br (201.0.5.1) 2.665 ms 2.672 ms 2.660 ms 4 187-100-53-162.dsl.telesp.net.br (187.100.53.162) 2.334 ms 2.257 ms 187-100-53-166.dsl.telesp.net.br (187.100.53.166) 10.123 ms 5 xe-2-0-0-0.border-c.spo-piaf.ctbc.com.br (201.48.46.245) 3.038 ms 2.788 ms 2.719 ms 6 et-0-0-1-0.core-b.spo-piaf.ctbc.com.br (201.48.46.37) 2.334 ms 3.754 ms 3.722 ms 7 ge-4-1-2-0.core-a.spo511.ctbc.com.br (201.48.46.86) 8.617 ms 8.674 ms 8.708 ms 8 * * 201-048-047-210.static.ctbctelecom.com.br (201.48.47.210) 10.941 ms 9 * * * 10 * * * 11 * * * 12 * * * 13 * * * 14 * * * 15 * * * -- But I can ping google (sixxs tic server) or browse the web... Look: --- root@firewall-1:~# ping -c 3 google.com PING google.com (173.194.118.129) 56(84) bytes of data. 64 bytes from gru06s11-in-f1.1e100.net (173.194.118.129): icmp_seq=1 ttl=56 time=5.38 ms 64 bytes from gru06s11-in-f1.1e100.net (173.194.118.129): icmp_seq=2 ttl=56 time=3.33 ms 64 bytes from gru06s11-in-f1.1e100.net (173.194.118.129): icmp_seq=3 ttl=56 time=3.67 ms --- google.com ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2002ms rtt min/avg/max/mdev = 3.332/4.130/5.384/0.897 ms --- Apparently, something is wrong within CTBC ISP, my PoP provider... I'm finishing to read "Reporting Problems" page. Tks, Thiago

Tunnel is up, but no connectivity

Jeroen Massar SixXS Staff

on Saturday, 15 February 2014 22:55:56

Pings fine from the other side of the world (hence the latency):

PING brudi01.sixxs.net (201.48.254.14) 56(84) bytes of data. 64 bytes from brudi01.sixxs.net (201.48.254.14): icmp_req=1 ttl=52 time=253 ms 64 bytes from brudi01.sixxs.net (201.48.254.14): icmp_req=2 ttl=52 time=253 ms ..

The routing path from the PoP to one hop before your endpoint is broken it seems though:

traceroute to 187.100.62.17 (187.100.62.17), 30 hops max, 60 byte packets 1 ge-0-2-0-71.seed.ula001.ctbc.com.br (201.48.254.13) 201.629 ms 201.706 ms 201.763 ms 2 ge-1-0-7-0.core-b.ula001.ctbc.com.br (201.48.44.69) 1.065 ms 1.384 ms 1.357 ms 3 * * * 4 xe-5-3-0-0.border-b.spo511.ctbc.com.br (201.48.46.33) 20.188 ms 20.160 ms 20.107 ms 5 * * * 6 * * * 7 * * * 8 * * *

Something is having routing issues, unfortunately very little we can do about. You might want to contact your ISP about that.

Tunnel is up, but no connectivity

Shadow Hawkins on Saturday, 15 February 2014 23:51:19

Well, My ISP can enter within CTBC network, the PoP IPv6 provider, look: --- root@firewall-1:~# traceroute 201.48.254.14 traceroute to 201.48.254.14 (201.48.254.14), 30 hops max, 60 byte packets 1 * * * 2 187-100-62-17.dsl.telesp.net.br (187.100.62.17) 2.005 ms 2.096 ms 2.138 ms 3 201-0-5-1.dsl.telesp.net.br (201.0.5.1) 2.298 ms 2.267 ms 2.234 ms 4 187-100-53-166.dsl.telesp.net.br (187.100.53.166) 88.847 ms 88.768 ms 88.682 ms 5 xe-2-0-0-0.border-c.spo-piaf.ctbc.com.br (201.48.46.245) 2.872 ms 2.873 ms 2.797 ms 6 et-0-0-1-0.core-b.spo-piaf.ctbc.com.br (201.48.46.37) 2.048 ms 1.843 ms 1.770 ms 7 ge-4-1-2-0.core-a.spo511.ctbc.com.br (201.48.46.86) 7.958 ms 12.131 ms 15.398 ms 8 201-048-047-210.static.ctbctelecom.com.br (201.48.47.210) 12.686 ms 12.530 ms * 9 * * * 10 * * * 11 * * * 12 * * * 13 * * * --- This doesn't means that my ISP can, in fact, enter into the CTBC PoP network? The traffic stops at the router 201-048-047-210.static.ctbctelecom.com.br (201.48.47.210), which is very, very close to the PoP (201.48.254.14), so, how can this be a problem with my ISP?! Nevertheless, my ISP employees are so dumb, that I have no idea about how to tell them about this problem, they don't even what that IPv6 is. I'm serious trouble now... My IPv4 ISP is called "VIVO / Telefnica", they are the worse in the country. I'll use this ticket as en evidence of they fault. If I'm lucky, the guys from Uberlndia CTBC might be able help me a bit... Thanks anyway, Thiago

Tunnel is up, but no connectivity

Shadow Hawkins on Saturday, 15 February 2014 23:52:59

I meant: sed/they don't even what that IPv6 is/they don't even knows what that IPv6 is/

Tunnel is up, but no connectivity

Shadow Hawkins on Sunday, 16 February 2014 18:03:18

Hello! I talked with my ISP (VIVO Fibra) and they didn't find any problems within their own infrastructure... Apparently, the problem lies _within_ the PoP provider, which is CTBC, precisely at the router: 201-048-047-210.static.ctbctelecom.com.br (201.48.47.210) <- Package loss happening here! Should I call CTBC at Uberlndia instead?! Thanks! Thiago

Tunnel is up, but no connectivity

Shadow Hawkins on Monday, 17 February 2014 12:05:24

Problem fixed! --- root@firewall-1:~# traceroute 201.48.254.14 traceroute to 201.48.254.14 (201.48.254.14), 30 hops max, 60 byte packets 1 * * * 2 187-100-62-17.dsl.telesp.net.br (187.100.62.17) 2.033 ms 1.960 ms 1.952 ms 3 201-0-5-1.dsl.telesp.net.br (201.0.5.1) 40.067 ms 40.075 ms 39.997 ms 4 187-100-53-162.dsl.telesp.net.br (187.100.53.162) 5.258 ms 5.178 ms 187-100-53-166.dsl.telesp.net.br (187.100.53.166) 27.763 ms 5 xe-2-0-0-0.border-c.spo-piaf.ctbc.com.br (201.48.46.245) 2.123 ms 2.187 ms 2.109 ms 6 et-0-0-1-0.core-b.spo-piaf.ctbc.com.br (201.48.46.37) 2.105 ms 1.559 ms 1.473 ms 7 ge-4-1-2-0.core-a.spo511.ctbc.com.br (201.48.46.86) 6.813 ms 7.567 ms 7.819 ms 8 201-048-047-210.static.ctbctelecom.com.br (201.48.47.210) 11.515 ms 16.742 ms 16.596 ms 9 ge-1-0-0-0.seed.ula001.ctbc.com.br (201.48.44.70) 16.752 ms 16.231 ms * 10 brudi01.sixxs.net (201.48.254.14) 17.063 ms 16.396 ms 16.891 ms --- --- root@firewall-1:~# ping6 -c 3 google.com PING google.com(2800:3f0:4001:814::1000) 56 data bytes 64 bytes from 2800:3f0:4001:814::1000: icmp_seq=1 ttl=56 time=40.4 ms 64 bytes from 2800:3f0:4001:814::1000: icmp_seq=2 ttl=56 time=32.7 ms 64 bytes from 2800:3f0:4001:814::1000: icmp_seq=3 ttl=56 time=33.1 ms --- google.com ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2002ms rtt min/avg/max/mdev = 32.778/35.440/40.411/3.524 ms --- Tks!

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