|
one of three tunnels stopped working on 12th of July
![[de]](/s/countries/de.gif) Shadow Hawkins on Saturday, 16 July 2011 11:12:30
Hi there,
my tunnel T60305/ayiya suddenly stopped working on 12th of July without any interaction from my side (i wasn't even at home).
I tried to enable my other tunnels (T64301/heartbeat and T73485/ayiya) on the same host (freebsd) and they are working fine.
T60305 also doesn't work on other systems.
I am not even able to ping my own local ipv6 address when using T60305.
What can be wrong? I even tried to switch to heartbeat and back to ayiya for testing, losing credits - without success (OK, i successfully lost credits, right).
Any pointer are really appreciated, i don't have any idea right now, what could be wrong. According to the logs, everything is fine.
cheers & thanks,
Thorsten
one of three tunnels stopped working on 12th of July
Pop side pings:
64 bytes from 2001:6f8:1c00:409::1: icmp_seq=1 ttl=53 time=22.8 ms
Your side pings:
64 bytes from 2001:6f8:1c00:409::2: icmp_seq=1 ttl=52 time=48.4 ms
What kind of tests (and their output) did you perform?
That big yellow box asks for people to post as much details as possible, I am really starting to wonder why people are not doing that actually as it seems to be skipped over a lot.
one of three tunnels stopped working on 12th of July
Shadow Hawkins on Monday, 18 July 2011 16:51:17
Hi Jeroen,
since i also use ipv6-only services i can detect outages pretty fast. I also used icmp for debugging...
for example, exactly at the time of your response, the ipv6 tunnel was working again. Unfortunately, 2 days later, the same problems arise:
From my tunnel endpoint:
PING6(56=40+8+8 bytes) 2001:6f8:1c00:409::2 --> 2001:6f8:1c00:409::1
^C
--- 2001:6f8:1c00:409::1 ping6 statistics ---
116 packets transmitted, 0 packets received, 100.0% packet loss
From outside:
PING 2001:6f8:1c00:409::1(2001:6f8:1c00:409::1) 56 data bytes
From 2001:6f8:800:1003::3 icmp_seq=1 Destination unreachable: No route
From 2001:6f8:800:1003::3 icmp_seq=2 Destination unreachable: No route
--- 2001:6f8:1c00:409::1 ping statistics ---
2 packets transmitted, 0 received, +2 errors, 100% packet loss, time 1001ms
and a tracerout:
$ traceroute6 -n 2001:6f8:1c00:409::2
traceroute to 2001:6f8:1c00:409::2 (2001:6f8:1c00:409::2), 30 hops max, 80 byte packets
1 2a01:488:66::2ea3:481c 0.038 ms 0.008 ms 0.007 ms
2 2a01:488:fade:fefe::43 0.263 ms 2a01:488:fade:fefe::53 0.244 ms 2a01:488:fade:fefe::43 0.249 ms
3 2001:2000:3080:1ca::1 0.601 ms * *
4 2001:2000:3018:10::1 7.560 ms 7.562 ms 7.557 ms
5 2001:6f8:1:0:87:86:71:249 11.143 ms 11.415 ms 11.417 ms
6 2001:6f8:800::10:48 11.000 ms 11.488 ms 11.481 ms
7 2001:6f8:800:1003::3 11.459 ms !N 11.744 ms !N 11.969 ms !N
From the aiccu logs:
Jul 18 16:41:31 fury sixxs-aiccu: sock_getline() : "200 Successfully logged in using md5 as TSH14-SIXXS (Thorsten Schroeder)"
Jul 18 16:41:31 fury sixxs-aiccu: sock_printf() : "tunnel show T60305"
Jul 18 16:41:32 fury sixxs-aiccu: sock_getline() : "201 Showing tunnel information for T60305"
Jul 18 16:41:32 fury sixxs-aiccu: sock_getline() : "TunnelId: T60305"
Jul 18 16:41:32 fury sixxs-aiccu: sock_getline() : "Type: ayiya"
Jul 18 16:41:32 fury sixxs-aiccu: sock_getline() : "IPv6 Endpoint: 2001:6f8:1c00:409::2"
Jul 18 16:41:32 fury sixxs-aiccu: sock_getline() : "IPv6 POP: 2001:6f8:1c00:409::1"
[...]
Any ideas?
cheers,
Thorsten
one of three tunnels stopped working on 12th of July
When the PoP sends back un unreachable for the <tunnel>::1 (PoP side) address of the tunnel, it means that the tunnel is not configured. In other words, no valid heartbeat or AYIYA packets are received. (Static tunnels are always configured)
one of three tunnels stopped working on 12th of July
Shadow Hawkins on Monday, 18 July 2011 17:50:28
Hi Jeroen,
so do you see the issue? i didn't changed anything on my side, it just stopped working from one minute to another. even the logs don't tell me something might be wrong.
can't you please check what's happening on the other side of the tunnel (from my point of view)?
cheers.
Thorsten
one of three tunnels stopped working on 12th of July
Shadow Hawkins on Tuesday, 19 July 2011 00:38:12
Hi again,
can you please check why the tunnel is not configured on your side? I double checked with my other two tunnels (one heartbeat and one ayiya) and they are working from exactly that configuration and host (except for the subnet routing of course).
my log looks pretty much okay, there is nothing that looks suspicious on my side.
i can't exclude that i am wrong anyway, but could you please give some advice what could possibly be wrong on my side? please... i also already checked different other similar issues in the ticket tracking system, but most of them were simply closed as "works for me" or "solved" without any comment.
I'm using FreeBSD 8.2-RELEASE-p2 and sixxs-aiccu from ports. This setup was working perfectly fine before, without any modification. This host is dedicated to ipv6 tunnel stuff, i did not modify it after setting up the tunnel stuff.
thanks & regards,
thorsten
|
![[ch]](/s/countries/ch.gif)
on Saturday, 16 July 2011 11:51:35
Posting is only allowed when you are