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
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
|
<html>
<head>
<title>Netdev moodss module</title>
</head>
<body>
<p>This is a view of network devices statistics for Linux.
<br><i><b>Note</b>: for FreeBSD, the Linux compatibiliy <b>proc</b> filesystem must be available in <b>/compat/linux/proc</b> (see <b>--proc</b> option below).</i>
<p>Data is displayed in two sets of two tables: 2 for data received by the interface with absolute and per second values, the others for data transmitted by the interface, again with absolute and per second values.
<pre><img src="netdev.gif"></pre>
<p>The table columns are:<ul>
<li>for received data:<ul>
<li>network device name
<li>total bytes received
<li>total packets received
<li>bad packets received
<li>received packets dropped for lack of space in kernel buffers, plus receiver missed packets
<li>receiver FIFO overruns
<li>frame alignment errors received, including length, receiver ring buff overflow and CRC errors
<li>compressed packets received
<li>multicast packets received
</ul>
<li>for transmitted data:<ul>
<li>network device name
<li>total bytes transmitted
<li>total packets transmitted
<li>packet transmit problems
<li>packets not transmitted for lack of space in kernel buffers
<li>transmitter FIFO overruns
<li>collisions while transmitting
<li>carriers errors, including aborted, window and heartbeat errors
<li>compressed packets transmitted
</ul>
</ul>
<p><b>Module options:</b><ul>
<li><i>-C</i> <i>(only available for ssh on UNIX client)</i>
<br>Whether data compression is used on all data between client and server (useful on slow connections, see <i>ssh</i> manual for detailed information).
<li><i>-i file</i> <i>(only available for ssh on UNIX client)</i>
<br>Selects a file from which the identity (private key) for authentication is read (useful if an authentication agent is not running). It must not be protected by a passphrase.
<li><i>-p port</i> <i>(only available for ssh on UNIX client)</i>
<br>Port to connect to on the remote host.
<li><i>--proc directory</i>
<br>Data directory, also known as <i>proc</i> filesystem, <i>/proc</i> by default (for Linux machines support). For example, use <i>/compat/linux/proc</i> for FreeBSD machines.
<br><i><b>Note</b>: the data contained in that directory must be in a format identical to the reference Linux implementation.</i>
<li><i>-r (--remote) [[rsh|ssh]://][user@]host</i>
<br>remote monitoring using <i>user</i> as logname on remote host <i>host</i> (<i>rsh</i> or <i>ssh</i> facilities must be properly setup). If <i>user</i> is not specified, current user is used as logname on remote host. The protocol is either <i>ssh</i> or <i>rsh</i> (used by default). The module title is set to <i>arp(host)</i>.
</ul>
<p><b>Notes on remote monitoring:</b><ul>
<li>Using <i>ssh</i> is strongly recommended, as <i>rsh</i>, while being much less secure is also less efficient, as it requires creating a new session for each poll.
<li>On a Windows client, you must use the <i>putty</i> software package (see <i>install.txt</i>), which does not support <i>rsh</i> in non interactive sessions. Consequently, the <i>-r (--remote) ssh://session</i> syntax is required to remove any confusion (where <i>session</i> has been added to the running <i>pageant</i> application).
</ul>
<p><b>Examples:</b>
<pre>$ moodss netdev
$ moodss netdev -r jdoe@foo.bar.com
$ moodss netdev -r ssh://jdoe@foo.bar.com
$ moodss netdev --remote foo.bar.com</pre>
</body>
</html>
|
