--------------------------
Explicit ChangeLog not found, but diff between source may say
following changes.
2.17
----
usage: arping [ -0aAbdDeFpPqrRuUv ] [ -w <us> ]
-w Time to wait between pings, in microseconds.
-W Same as -w, but in floating point seconds.
2.18
----
usage: arping [ -0aAbdDeFpPqrRuUv ] [ -w <sec> ]
-w sec Specify a timeout before ping exits regardless of how many
packets have been sent or received.
-W sec Time to wait between pings.
--------------------------
Explicit ChangeLog is not known, but diff shows following lines
+ // Padding size chosen fairly arbitrarily.
+ // Without this padding some systems (e.g. Raspberry Pi 3
+ // wireless interface) failed. dmesg said:
+ // arping: packet size is too short (42 <= 50)
+ const char padding[16] = {0};
--------------
Explicit ChangeLog not found, but diff src tells two options are
added, -Q and -V, ( -V vlan -Q priority )
-Q pri 802.1p priority to set. Should be used with 802.1Q (-V).
Defaults to 0.
-V num 802.1Q tag to add. Defaults to no VLAN tag.
--------------
Explicit ChangeLog not found, but looking into the source, the option -m is added.
------------
+ " -m type"
+#ifndef HAVE_PCAP_LIST_TSTAMP_TYPES
+ " (Disabled on this system. Option ignored)"
+#endif
+ "\n Type of timestamp to use for incoming packets. Use -vv when\n"
+ " pinging to list available ones.\n"
- "[ -C <count> ] [ -i <interface> ] "
+ "[ -C <count> ] [ -i <interface> ] [ -m <type> ] "
worked. But somehow, today it didn't work anymore.
Fixed everything by removing the patch for the Makefile and doing the
whole build command in the package Makefile.
Fixes PR 35786.
Quentin Garnier.
Arping can be used to find out it a specific IP address on the LAN is 'taken'
and what MAC address owns it. Sure, you *could* just use 'ping' to find out if
it's taken and even if the computer blocks ping (and everything else) you still
get an entry in your ARP cache. But what if you aren't on a routable net? Or
the host blocks ping (all ICMP even)? Then you're screwed. Or you use arping.
