Hello folks,
I am noticing weird behavior from arping command.
There is a periodic lag in response.
Whereas there is no such lag in ping response to the same host.
The connection is wired.
Given that arping is guaranteed to work [doesn't get blocked by device firewalls] and not ping, this is a bit troubling if I am to rely on it's response time.
Is this a known behaviour and can I do something about it?
ARPING 192.168.0.3 from 192.168.0.1 br-lan
Unicast reply from 192.168.0.3 [9C:A2:F4:FE:6D:66] 1.180ms
Unicast reply from 192.168.0.3 [9C:A2:F4:FE:6D:66] 1.184ms
Unicast reply from 192.168.0.3 [9C:A2:F4:FE:6D:66] 1.210ms
Unicast reply from 192.168.0.3 [9C:A2:F4:FE:6D:66] 382.890ms
Unicast reply from 192.168.0.3 [9C:A2:F4:FE:6D:66] 1.589ms
Unicast reply from 192.168.0.3 [9C:A2:F4:FE:6D:66] 1.120ms
Unicast reply from 192.168.0.3 [9C:A2:F4:FE:6D:66] 1.219ms
Unicast reply from 192.168.0.3 [9C:A2:F4:FE:6D:66] 1.666ms
Unicast reply from 192.168.0.3 [9C:A2:F4:FE:6D:66] 1.126ms
Unicast reply from 192.168.0.3 [9C:A2:F4:FE:6D:66] 1.208ms
Unicast reply from 192.168.0.3 [9C:A2:F4:FE:6D:66] 1.065ms
Unicast reply from 192.168.0.3 [9C:A2:F4:FE:6D:66] 1.320ms
Unicast reply from 192.168.0.3 [9C:A2:F4:FE:6D:66] 1.447ms
Unicast reply from 192.168.0.3 [9C:A2:F4:FE:6D:66] 1.001ms
Unicast reply from 192.168.0.3 [9C:A2:F4:FE:6D:66] 1.951ms
Unicast reply from 192.168.0.3 [9C:A2:F4:FE:6D:66] 420.737ms
Unicast reply from 192.168.0.3 [9C:A2:F4:FE:6D:66] 1.236ms
Unicast reply from 192.168.0.3 [9C:A2:F4:FE:6D:66] 1.866ms
Unicast reply from 192.168.0.3 [9C:A2:F4:FE:6D:66] 1.627ms
Unicast reply from 192.168.0.3 [9C:A2:F4:FE:6D:66] 1.848ms
Unicast reply from 192.168.0.3 [9C:A2:F4:FE:6D:66] 1.314ms
Unicast reply from 192.168.0.3 [9C:A2:F4:FE:6D:66] 1.140ms
Unicast reply from 192.168.0.3 [9C:A2:F4:FE:6D:66] 1.804ms
Unicast reply from 192.168.0.3 [9C:A2:F4:FE:6D:66] 1.240ms
Unicast reply from 192.168.0.3 [9C:A2:F4:FE:6D:66] 1.198ms
Unicast reply from 192.168.0.3 [9C:A2:F4:FE:6D:66] 1.286ms
Unicast reply from 192.168.0.3 [9C:A2:F4:FE:6D:66] 1.356ms
Unicast reply from 192.168.0.3 [9C:A2:F4:FE:6D:66] 445.354ms
PING 192.168.0.3 (192.168.0.3): 56 data bytes
64 bytes from 192.168.0.3: seq=1 ttl=64 time=1.200 ms
64 bytes from 192.168.0.3: seq=2 ttl=64 time=0.976 ms
64 bytes from 192.168.0.3: seq=3 ttl=64 time=0.841 ms
64 bytes from 192.168.0.3: seq=4 ttl=64 time=0.967 ms
64 bytes from 192.168.0.3: seq=5 ttl=64 time=1.372 ms
64 bytes from 192.168.0.3: seq=6 ttl=64 time=1.004 ms
64 bytes from 192.168.0.3: seq=7 ttl=64 time=0.880 ms
64 bytes from 192.168.0.3: seq=8 ttl=64 time=1.042 ms
64 bytes from 192.168.0.3: seq=9 ttl=64 time=0.683 ms
64 bytes from 192.168.0.3: seq=10 ttl=64 time=0.972 ms
64 bytes from 192.168.0.3: seq=11 ttl=64 time=1.105 ms
64 bytes from 192.168.0.3: seq=12 ttl=64 time=0.998 ms
64 bytes from 192.168.0.3: seq=13 ttl=64 time=1.109 ms
64 bytes from 192.168.0.3: seq=14 ttl=64 time=1.033 ms
64 bytes from 192.168.0.3: seq=15 ttl=64 time=1.397 ms
64 bytes from 192.168.0.3: seq=16 ttl=64 time=1.207 ms
64 bytes from 192.168.0.3: seq=17 ttl=64 time=0.845 ms
64 bytes from 192.168.0.3: seq=18 ttl=64 time=0.726 ms
64 bytes from 192.168.0.3: seq=19 ttl=64 time=1.343 ms
64 bytes from 192.168.0.3: seq=20 ttl=64 time=1.470 ms
64 bytes from 192.168.0.3: seq=21 ttl=64 time=1.169 ms
64 bytes from 192.168.0.3: seq=22 ttl=64 time=1.135 ms
64 bytes from 192.168.0.3: seq=23 ttl=64 time=0.980 ms
64 bytes from 192.168.0.3: seq=24 ttl=64 time=0.998 ms
64 bytes from 192.168.0.3: seq=25 ttl=64 time=1.162 ms
64 bytes from 192.168.0.3: seq=26 ttl=64 time=0.874 ms