|
Ticket ID: SIXXS #5617834 Ticket Status: User PoP: chzrh02 - Init7 AG (Zurich)
Ping robot reports my tunnel down, but it is up
![[ch]](/s/countries/ch.gif) Shadow Hawkins on Saturday, 24 September 2011 08:06:52
Last weekend the POP chzrh02 was down from Sat 06:00 to Mon 15:00
Then it was again down from on the 22nd.
Now I get an email telling my tunnel was last pingable the 19th Sep. This is not true. As you can see in the traffic statistics, there was constant traffic on the tunnel.
Please verify the ping check.
Tunnel is T47137
State change: user
The state of this ticket has been changed to user
Ping robot reports my tunnel down, but it is up
Traffic != Ping.
Please actually read the FAQ, there can be various reasons why your endpoint does not properly ping.
Ping robot reports my tunnel down, but it is up
Shadow Hawkins on Sunday, 25 September 2011 10:17:21
I can ping everything from my side. Both tunnel endpoints. There was no change in my environment for the last 2 month.
I restate: since the 19th Sat since the POP went down it is not possible for the ping check to ping my tunnel endpoint.
Traceroute also shows strange behavior:
If I check the POP side:
root@argus:~# traceroute6 -n 2001:1620:f00:c5::1
traceroute to 2001:1620:f00:c5::1 (2001:1620:f00:c5::1), 30 hops max, 80 byte packets
1 2001:1620:2053:2::10 0.422 ms 0.279 ms 0.282 ms
2 2001:1620:2053:1::5 1.056 ms 0.945 ms 0.889 ms
3 2001:1620:2053::1 0.925 ms 0.930 ms 1.038 ms
4 2001:1620:e::1 4.463 ms 4.301 ms 4.247 ms
5 2001:1620:f00:c5::1 3.231 ms 3.178 ms 3.075 ms
If I check my side:
root@argus:~# traceroute6 -n 2001:1620:f00:c5::2
traceroute to 2001:1620:f00:c5::2 (2001:1620:f00:c5::2), 30 hops max, 80 byte packets
1 2001:1620:2053:2::10 0.407 ms 0.353 ms 0.272 ms
2 2001:1620:2053:1::5 0.874 ms 0.858 ms 0.800 ms
3 2001:1620:2053::1 0.885 ms 0.852 ms 0.862 ms
4 2001:1620:e::2 3.158 ms 2.999 ms 2.958 ms
5 2001:1620:2::e 4.360 ms 2001:1620:2::a5 3.264 ms 3.209 ms
6 2001:1620:2::ea 4.930 ms 2001:1620:2::15 10.700 ms 2001:1620:2::ea 4.331 ms
7 2001:1620:2::e6 4.319 ms 4.159 ms 2001:1620:2::c6 3.310 ms
8 2001:1620:2::c9 3.199 ms 3.233 ms 3.226 ms
9 2001:1620:2::29 4.344 ms 4.269 ms 2001:1620:2::4a 3.287 ms
10 2001:1620:2005:4:216:3eff:fe71:e1f3 3.447 ms 4.290 ms 3.375 ms
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
Ping robot reports my tunnel down, but it is up
I can ping everything from my side. Both tunnel endpoints. There was no change in my environment for the last 2 month.
The internet changes, if you like it or not.
Maybe you have connection tracking (see the FAQ) causing issues?
Are you routing packets outbound over the proper paths?
I restate: since the 19th Sat since the POP went down it is not possible for the ping check to ping my tunnel endpoint.
The PoP is pinging quite fine to the rest of the world: chzrh02 latency/loss
root@argus:~# traceroute6 -n 2001:1620:f00:c5::1 traceroute to 2001:1620:f00:c5::1 (2001:1620:f00:c5::1), 30 hops max, 80 byte packets 1 2001:1620:2053:2::10 0.422 ms 0.279 ms 0.282 ms
What is this 'argus' host and what is it's source address?
Where is the running configuration of the host/router that terminates the tunnel? Where are the traceroutes from that host?
Your traceroutes only confirm that your endpoint is not responding to ICMP.
Checking a v4 traceroute:
traceroute to 62.65.142.151 (62.65.142.151), 30 hops max, 40 byte packets
1 r1zlz1.core.init7.net (213.144.148.73) 0.000 ms 0.000 ms 0.000 ms
2 r1zba1.core.init7.net (77.109.128.230) 0.000 ms 0.000 ms 0.000 ms
3 r1zur2.core.init7.net (77.109.128.205) 0.000 ms 0.000 ms 0.000 ms
4 91.206.52.123 (91.206.52.123) 0.000 ms 0.000 ms 0.000 ms
5 core0.ge-0-2-0.intx.ch.netstream.com (62.65.130.150) 0.000 ms 4.000 ms 4.000 ms
6 core0.ge-0-3-0.nshq.ch.netstream.com (62.65.128.129) 0.000 ms 4.000 ms 4.000 ms
7 lns0.ge-0-1-0.nshq.ch.netstream.com (62.65.128.147) 4.000 ms 4.000 ms 4.000 ms
8 * * *
9 * * *
Nothing coming back from that either. Pings don't get responses either.
Packets are being sent (times in UTC)
08:47:09.287000 IP 213.144.148.74 > 62.65.142.151: IP6 2a01:4f8:130:74c1:5054:ff:fe61:9910 > 2001:1620:f00:c5::2: ICMP6, echo request, seq 163, length 64
...
08:47:42.287000 IP 213.144.148.74 > 62.65.142.151: IP6 2a01:4f8:130:74c1:5054:ff:fe61:9910 > 2001:1620:f00:c5::2: ICMP6, echo request, seq 196, length 64
But not even an ICMP is returned.
Sorry, nothing that we can work with or do about.
Ping robot reports my tunnel down, but it is up
Shadow Hawkins on Sunday, 25 September 2011 13:12:14
Thanks for your help. I finally found the problem.
I had to limit administrative access to the firewall also for IPv6. This also restricts ping to the limited IP address range even if ping is enabled on the interface.
Ping robot reports my tunnel down, but it is up
Strange that you then claimed "There was no change in my environment for the last 2 month"...
But it works again, good.
|
on Saturday, 24 September 2011 10:15:08
Posting is only allowed when you are