Arping can be used to find out if 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 out of luck. Or you use arping.
OS | Architecture | Version |
---|---|---|
NetBSD 10.0 | aarch64 | arping-2.21nb1.tgz |
NetBSD 10.0 | aarch64 | arping-2.21nb1.tgz |
NetBSD 10.0 | aarch64eb | arping-2.21nb1.tgz |
NetBSD 10.0 | aarch64eb | arping-2.21nb1.tgz |
NetBSD 10.0 | alpha | arping-2.21nb1.tgz |
NetBSD 10.0 | alpha | arping-2.21nb1.tgz |
NetBSD 10.0 | earmv4 | arping-2.21nb1.tgz |
NetBSD 10.0 | earmv4 | arping-2.21nb1.tgz |
NetBSD 10.0 | earmv6hf | arping-2.21nb1.tgz |
NetBSD 10.0 | earmv6hf | arping-2.21nb1.tgz |
NetBSD 10.0 | earmv6hf | arping-2.21nb1.tgz |
NetBSD 10.0 | earmv7hf | arping-2.21nb1.tgz |
NetBSD 10.0 | earmv7hf | arping-2.21nb1.tgz |
NetBSD 10.0 | earmv7hf | arping-2.21nb1.tgz |
NetBSD 10.0 | i386 | arping-2.21nb1.tgz |
NetBSD 10.0 | i386 | arping-2.21nb1.tgz |
NetBSD 10.0 | m68k | arping-2.21nb1.tgz |
NetBSD 10.0 | powerpc | arping-2.21nb1.tgz |
NetBSD 10.0 | powerpc | arping-2.21nb1.tgz |
NetBSD 10.0 | powerpc | arping-2.21nb1.tgz |
NetBSD 10.0 | sh3el | arping-2.21nb1.tgz |
NetBSD 10.0 | sparc64 | arping-2.21nb1.tgz |
NetBSD 10.0 | sparc64 | arping-2.21nb1.tgz |
NetBSD 10.0 | sparc | arping-2.21nb1.tgz |
NetBSD 10.0 | sparc | arping-2.21nb1.tgz |
NetBSD 10.0 | vax | arping-2.21nb1.tgz |
NetBSD 10.0 | vax | arping-2.21nb1.tgz |
NetBSD 10.0 | vax | arping-2.21nb1.tgz |
NetBSD 10.0 | x86_64 | arping-2.21nb1.tgz |
NetBSD 10.0 | x86_64 | arping-2.21nb1.tgz |
NetBSD 9.0 | aarch64 | arping-2.21nb1.tgz |
NetBSD 9.0 | aarch64 | arping-2.21nb1.tgz |
NetBSD 9.0 | alpha | arping-2.21nb1.tgz |
NetBSD 9.0 | alpha | arping-2.21nb1.tgz |
NetBSD 9.0 | earmv6hf | arping-2.21nb1.tgz |
NetBSD 9.0 | earmv6hf | arping-2.21nb1.tgz |
NetBSD 9.0 | earmv6hf | arping-2.21nb1.tgz |
NetBSD 9.0 | earmv7hf | arping-2.21nb1.tgz |
NetBSD 9.0 | earmv7hf | arping-2.21nb1.tgz |
NetBSD 9.0 | earmv7hf | arping-2.21nb1.tgz |
NetBSD 9.0 | i386 | arping-2.21nb1.tgz |
NetBSD 9.0 | i386 | arping-2.21nb1.tgz |
NetBSD 9.0 | m68k | arping-2.21nb1.tgz |
NetBSD 9.0 | powerpc | arping-2.21nb1.tgz |
NetBSD 9.0 | powerpc | arping-2.21nb1.tgz |
NetBSD 9.0 | powerpc | arping-2.21nb1.tgz |
NetBSD 9.0 | sparc64 | arping-2.21nb1.tgz |
NetBSD 9.0 | sparc64 | arping-2.21nb1.tgz |
NetBSD 9.0 | x86_64 | arping-2.21nb1.tgz |
NetBSD 9.0 | x86_64 | arping-2.21nb1.tgz |
NetBSD 9.3 | x86_64 | arping-2.21nb1.tgz |
Binary packages can be installed with the high-level tool pkgin (which can be installed with pkg_add) or pkg_add(1) (installed by default). The NetBSD packages collection is also designed to permit easy installation from source.
The pkg_admin audit command locates any installed package which has been mentioned in security advisories as having vulnerabilities.
Please note the vulnerabilities database might not be fully accurate, and not every bug is exploitable with every configuration.
Problem reports, updates or suggestions for this package should be reported with send-pr.