Little changes

In my recent attempts to venture into ROS 5.4 software made me ask for some feature additions:

  1. Netwatch tool should have interface binding feature, so it is possible to mark over what interface the tested network address should be pingable;
  2. Netwatch tool should have TTL option;
  3. In IP route “Check Gateway” by ping checking should be able settable to apply only to that single route and not to bring down any other route associated to that gateway;
  4. IP DHCP-Client should have “Check Gateway” option;
  5. Netwatch should have option to trigger host status change depending the state over numerous pings (currently it is set to 3, but it is still bit short - maybe add an option to change that default 3 times pinging?).

All these features just advance existing ones a bit and should not break any current functionality.

As Netwatch status change is being triggered by just simply one ping getting lost, it will render that tool pretty much useless for real world usage. It should be possible to monitor a host over number of ping results and then the host status will get determined by some set percent of those ping results. That will allow some dropped pings here and there without too hasty judgement as host being down.

I think a delay option would be more useful. Define a delay in seconds. When status of the test changes (ping drops) the status of the netwatch tracker stays the same until the test has stayed at the new status for the duration of the delay.
Mostly like IP SLA trackers in IOS.

I like your proposed solution. How can we make the MikroTik accept it and get them to implement it?

Hope like hell they read this, or email support@mikrotik.com.

> tool  netwatch add 
comment  copy-from  disabled  down-script  host  interval  timeout  up-script

from here you can set:
timeout value is also interval between ICMP packets being sent.
interval is time between checks.

timeout by default is 1s and interval is 1m.

netwatch changes status from up to down only if all 3 ICMP packets fail.

check gateway=icmp checks next-hop address of the route and pings that address

all of this is in manual at wiki.mikrotik.com

we will consider about src-address for netwatch tool. In the mean time use the scripting and ping to check something this specific.

@ Janisk,
Any update on src ping for Netwatch?

no, you have to use IPv6 global addresses to monitor host via netwatch.