ping suddenly stopped working

RouterOS General
1

Hi all,
I have a script through API Rest that performs pings and suddenly it has stopped working and only returns “timeout”. From the terminal it doesn’t work either but what does work perfectly is the traceroute.

The log in the rules filter indicates that there is both output and input icmp traffic at the time I perform the ping but incomprehensibly responds timeout.

I suspect that if I restart the router it will work again but it is not something that I can do whenever I want.

thank you

CCR1036-12G-4S
Routeros 7.1.3

[ROS 7 Bug?] MikroTik cannot ping to any devices until reboot.
v7.4 [stable] is released!
2

I had this happen just now..

CCR1036-12G running RouterOs 7.2.2

It could not ping anything but I could telnet to ports on the destinations..

i.e. ping 192.168.1.1 failed with timeout, but telnet 192.168.1.1 I could login to the router.

This was not just for one device it was for all devices on the network.. routers, switches, servers, etc… icmp not working but telnet/ssh/http ok to the destinations.

3

Had the same on two CCR1072 with RouterOS 7.1.5…
Support told me to update to 7.2.x… Waiting whether or not it happens again.

Anyway… Report to support please. The have to be aware this happens again and again.

4

I have raised a support ticket.. :slight_smile:

5

It’s still happening on 7.3 but now it recovers a few hours later with no intervention… so still an issue but hard to replicate and with 7.3 it lasts 4-5hours before it comes good again.

6

Looks like Mikrotik managed to reproduce this. They told me this is due to valid packets being seen as invalid and thus discarded.
Let’s hope we will see a fix soon.

7

Hope this bug will fix soon too.

On my CHR it never recovery by itself (I’ve wait for a month). Have to reboot so it can work back to normal.

8

Can’t use netwatch anymore.. T___T
1658196717278.jpg

9

I have this bug only on x86 platforms. After 36/48h i got the ping tool not working. So all the route with check-gateway=ping are disabled.
To workaround it I reboot the router each night.

Now with 7.4 there is a differnt behavior:

  • netwatch works correctly, this mean that this tool correctly identifies if an host is up (also if the regular ping tool don’t get reply due to this bug) and down, in fact blocking icmp for an host it get the host down.
  • the check-gateway=ping in route follow not the netwatch but the ping tool, so during the issue, the routes with check-gateway=ping got disabled and at the same time the netwatch report the gateway up…..

this pushes me to thing that ping tool during the issue works on a wrong vrf or socket or something like that.

I updated my ticket SUP-67221 about it.
regards
Ros

10

This should be fixed with 7.5beta8, which includes this change:

*) ping - improved service stability;