Ticket ID: SIXXS #4715365 Ticket Status: User PoP: chzrh02 - Init7 AG (Zurich)
missing pong from PoP Endpoint
Shadow Hawkins on Monday, 16 May 2011 13:46:40
Dear SixXS team,
I currently don't get any responses to ping requests on 2001:1620:2005:4::2, i.e. the PoP endpoint of my tunnel T51157. Neither from what looks like a properly configured tunnel, nor from the outside.
aiccu test on my router succeeds until step 6, where it tries to "ping the IPv6 Remote/PoP Inner Tunnel Endpoint (2001:1620:f00:dc::1)". Ping reports:
PING 2001:1620:f00:dc::1(2001:1620:f00:dc::1) 56 data bytes
--- 2001:1620:f00:dc::1 ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 2005ms
Upon startup, aiccu correctly reports: "Successfully retrieved tunnel information for T51157" and configures the interfaces.
From a random online ping6 service, I get "No route" for the very same IP(v6).
IPv6 Ping Output:
PING 2001:1620:f00:dc::1(2001:1620:f00:dc::1) 32 data bytes
From 2001:1620:2005:4::2 icmp_seq=0 Destination unreachable: No route
From 2001:1620:2005:4::2 icmp_seq=1 Destination unreachable: No route
From 2001:1620:2005:4::2 icmp_seq=2 Destination unreachable: No route
From 2001:1620:2005:4::2 icmp_seq=3 Destination unreachable: No route
--- 2001:1620:f00:dc::1 ping statistics ---
4 packets transmitted, 0 received, +4 errors, 100% packet loss, time 3009ms
I didn't touch my router's configuration for a while (last month or so). During that period of time the tunnel stats report a reasonable ping time. So I currently suspect a failure on the side of the PoPs.
Kind Regards
Markus Wanner
State change: user
Jeroen Massar on Monday, 16 May 2011 13:55:12
The state of this ticket has been changed to user
missing pong from PoP Endpoint
Jeroen Massar on Monday, 16 May 2011 13:57:27
Maybe you want to synchronize the clock of your host?
Proper timekeeping is really important for AYIYA tunnels towork.
missing pong from PoP Endpoint
Shadow Hawkins on Monday, 16 May 2011 14:50:42
Wow, good catch, thanks. I'm using chrony to synchronize clocks. As it turned out, chrony was 'offline' and not properly activated by ip-up scripts.
Thanks for quicker-and-better-than-most-paid-services response. I'm on IPv6 again, issue resolved.
Posting is only allowed when you are logged in. |