summaryrefslogtreecommitdiff
path: root/net/arping/DESCR
diff options
context:
space:
mode:
authorxtraeme <xtraeme@pkgsrc.org>2004-07-07 17:30:12 +0000
committerxtraeme <xtraeme@pkgsrc.org>2004-07-07 17:30:12 +0000
commit15a909427cb1c88dfe1571347a451aaf61eefb5b (patch)
treed4d19e41fabea9911bfbe65808462b4bb7ffbfc2 /net/arping/DESCR
parentd3d73f6357e96b1509c0bf17c8e531544e36da96 (diff)
downloadpkgsrc-15a909427cb1c88dfe1571347a451aaf61eefb5b.tar.gz
Initial import of arping-2.01 from pkgsrc-wip, contributed by
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.
Diffstat (limited to 'net/arping/DESCR')
-rw-r--r--net/arping/DESCR5
1 files changed, 5 insertions, 0 deletions
diff --git a/net/arping/DESCR b/net/arping/DESCR
new file mode 100644
index 00000000000..21e77b3384d
--- /dev/null
+++ b/net/arping/DESCR
@@ -0,0 +1,5 @@
+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.