|
Ticket ID: SIXXS #3628005 Ticket Status: Resolved PoP: simbx01 - Amis (Maribor)
Tunnel stopped working
![[si]](/s/countries/si.gif) Shadow Hawkins on Wednesday, 09 February 2011 09:21:20
I have read and followed the "Reporting Problems" section on the Contact page.
I am removing these five pre-filled lines to demonstrate that I really read it.
I am providing the full details as requested on the mentioned Contact page.
If I do not remove this, then please ignore this message as I didn't read it anyway.
------------------------------------------------------------------------------>8
My tunnel stopped working yesterday 2011/02/02 around 21:15 hour.
This normally happens once per week, but restarting aiccu service on my ubuntu box usually helps. Not this time. Aiccu starts ok, there are not no error messages in logs, sixxs network device is up, ipv6 default route is established, but i cannot even ping6 my defaultrouter...
# ping6 2001:15c0:65ff:493::1
PING 2001:15c0:65ff:493::1(2001:15c0:65ff:493::1) 56 data bytes
^C
--- 2001:15c0:65ff:493::1 ping statistics ---
26 packets transmitted, 0 received, 100% packet loss, time 24999ms
Tunnel stopped working
![[cz]](/s/countries/cz.gif) Shadow Hawkins on Wednesday, 09 February 2011 10:17:06
Same to me.
ping6 -c 3 ipv6.google.com
PING ipv6.google.com(2a00:1450:8007::67) 56 data bytes
--- ipv6.google.com ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 2015ms
--- tcpdump ---
tcpdump -i eth1 -n -v host simbx01.sixxs.net
10:12:14.096048 IP (tos 0x0, ttl 63, id 21378, offset 0, flags [DF], proto: UDP (17), length: 176) 195.113.146.195.50528 > 212.18.63.73.ayiya: UDP, length 148
10:12:15.099945 IP (tos 0x0, ttl 63, id 21379, offset 0, flags [DF], proto: UDP (17), length: 176) 195.113.146.195.50528 > 212.18.63.73.ayiya: UDP, length 148
10:12:16.109958 IP (tos 0x0, ttl 63, id 21380, offset 0, flags [DF], proto: UDP (17), length: 176) 195.113.146.195.50528 > 212.18.63.73.ayiya: UDP, length 148
No response :-(
Tunnel stopped working
![[hu]](/s/countries/hu.gif) Shadow Hawkins on Wednesday, 09 February 2011 10:23:28
I don't know if it's a general problem with the PoP or not, but my tunnel stopped working yesterday. I'm on the same simbx01 PoP, and cannot ping the remote end of the tunnel. It was working for years without the problem, and I did not made any changes on my Gentoo server in a week.
PING 2001:15c0:65ff:ca::1(2001:15c0:65ff:ca::1) 56 data bytes
--- 2001:15c0:65ff:ca::1 ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 2006ms
Tunnel stopped working
![[at]](/s/countries/at.gif) Shadow Hawkins on Wednesday, 09 February 2011 10:34:53
The problem seems to be at the PoPs side - using the SixXS Traceroute util (https://www.sixxs.net/tools/traceroute/), there is a 100% packet loss at the PoP IP address 2001:15c0:65ff:353::1.
Could it be that the address was changed and only old settings are available at SixXSs side? This theory comes from the fact that simbx01.sixxs.net is now resolving to 2001:15c0:ffff:7::2.
State change: resolved
The state of this ticket has been changed to resolved
Tunnel stopped working
The clock went crazy and then heartbeat tunnels fail to work. Resolved.
Tunnel stopped working
Shadow Hawkins on Wednesday, 09 February 2011 12:49:00
Resolution confirmed, everything works perfectly now! Thanks alot!
I found the following in my logs:
Feb 8 21:45:45 frost aiccu: [AYIYA-tun->tundev] [212.18.63.73]:5072 : Time is 304 seconds off for ::
Feb 8 21:45:45 frost aiccu: [AYIYA-tun->tundev] [212.18.63.73]:5072 : Time is 304 seconds off for ::
Feb 8 21:45:45 frost aiccu: [AYIYA-tun->tundev] [212.18.63.73]:5072 : Time is 303 seconds off for ::
Feb 8 21:46:22 frost aiccu: last message repeated 15 times
I have stopped aiccu, stopped ntpd and resynced clock using ntpdate, which reported that local clock changed for less than 1 msec; However it didn't come to my mind that pop's clock could have been out of sync.
Thanks alot again!
Brane
Tunnel stopped working
Shadow Hawkins on Wednesday, 09 February 2011 19:57:37
It is still not working for me, and I haven't been changing anything in weeks. Issues started last week (I believe, could be earlier).
I use SIT tunnel from 89.212.96.129. Sometimes I could ping the other end of tunnel, now even after tunnel restart there is no response from the other end.
b.
Tunnel stopped working
Please provide the details as mentioned in the "reporting problems" list. Note that the clock issue only affected dynamic (heartbeat/AYIYA) tunnels, not the static ones as these are always configured on the PoP.
Tunnel stopped working
Shadow Hawkins on Friday, 11 February 2011 01:34:08
Now it "magically" works again. I haven't done a thing, just checked it again after I just received email with "Your tunnel has been down for a week" :/
b.
Tunnel stopped working
You most likely are hit by the connection tracking issue which is described in the FAQ.
|
![[ch]](/s/countries/ch.gif)
on Wednesday, 09 February 2011 10:57:52
Posting is only allowed when you are