ping 192.168.34.1 size=1500 interval=00:00:05
worked
ping 192.168.34.1 size=1500 interval=00:00:00.2
do not worked
ping 192.168.34.1 size=1500 interval=00:00:05
worked
ping 192.168.34.1 size=1500 interval=00:00:00.2
do not worked
How is that a bug?
what?
you cannot set any lower time frame as 1 second in normal ping command.
if you need more pings sent - just use /tool flood-ping
Sorry for my simple expression. Ill try to explain what i have found.
Try write into RouterOs console:
[admin@GateWay] > ping 192.168.52.1 interval=05
You will receive this in 5second interval:
192.168.52.1 64 byte ping: ttl=63 time<1 ms
192.168.52.1 64 byte ping: ttl=63 time<1 ms
192.168.52.1 64 byte ping: ttl=63 time<1 ms
192.168.52.1 64 byte ping: ttl=63 time<1 ms
192.168.52.1 64 byte ping: ttl=63 time<1 ms
And than try to write into console this:
[admin@GateWay] > ping 192.168.52.1 interval=10
You will receive this message:
value of interval is out of range (00:00:00.010 .. 00:00:05)
Try to write into console this:
[admin@GateWay] > ping 192.168.52.1 interval=00:00:00.010
or only
[admin@GateWay] > ping 192.168.52.1 interval=0.010
You will receive this response:
invalid time value for argument interval
I think some think is wrong…
In winbox, you are able to do this. In console you are not.
00:00:00.010 is 10ms
you have to write
/ping 192.168.52.1 interval=10ms
And this is from manual:
interval (time: 10ms..5s; default: 1s) - delay between messages
so it is working as it should.
Ok THX for explaining.
But than it should be written this message by RouterOS:
value of interval is out of range 10ms .. 5s)
instead of this message:
value of interval is out of range (00:00:00.010 .. 00:00:05)