|
decgn01 ping check failure?
![[de]](/s/countries/de.gif) Shadow Hawkins on Wednesday, 08 February 2012 19:08:44
Today i got an email telling me that my tunnel 2001:4dd0:ff00:913::2 does not reply to icmp. Could it be that the ping robot is misbehaving again?
ys Andreas
decgn01 ping check failure?
Shadow Hawkins on Wednesday, 08 February 2012 19:13:24
Seems to be misbehaving:
#traceroute 2001:4dd0:ff00:913::2
traceroute to 2001:4dd0:ff00:913::2 (2001:4dd0:ff00:913::2), 30 hops max, 80 byte packets
1 2607:f2f8:1600::1 (2607:f2f8:1600::1) 1.096 ms 1.033 ms 1.548 ms
2 (2001:504:13::1a) 1.953 ms 2.085 ms 2.079 ms
3 10gigabitethernet2-1.core1.lax1.he.net (2001:470:0:72::1) 7.674 ms 2.040 ms 2.030 ms
4 10gigabitethernet4-3.core1.nyc4.he.net (2001:470:0:10e::2) 63.046 ms 63.113 ms 62.989 ms
5 10gigabitethernet1-2.core1.lon1.he.net (2001:470:0:128::2) 141.109 ms 139.050 ms 141.176 ms
6 2001:7f8:4::20e6:1 (2001:7f8:4::20e6:1) 147.759 ms 147.398 ms 147.196 ms
7 core-sto1-vl507.netcologne.de (2001:4dd0:a2b:19:dc30::c1) 147.071 ms 147.136 ms 146.855 ms
8 core-eup2-te3-1.netcologne.de (2001:4dd0:a2b:21:dc40::1) 146.647 ms 146.189 ms 146.622 ms
9 2001:4dd0:1234:3::42 (2001:4dd0:1234:3::42) 146.479 ms 146.507 ms 146.878 ms
10 gw-2324.cgn-01.de.sixxs.net (2001:4dd0:ff00:913::1) 146.402 ms 146.516 ms 146.123 ms
11 cl-2324.cgn-01.de.sixxs.net (2001:4dd0:ff00:913::2) 186.885 ms 184.710 ms 185.222 ms
#ping6 -c 3 2001:4dd0:ff00:913::2
PING 2001:4dd0:ff00:913::2(2001:4dd0:ff00:913::2) 56 data bytes
64 bytes from 2001:4dd0:ff00:913::2: icmp_seq=1 ttl=53 time=184 ms
64 bytes from 2001:4dd0:ff00:913::2: icmp_seq=2 ttl=53 time=180 ms
64 bytes from 2001:4dd0:ff00:913::2: icmp_seq=3 ttl=53 time=182 ms
--- 2001:4dd0:ff00:913::2 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2002ms
rtt min/avg/max/mdev = 180.207/182.708/184.978/2.016 ms
decgn01 ping check failure?
#traceroute 2001:4dd0:ff00:913::2
Ping tests are performed from the PoP side of the tunnel endpoint towards the user side of the tunnel.
If replies are not received, then the tunnel is marked as down, a traceroute from a random remote side does not explain anything.
#ping6 -c 3 2001:4dd0:ff00:913::2 PING 2001:4dd0:ff00:913::2(2001:4dd0:ff00:913::2) 56 data bytes 64 bytes from 2001:4dd0:ff00:913::2: icmp_seq=1 ttl=53 time=184 ms
A latency of 183ms, that looks the random endpoint you used above.
The pinging from the PoP to the endpoint was fine all the time. The above though is not that.
Only a tcpdump on the IPv4 interface where the tunnel runs over should show that you are responding to ICMP6 Echo Requests, though then that reply can still be filtered/dropped somewhere on the IPv4 path.
decgn01 ping check failure?
Shadow Hawkins on Wednesday, 08 February 2012 20:03:39
Same here with decgn01 since 5 February. The tunnel statistics also stopped at this day.
decgn01 ping check failure?
Shadow Hawkins on Wednesday, 08 February 2012 22:33:35
I haven't got an email yet. But since 5th of February the local tunnel endpoint 2001:4dd0:ff00:c2f::2 of my AYIYA tunnel T81482 doesn't get pinged any more from the address 2001:4dd0:1234:3::42 which belongs to NetCologne GmbH (I'm using their PoP decgn01). I only get pinged by the PoP itself (address 2001:4dd0:ff00:c2f::1) once a minute (and of course my local entpoint responds to that), but these pings are not responsible for judging my tunnel as "alife". Before februay 5th I got pinged from 2001:4dd0:1234:3::42 every 90 seconds within the first 10-15 minutes of every full and half hour, and obviously only those pings cause my tunnel to be evaluated as alive, as could be seen by the immediate update of the "Last alive" tunnel status after the last ping of every pinging intervall. As a consequence in the configuration state of tunnel T81482 the line "Last alive" isn't shown any more. Moreover the graphs for latency and loss statistics stop at 5th of February.
decgn01 ping check failure?
my AYIYA tunnel T81482 doesn't get pinged any more from the address 2001:4dd0:1234:3::42
It should have never been pinged from there, it should only be pinged from the PoP side of the tunnel.
I only get pinged by the PoP itself (address 2001:4dd0:ff00:c2f::1) once a minute
That is the only correct one anything else is irrelevant.
decgn01 ping check failure?
Shadow Hawkins on Saturday, 11 February 2012 23:56:21
What you say is true since 10 February 2012, since then everything works fine again. Thank you for fixing that!
But I have several packet traces taken by Wireshark in December 2011 and January 2012, that show pings coming from my PoP every 65 seconds (now this happens every 60 seconds) and in addition those coming from 2001:4dd0:1234:3::42, that start at XX:04:36 and XX:34:36 (XX=0, 1, ..., 23) and are repeated 4 times any 95 to 97 seconds. And it was only after the last of those 5 pings at about XX:11:00 and XX:41:00 respectively that caused the "Last alive" state of my tunnel to be updated.
But okay, now that's not important any more, because things got fixed irrespective that they work different now ("Last alive" state now updated by pings coming from the PoP).
|
![[ch]](/s/countries/ch.gif)
on Saturday, 11 February 2012 13:29:21
Posting is only allowed when you are