1 <!DOCTYPE HTML PUBLIC
"-//W3C//DTD HTML 4.01//EN">
5 >Detailed Interface Statistics
</TITLE
8 CONTENT=
"Modular DocBook HTML Stylesheet Version 1.64
11 TITLE=
"IPTraf User's Manual"
12 HREF=
"manual.html"><LINK
14 TITLE=
"Network Interface Statistics"
15 HREF=
"netstats.html"><LINK
17 TITLE=
"Network Interface Statistics"
18 HREF=
"netstats.html"><LINK
20 TITLE=
"Statistical Breakdowns"
21 HREF=
"statbreakdowns.html"></HEAD
40 >IPTraf User's Manual
</TH
49 ><<< Previous
</A
55 >Network Interface Statistics
</TD
61 HREF=
"statbreakdowns.html"
62 >Next
>>></A
75 >Detailed Interface Statistics
</A
78 > The third menu option displays packet statistics for any
79 selected interface. It provides basically the same information
82 >General interface statistics
</I
84 option, with additional details.
85 This facility provides the following information:
</P
91 STYLE=
"list-style-type: disc"
93 > Total packet and byte counts
</P
96 STYLE=
"list-style-type: disc"
98 > IP packet and byte counts
</P
101 STYLE=
"list-style-type: disc"
103 > TCP packet and byte counts
</P
106 STYLE=
"list-style-type: disc"
108 > UDP packet and byte count
</P
111 STYLE=
"list-style-type: disc"
113 > ICMP packet and byte counts
</P
116 STYLE=
"list-style-type: disc"
118 > Other IP-type packet and byte counts
</P
121 STYLE=
"list-style-type: disc"
123 > Non-IP packet and byte counts
</P
126 STYLE=
"list-style-type: disc"
128 > Checksum error count
</P
131 STYLE=
"list-style-type: disc"
133 > Interface activity
</P
136 STYLE=
"list-style-type: disc"
138 > Broadcast packet and byte counts
</P
142 > All IP byte counts (IP, TCP, UDP, ICMP, other IP) include IP header data
143 and payload. The data link header is not included. The full frame length
144 (including data-link header) is included in the non-IP and Total
145 byte count. All data-link headers are also included in the Total byte
154 SRC=
"iptraf-dstat1.png"></P
157 >Figure
2. The detailed interface statistics screen
</B
161 > The upper portion of the screen
162 contains the packet and byte counts for all IP and
163 non-IP packets intercepted on the interface. The lower portion
164 contains the total, incoming, and outgoing interface data rates.
</P
166 > This facility also displays incoming and outgoing counts and data rates.
167 The packet size breakdown in versions prior to
2.0.0 has been moved
168 to its own facility under
<I
170 >Statistical breakdowns.../By packet
173 HREF=
"statbreakdowns.html#PKTSIZE"
177 > An outgoing packet is one that exits your interface, regardless
178 of whether it originated from your machine or came
179 from another machine and was routed through yours. An incoming packet is
180 one that enters your interface, either addressed
181 to you directly, broadcast, multicast, or captured promiscuously.
</P
183 > The rate indicators can be set to display kbits/s or kbytes/s with the
187 > configuration option.
</P
202 SRC=
"./stylesheet-images/note.gif"
219 > Buffering and some other factors may affect the data rates, notably
220 the outgoing rate, causing it to reflect a higher figure than the actual
221 rate at which the interface is sending.
</P
227 > The figures are logged at regular intervals if logging is enabled. The
228 default log file name at the prompt is
231 >iface_stats_detailed-
<TT
238 where iface is the selected interface for this session (for example,
241 >iface_stats_detailed-eth0.log
</TT
244 > If you wish to start this facility directly
245 from the command line, you can specify the
247 CLASS=
"COMPUTEROUTPUT"
249 > parameter and an interface
250 to monitor. For example,
</P
264 > starts the statistics for
<TT
267 >. The interface must be specified, or
268 IPTraf will not start the facility.
</P
270 > When started from the command line, the log filename and log interval can be
271 specified with the
<TT
272 CLASS=
"COMPUTEROUTPUT"
275 CLASS=
"COMPUTEROUTPUT"
278 parameters respectively. See the
<A
280 >Command-line Parameters
</A
282 section above for more information.
</P
297 SRC=
"./stylesheet-images/note.gif"
314 > In both the general and detailed statistics screens, as well as
315 in the IP traffic monitor, the packet counts are for
316 actual network packets (layer
2), not the logical IP packets (layer
3)
317 that may be reconstructed after fragmentation. That means, if a
318 packet was fragmented into four pieces, and these four fragments pass
319 over your interface, the packet counts will indicate four separate
327 > The figure for the IP checksum errors is a packet count only, because the
328 corrupted IP header cannot be relied upon to give a correct IP
329 packet length value.
</P
331 > This facility's output is also affected by IPTraf's
<A
334 >. See Chapter
7 for more information
337 > Pressing X or Q takes you back to the main menu (if this
338 facility was started with the command-line option, X or Q drops you back
357 ><<< Previous
</A
372 HREF=
"statbreakdowns.html"
373 >Next
>>></A
381 >Network Interface Statistics
</TD
394 >Statistical Breakdowns
</TD