Bug 7.5 netwatch timeout value

Hello
In 6.x the timeout value could be set below 1s. After a 7.5 upgrade the value is still 0.10 for example but value is red in winbox and you can not change it to something else <1.00.
For example 1.50 works but 0.50 gives “Error in Timeout - Fixed point decimal expected!”.

It is a pure GUI bug, setting timeout <1s from CLI works fine

And not sure the packet interval value works as expected either? With 1s intervall and 0.10s packet interval you get 10 sent/response count in status.
If I change packet interval to 0.2s I would expect the sent/response count to be 5 then? But it is still 10. And no matter what I change packet interval to? What seems to change is the test interval, 1,50s packet interval gives a test interval of about 15s since sent/response count is still 10 even when interval is set to 1s.
I figure packet count seems to be fixed to 10 even when it is not set when you might expect it to only do as many as it can in the set interval then?

Issue seems fixed in 7.6rc :slight_smile:
*) winbox - allow “timeout” value to be less than 1 under “Tools/Netwatch” menu;

Packet count behaviour when not set is still the same (locked at 10).

We are evaluating some changes to packet-count in case packet-count x packet-interval would be larger than the interval value. Though nothing is decided for sure at this moment.