It appears that the history reading of the Ping Probe is not accurate. I have installed a local Mikrotik router connected directly to the dude server. I am using the dude 4.0 by the way. I open a command prompt and can ping the router from the dude server (windows) with less than 1ms steady. However when I look at the history of pings in the dude I see it spiking to 17ms every 15 minutes or so. I have another mikrotik router on a wireless link at another location. When I open a command prompt and ping the router it averages about 4ms… and sometimes spikes to 15ms or so… where as if I look in the history graph in the dude.. it shows average about 16ms and spikes to 60ms… Am I missing something here? The dude history of pings seems to be 4 times higher than it actually is. Thanks!
There has been no official response to this issue, you can find posts from me showing how crazy pings in the dude can be. Because of this I do not use ping for anything other than up or down. Also if you notice a device with a high ping and manually re-probe it the ping will re-settle to something more appropriate.
Since this is somewhat interesting I will add… The dude seems to use the previously graphed value as the next graphed value as if the “cache” is not being cleared between probes. i.e. I will see long time of pings at one value then it will change to another value for another long time, like 10 hours of pings being 120ms and then 4 days of pings being 50ms. And a reprobe will cause it to graph a “reasonable” value for a while but not for very long.
Anyhow we are stuck waiting to see if they fix the issue in the next version…
Lebowski