screwy timing in arping (v1.7.2 avr32)

[Denys Vlasenko]

On Monday 17 December 2007 23:28, Clem Taylor wrote:
> The timing in arping from busybox 1.7.2 doesn't seem to be counting
> correctly. Could someone else running 1.7.2 check if they are seeing
> the same problem?
>
>                                   --Clem
>
> busybox 1.7.2 (avr32)
> $ arping -f -c 10 -w 1 -I eth1 10.42.0.10
> ARPING to 10.42.0.10 from 0.42.0.10 via eth1
> Unicast reply from 10.42.0.10 [0:18:8:0:0:6b] 2493806.359ms
> Sent 1 probe(s) (1 broadcast(s))
> Received 1 replies (0 request(s), 0 broadcast(s))
> [took 0.03s]
>
> busybox 1.5.0 (mips)
> $ arping -f -c 10 -w 1 -i eth0 192.168.50.80
> ARPING to 92.168.50.241 from 192.168.50.241 via eth0
> Unicast reply from 192.168.50.80 [0:4:25:1c:71:2c] 1.624ms
> Sent 1 probe(s) (1 broadcast(s))
> Received 1 replies (0 request(s), 0 broadcast(s))
> [took 0.02s]

Yes, you're right, this is a bug. Try:

http://busybox.net/downloads/fixes-1.8.2/busybox-1.8.2-arping.patch
--
vda