Thank you for your replay.
Version 2.14 solved the above problem.
But now I have new issue. Look at replay delay:
./arping 192.168.10.120 -c 5
ARPING 192.168.10.120
60 bytes from 00:30:4f:61:4e:13 (192.168.10.120): index=0 time=130.299 msec
60 bytes from 00:30:4f:61:4e:13 (192.168.10.120): index=1 time=129.696 msec
60 bytes from 00:30:4f:61:4e:13 (192.168.10.120): index=2 time=129.545 msec
60 bytes from 00:30:4f:61:4e:13 (192.168.10.120): index=3 time=224.335 msec
60 bytes from 00:30:4f:61:4e:13 (192.168.10.120): index=4 time=465.971 msec
and now output by arping (from iputils-arping package) on the same station:
arping -I eth0 -c 5 192.168.10.120
ARPING 192.168.10.120 from 192.168.10.131 eth0
Unicast reply from 192.168.10.120 [00:30:4F:61:4E:13] 0.553ms
Unicast reply from 192.168.10.120 [00:30:4F:61:4E:13] 0.598ms
Unicast reply from 192.168.10.120 [00:30:4F:61:4E:13] 0.598ms
Unicast reply from 192.168.10.120 [00:30:4F:61:4E:13] 0.556ms
Unicast reply from 192.168.10.120 [00:30:4F:61:4E:13] 0.555ms
Why so big difference in reply delay?
Output from arping (iputils-arping) looks like more accurate about delay value.
2014-12-03 13:16 GMT+04:00 Thomas Habets <email address hidden>:
> This is probably the known issue that was fixed in upstream in Aug 2012,
> over two years ago.
>
> Try again with arping-2.13 or later.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1398467
>
> Title:
> 14.04, arping, time to wait option
>
> Status in arping package in Ubuntu:
> New
>
> Bug description:
> Ubuntu 14.04.1 LTS
>
> arping from 'arping' package(not iputils-arping) version 2.11
>
>
> example shows the problem:
>
>
> # arping 192.168.10.120 -c 10 -w 100000
> ARPING 192.168.10.120
>
> --- 192.168.10.120 statistics ---
> 10 packets transmitted, 0 packets received, 100% unanswered (0 extra)
>
>
> so, 100% loss.
>
> The same syntax is working with Ubuntu 12.04.1 LTS and arping version
> 2.09.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/arping/+bug/1398467/+subscriptions
Hello,
Thank you for your replay.
Version 2.14 solved the above problem.
But now I have new issue. Look at replay delay:
./arping 192.168.10.120 -c 5
ARPING 192.168.10.120
60 bytes from 00:30:4f:61:4e:13 (192.168.10.120): index=0 time=130.299 msec
60 bytes from 00:30:4f:61:4e:13 (192.168.10.120): index=1 time=129.696 msec
60 bytes from 00:30:4f:61:4e:13 (192.168.10.120): index=2 time=129.545 msec
60 bytes from 00:30:4f:61:4e:13 (192.168.10.120): index=3 time=224.335 msec
60 bytes from 00:30:4f:61:4e:13 (192.168.10.120): index=4 time=465.971 msec
and now output by arping (from iputils-arping package) on the same station:
arping -I eth0 -c 5 192.168.10.120
ARPING 192.168.10.120 from 192.168.10.131 eth0
Unicast reply from 192.168.10.120 [00:30:4F:61:4E:13] 0.553ms
Unicast reply from 192.168.10.120 [00:30:4F:61:4E:13] 0.598ms
Unicast reply from 192.168.10.120 [00:30:4F:61:4E:13] 0.598ms
Unicast reply from 192.168.10.120 [00:30:4F:61:4E:13] 0.556ms
Unicast reply from 192.168.10.120 [00:30:4F:61:4E:13] 0.555ms
Why so big difference in reply delay?
Output from arping (iputils-arping) looks like more accurate about delay value.
2014-12-03 13:16 GMT+04:00 Thomas Habets <email address hidden>: /bugs.launchpad .net/bugs/ 1398467 /bugs.launchpad .net/ubuntu/ +source/ arping/ +bug/1398467/ +subscriptions
> This is probably the known issue that was fixed in upstream in Aug 2012,
> over two years ago.
>
> Try again with arping-2.13 or later.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> 14.04, arping, time to wait option
>
> Status in arping package in Ubuntu:
> New
>
> Bug description:
> Ubuntu 14.04.1 LTS
>
> arping from 'arping' package(not iputils-arping) version 2.11
>
>
> example shows the problem:
>
>
> # arping 192.168.10.120 -c 10 -w 100000
> ARPING 192.168.10.120
>
> --- 192.168.10.120 statistics ---
> 10 packets transmitted, 0 packets received, 100% unanswered (0 extra)
>
>
> so, 100% loss.
>
> The same syntax is working with Ubuntu 12.04.1 LTS and arping version
> 2.09.
>
> To manage notifications about this bug go to:
> https:/