From wikistone
(Created page with "==arping== Use arping to get L2 and L3 responses.<br> Some files here: http://www.habets.pp.se/synscan/files/ .<br> ==use== Send ARP request: <pre> # arping -I enp4s0 -c 2 1...") |
(→use) |
||
| Line 9: | Line 9: | ||
# arping -I enp4s0 -c 2 10.0.0.1 | # arping -I enp4s0 -c 2 10.0.0.1 | ||
ARPING 10.0.0.1 from 10.0.0.42 enp4s0 | ARPING 10.0.0.1 from 10.0.0.42 enp4s0 | ||
| − | Unicast reply from 10.0.0.1 [ | + | Unicast reply from 10.0.0.1 [AA:BB:CC:DD:EE:FF] 1.199ms |
| − | Unicast reply from 10.0.0.1 [ | + | Unicast reply from 10.0.0.1 [AA:BB:CC:DD:EE:FF] 1.045ms |
Sent 2 probes (1 broadcast(s)) | Sent 2 probes (1 broadcast(s)) | ||
Received 2 response(s) | Received 2 response(s) | ||
Revision as of 14:47, 11 January 2014
arping
Use arping to get L2 and L3 responses.
Some files here: http://www.habets.pp.se/synscan/files/ .
use
Send ARP request:
# arping -I enp4s0 -c 2 10.0.0.1 ARPING 10.0.0.1 from 10.0.0.42 enp4s0 Unicast reply from 10.0.0.1 [AA:BB:CC:DD:EE:FF] 1.199ms Unicast reply from 10.0.0.1 [AA:BB:CC:DD:EE:FF] 1.045ms Sent 2 probes (1 broadcast(s)) Received 2 response(s)
Dup IP check:
# arping -D -I enp4s0 -c 3 10.0.0.1 ARPING 10.0.0.1 from 0.0.0.0 enp4s0 Unicast reply from 10.0.0.1 [AA:BB:CC:DD:EE:FF] 0.888ms Sent 1 probes (1 broadcast(s)) Received 1 response(s)
man page
arping(8)
NAME
arping - send ARP REQUEST to a neighbour host
SYNOPSIS
arping [-AbDfhqUV] [-c count] [-w deadline] [-s source] {-I interface} {destination}
DESCRIPTION
Ping destination on device interface by ARP packets, using source address source.
OPTIONS
-A The same as -U, but ARP REPLY packets used instead of ARP REQUEST.
-b Send only MAC level broadcasts. Normally arping starts from sending broadcast, and switch to unicast after reply received.
Stop after sending count ARP REQUEST
packets. With deadline [arping(8)] option, arping waits for count ARP REPLY packets, until the timeout expires.
-D Duplicate address detection mode (DAD). See RFC2131, 4.4.1 ⟨http://tools.ietf.org/rfc/rfc2131.txt⟩ . Returns 0, if DAD succeeded i.e. no replies are received
-f Finish after the first reply confirming that target is alive.
Name of network device where to send ARP REQUEST packets.
-h Print help page and exit.
-q Quiet output. Nothing is displayed.
IP source address to use in ARP packets.
If this option is absent, source address is:
· In DAD mode (with option -D) set to 0.0.0.0.
· In Unsolicited ARP mode (with options -U or -A) set to destination.
· Otherwise, it is calculated from routing tables.
-U Unsolicited ARP mode to update neighbours' ARP caches. No replies are expected.
-V Print version of the program and exit.
Specify a timeout, in seconds, before
arping exits regardless of how many packets have been sent or received. In this case arping does not stop after count [arping(8)] packet are sent,
it waits either for deadline [arping(8)] expire or until count [arping(8)] probes are answered.
SEE ALSO
ping(8)[Cross reference to non-existant ID “ping”], clockdiff(8)[Cross reference to non-existant ID “clockdiff”], tracepath(8)[Cross reference to non-existant ID “tracepath”].
AUTHOR
arping was written by Alexey Kuznetsov kuznet@ms2.inr.ac.ru ⟨mailto:kuznet@ms2.inr.ac.ru⟩ . It is now maintained by YOSHIFUJI Hideaki yoshfuji@skbuff.net ⟨mailto:yoshfuji@skbuff.net⟩ .
SECURITY
arping requires CAP_NET_RAW capability to be executed. It is not recommended to be used as set-uid root, because it allows user to modify ARP caches of neighbour hosts.
AVAILABILITY
arping is part of iputils package and the latest versions are available in source form at ⟨http://www.skbuff.net/iputils/iputils-current.tar.bz2⟩.
iputils- 13 August 2013 arping(8)