The bug this page is about is fixed in arping-2.13, and Ubuntu should
update to at least that version.
The delay issue is now fixed in upstream and will be part of
arping-2.15. It was not a bug in libpcap, but an API change that meant
buffering delays were introduced by default.
--
You received
That's a completely different issue and is actually a regression in
libpcap somewhere between 1.3 and 1.6.2. I have a TODO to investigate
if this is a known issue, or if I can just send a patch.
iputils-arping, if I remember correctly, doesn't use libpcap but
instead Linux-specific API calls, whic
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)
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 a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1398467
Title:
14.04,
