[ROS 7 Bug?] MikroTik cannot ping to any devices until reboot.

I’ve face this issue on MikroTik CHR and CCR1072 with ROS 7.1.3, ROS 7.2, ROS 7.3.1.

When MikroTik has been using for a while (sometimes days, sometimes months) it will cannot ping to any devices (still can traceroute) so netwatch will malfunction but other modules are working fine.

Any solution to fix this? on CCR1072, I use schedule restart everyday and the problem do not happen again.
but on CHR, I use it as a production for 24x7 systems. Cannot just schedule restart. Everytime I want to reboot, I have to write a formal letter to notice several departments.
1657428070085.jpg

if you have connection tracking active check in ip->firewall->connections all the details of the ping connection which is not responding

1657428070085.jpg
Orig. and Repl. Bytes are increasing along the time I’ve ping. But status of ping is still timeout.
try remove those connections already. result still the same.

Maybe you can try upgrade to the latest stable version, or maybe better (when your usage allows it) downgrade to 6.49.6 ?

I think so. downgrade would help.
but can I use wireguard with ROS 6 ?
If ROS 6 had wireguard, I definitely wouldn’t use ROS 7 on my CHR.

(now 7.3.1 is the lastest stable version)

I guess this is the same issue:
http://forum.mikrotik.com/t/ping-suddenly-stopped-working/157534/1

I am suffering the same, it is tracked in SUP-83146, Mikrotik reproduced it but a fix is pending.

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

*) ping - improved service stability;