Netwatch is nice, but if it misses only a single ping it declares the host down, and executes the "on down" action.
When the next ping is replied, it executes the "on up" action.
Result: when there is slight packet loss, the actions are firing way too often.

Request: implement a settable parameter that defines the number of pings before the system is declared down (default 1).
Only when that number of consecutive pings are all not replied the action is taken. Any reply restores the host back to up
without action.

This should make netwatch much more usable. I see people writing scripts to work around this limitation.

Another suggestion is implement what routing-table will be used directaly when create a new netwatch.