1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
|
<html>
<head>
<title>Arp moodss module.</title>
</head>
<body>
<p>This is a view of the network Address Resolution Protocol cache for the system (tested on IPv4 only).
<p>Host addresses are looked up and converted to official names when possible.
<p>Hardware addresses are decoded, with a full name (from the <i>/etc/ethers</i> file if present, read once when the application is started), or with the vendor name for the first 3 bytes (from the <i>vendor.txt</i> file in the arp module sub directory).
<br>Note: you may update the <i>vendor.txt</i> file yourself by opening it from the <a HREF="http://pax.cavebear.com/CaveBear/Ethernet/">http://pax.cavebear.com/CaveBear/Ethernet/</a> page and saving it as a text file under the <i>vendor.txt</i> name in the arp module sub directory (no editing needed).
<pre><img src="arp.gif"></pre>
<p><b>Module options:</b>
<ul>
<li>
<i>-n (--numeric)</i>
<br>display numerical addresses instead of trying to determine symbolic host or network names.
</li>
<li>
<i>-r (--remote) [user@]host</i>
<br>remote monitoring using <i>user</i> as logname on remote host <i>host</i> (rsh facilities must be properly setup). If <i>user</i> is not specified, current user is used as logname on remote host. The module title is set to <i>arp(host)</i>.
</li>
</ul>
<p><b>Examples:</b>
<pre>$ moodss arp --numeric
$ moodss -- arp -n
$ moodss arp -r jdoe@foo.bar.com
$ moodss arp --remote foo.bar.com</pre>
</body>
</html>
|
