better netwatch

RouterOS General
1

option to set down after N fails in netwatch.

reasoning, I want to run a script to change my OSPF costs on redundant links to fail over to an alternate link if my ping times increase above a certain number, but I don’t want the script to run if there is just one or two erronious “high” pings (in this case 5ms or higher), or a single dropped packet…

a similar solution would be to have an option to track the average ping times over the last N probe attempts, and to be able to set a down status if that average increases above a pre-defined limit.

Feature request: Netwatch parameters extension
2

any update on if this is going to be included at some point?

3

You can do this with scripting at the moment. Try something like:

 :local i 0; {:do {:set i ($i + 1); :put $i; :delay 2} while (($i < 5) && ([/ping 196.22.185.221 count=1 interval=5]=0)}; :if ($i=5) do={ :log info "Gateway is down!"

This will ping an address 5 times at 5 second intervals and only if all 5 pings are unsuccessful will it run the rest of the script

Script to ping
4

Hi,

I would also suggest that netwatch would execute a script :

  • One time or
  • as many times as N or
  • until STATUS changes back to previous state.

Regards.

5

I am looking at the 3.25 netwatch and I see it is missing the settings from the ping window, where you can specify interface, routing table, src-sddress etc. all this should be available from ntewatch + more. So MikroTik dev teаm - this is my request for today :slight_smile: Good luck with making it happen.

6

Is there a way to use this script to send email when specified IP does not reply for 5 consecutive pings and then have a second email when IP does respond to 5 consecutive pings.

Using netwatch is too sensitive as I believe it changes status if a single ping is lost.

I assume we have to enable and disable scripts so that when link is down, script it is only running “Up Script” and after link is up it only runs “Down Script”.

Anyone smart enough to figure this out?