On wireless links it is really a problem to get notification when link becomes bad. The problem is that link sometimes becomes bad long before becoming down. It still works, packets are not lost, but speed is terrible, pings are 20-50ms on ptp link.
We need to get notification (email is ok) when it happens. The netwatch tool can't help here as packets are not lost, they are still transmitted, but too slow to make client happy. Various stats from wireless interface seems to be too variable to make some thresholds.
It seems to me that the only reliable thing that can help to identify this problem is when average ping for about 2-3 minutes is bigger than some predefined value for this link. Usually the problem is when ping becomes between 10-20ms on ptp links. This makes dude's ping useles, as it's time resolutions seems to be 10ms. So all pings in dude are 0, 10, 20, ... ms, which makes it useless for averaging.
So, the question is: is there a way to get actual ping times (or any other round-trip-times) somehow between 2 miktorik routers via script or dude or in any other way (snmp?), than can be collected, averaged & compared to some threshold?
Netwatch can do all you want.
add comment="" disabled=no down-script="" host=10.50.51.1 interval=1m timeout=1s up-script=""
add comment="" disabled=no down-script="" host=10.50.51.1 interval=1m timeout=500ms up-script=""
add comment="" disabled=no down-script="" host=10.50.51.1 interval=1m timeout=50ms up-script=""
add comment="" disabled=no down-script="" host=10.50.51.1 interval=1m timeout=5ms up-script=""
You can set the interval, you can set the timeout and you can make any script you want.
Now you have to decide when you consider a link to be down, bad, poor, moderate or fast.
Show your appreciation of this post by giving me Karma! Thanks.
Rudy R. Puister
WISP operator based on MT routerboard & ROS.