Gecko [ fernandoquevedodop.com ]

Name	Size	Permission
stylesheet-images	[ DIR ]	drwxr-xr-x
a1980.html	22.26 KB	-rw-r--r--
a2377.html	3.45 KB	-rw-r--r--
c1037.html	3.72 KB	-rw-r--r--
c1101.html	4.73 KB	-rw-r--r--
c1147.html	34.02 KB	-rw-r--r--
c1793.html	11.21 KB	-rw-r--r--
c1957.html	4.17 KB	-rw-r--r--
c277.html	2.99 KB	-rw-r--r--
c429.html	17.08 KB	-rw-r--r--
c66.html	3.56 KB	-rw-r--r--
c954.html	4.45 KB	-rw-r--r--
f21.html	2.41 KB	-rw-r--r--
index.html	9.81 KB	-rw-r--r--
iptraf-configmenu.png	5.02 KB	-rw-r--r--
iptraf-dstat1.png	4.31 KB	-rw-r--r--
iptraf-editfilter.png	3.46 KB	-rw-r--r--
iptraf-filtermenu.png	2.99 KB	-rw-r--r--
iptraf-gstat1.png	1.84 KB	-rw-r--r--
iptraf-hw.png	4.71 KB	-rw-r--r--
iptraf-hwsort.png	6.38 KB	-rw-r--r--
iptraf-ipfltdlg.png	4.62 KB	-rw-r--r--
iptraf-ipfltlist.png	2.09 KB	-rw-r--r--
iptraf-ipfltmenu.png	3.13 KB	-rw-r--r--
iptraf-ipfltnamedlg.png	2.97 KB	-rw-r--r--
iptraf-iptm1.png	8.35 KB	-rw-r--r--
iptraf-iptmsort.png	7.99 KB	-rw-r--r--
iptraf-logprompt.png	4.15 KB	-rw-r--r--
iptraf-mmenu.png	2.74 KB	-rw-r--r--
iptraf-othipfltdefine.png	3.63 KB	-rw-r--r--
iptraf-othipfltdlg.png	4.47 KB	-rw-r--r--
iptraf-othipfltselect.png	3.34 KB	-rw-r--r--
iptraf-pktsize.png	5.21 KB	-rw-r--r--
iptraf-tcpflt-dlg2.png	3.62 KB	-rw-r--r--
iptraf-tcpfltmenu.png	3.99 KB	-rw-r--r--
iptraf-tcpudp.png	6.94 KB	-rw-r--r--
iptraf-tcpudpsort.png	7.56 KB	-rw-r--r--
iptraf-timermenu.png	5.49 KB	-rw-r--r--
x1062.html	6.22 KB	-rw-r--r--
x1142.html	2.21 KB	-rw-r--r--
x144.html	4.37 KB	-rw-r--r--
x171.html	6.46 KB	-rw-r--r--
x1789.html	2.11 KB	-rw-r--r--
x1880.html	6.74 KB	-rw-r--r--
x1915.html	6.71 KB	-rw-r--r--
x2335.html	4.66 KB	-rw-r--r--
x2387.html	5.26 KB	-rw-r--r--
x2397.html	2.69 KB	-rw-r--r--
x2401.html	3.99 KB	-rw-r--r--
x2407.html	7.11 KB	-rw-r--r--
x2443.html	3.17 KB	-rw-r--r--
x2448.html	2.62 KB	-rw-r--r--
x2452.html	2.86 KB	-rw-r--r--
x2456.html	2.59 KB	-rw-r--r--
x2459.html	2.38 KB	-rw-r--r--
x2462.html	2.9 KB	-rw-r--r--
x2467.html	3.13 KB	-rw-r--r--
x262.html	2.54 KB	-rw-r--r--
x27.html	3.85 KB	-rw-r--r--
x270.html	2.54 KB	-rw-r--r--
x304.html	3.65 KB	-rw-r--r--
x322.html	2.2 KB	-rw-r--r--
x328.html	4.85 KB	-rw-r--r--
x606.html	13.74 KB	-rw-r--r--
x938.html	3.11 KB	-rw-r--r--
x96.html	4.39 KB	-rw-r--r--
x980.html	7.06 KB	-rw-r--r--

Code Editor : x606.html

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN""http://www.w3.org/TR/html4/loose.dtd">
<HTML
><HEAD
><TITLE
>Lower Window</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK
REL="HOME"
TITLE="IPTraf-ng User's Manual"
HREF="index.html"><LINK
REL="UP"
TITLE="The IP Traffic Monitor"
HREF="c429.html"><LINK
REL="PREVIOUS"
TITLE="The IP Traffic Monitor"
HREF="c429.html"><LINK
REL="NEXT"
TITLE="Additional Information"
HREF="x938.html"></HEAD
><BODY
CLASS="SECT1"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
SUMMARY="Header navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TH
COLSPAN="3"
ALIGN="center"
>IPTraf-ng User's Manual</TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="c429.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Chapter 3. The IP Traffic Monitor</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="x938.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="LOWERWIN"
>3.2. Lower Window</A
></H1
> The lower window displays information about the other types of traffic
 on your network. The following protocols are detected internally:<UL
COMPACT="COMPACT"
><LI
>User Datagram Protocol (UDP)</LI
><LI
>Internet Control Message Protocol (ICMP)</LI
><LI
>Open Shortest-Path First (OSPF)</LI
><LI
>Interior Gateway Routing Protocol (IGRP)</LI
><LI
>Interior Gateway Protocol (IGP)</LI
><LI
>Internet Group Management Protocol (IGMP)</LI
><LI
>General Routing Encapsulation (GRE)</LI
><LI
>Layer 2 Tunneling Protocol (L2TP)</LI
><LI
>IPSec AH and ESP protocols (IPSec AH and IPSec ESP)</LI
><LI
>Address Resolution Protocol (ARP)</LI
><LI
>Reverse Address Resolution Protocol (RARP)</LI
></UL
> Other IP protocols are looked up from the <TT
CLASS="FILENAME"
>/etc/services</TT
>
 file. If <TT
CLASS="FILENAME"
>/etc/services</TT
> doesn't contain information about
 that protocol, the protocol number is indicated. Non-IP packets are indicated as
<SAMP
CLASS="COMPUTEROUTPUT"
>Non-IP</SAMP
> in the lower window.<DIV
CLASS="NOTE"
><TABLE
CLASS="NOTE"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TH
ALIGN="LEFT"
VALIGN="MIDDLE"
>Note</TH
></TR
><TR
><TD
>&nbsp;</TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
>The source and destination addresses for ARP and
RARP entries are MAC addresses. Strictly speaking, ARP and RARP packets aren't IP packets, since
 they are not encapsulated in an IP datagram. They're
 just indicated because they are integral to proper IP operation on LANs.</TD
></TR
></TABLE
></DIV
> For all packets in the lower window, only the first IP fragment is
 indicated (since that contains the header
 of the IP-encapsulated protocol) but with no further information
 from the encapsulated protocol.UDP packets are also displayed
in
<SAMP
CLASS="COMPUTEROUTPUT"
><TT
CLASS="REPLACEABLE"
>address</TT
>:<TT
CLASS="REPLACEABLE"
>port</TT
></SAMP
> format while ICMP entries also contain the
ICMP message type. For easier location, each type of protocol
is color-coded (only on color terminals such as the Linux console).<DIV
CLASS="VARIABLELIST"
><DL
><DT
>UDP</DT
><DD
>Red on White</DD
><DT
>ICMP</DT
><DD
>Yellow on Blue</DD
><DT
>OSPF</DT
><DD
>Black on Cyan</DD
><DT
>IGRP</DT
><DD
>Bright white on Cyan</DD
><DT
>IGP</DT
><DD
>Red on Cyan</DD
><DT
>IGMP</DT
><DD
>Bright green on Blue</DD
><DT
>GRE</DT
><DD
>Blue on white</DD
><DT
>ARP</DT
><DD
>Bright white on Red</DD
><DT
>RARP</DT
><DD
>Bright white on Red</DD
><DT
>Other IP</DT
><DD
>Yellow on red</DD
><DT
>Non-IP</DT
><DD
>Yellow on Red</DD
></DL
></DIV
> The lower window can hold up to 512 entries. You can
 scroll the lower window by using the W key to move the Active indicator
 to it, and by using the Up and Down cursor keys. The lower
 window automatically scrolls every time a new entry is added, and either
 the first entry or last entry is visible. Upon reaching 512 entries, old
 entries are thrown out as new entries are added. Some entries may be too long to completely fit in a screen line. You can
 use the Left and Right cursor keys to vertically scroll the lower window
 when it is marked <SAMP
CLASS="COMPUTEROUTPUT"
>Active</SAMP
>. If your
terminal can be resized (e.g. xterm), you may do so before starting
IPTraf-ng. Entries for packets received on LAN interfaces also include the
 source MAC address of the LAN host which delivered it. This behavior
 is enabled by turning on the Source MAC addrs in traffic monitor toggle
 in the <A
HREF="c1793.html"
>Configure...</A
> menu.<DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN697"
>3.2.1. Entry Details</A
></H2
> In general, the entries in the lower window indicate the protocol, the
 IP datagram size (full frame size for non-IP, including ARP and
 RARP), the source address, the destination
 address, and the network interface the packet was detected on.
 However, some protocols have a little more information.<DIV
CLASS="SECT3"
><H3
CLASS="SECT3"
><A
NAME="AEN700"
>3.2.1.1. ICMP</A
></H3
> ICMP entries are displayed in this format:<PRE
CLASS="SYNOPSIS"
>ICMP <TT
CLASS="REPLACEABLE"
>type</TT
> [(<TT
CLASS="REPLACEABLE"
>subtype</TT
>)] (<TT
CLASS="REPLACEABLE"
>size</TT
> bytes) from <TT
CLASS="REPLACEABLE"
>source</TT
> to <TT
CLASS="REPLACEABLE"
>destination</TT
>
[(src HWaddr <TT
CLASS="REPLACEABLE"
>srcMACaddress</TT
>)] on <TT
CLASS="REPLACEABLE"
>interface</TT
></PRE
> where type could be any of the following:<DIV
CLASS="VARIABLELIST"
><DL
><DT
><SAMP
CLASS="COMPUTEROUTPUT"
>echo req, echo rply</SAMP
></DT
><DD
> ICMP echo request and reply. Usually used by the ping program and other network monitoring and diagnostic program. </DD
><DT
><SAMP
CLASS="COMPUTEROUTPUT"
>dest unrch</SAMP
></DT
><DD
> ICMP destination unreachable. Something failed to reach its target. The dest unreach type is supplemented with a further indicator of the problem. Destination unreachable messages for TCP traffic causes the corresponding TCP entry in the upper
 window to be made available for reuse by new connections. </DD
><DT
><SAMP
CLASS="COMPUTEROUTPUT"
>redirct</SAMP
></DT
><DD
> ICMP redirect. Usually generated by a router to tell a host that a better gateway is available. </DD
><DT
><SAMP
CLASS="COMPUTEROUTPUT"
>src qnch</SAMP
></DT
><DD
> The ICMP source quench is used to stop a host from transmitting. It's a
flow control mechanism for IP. </DD
><DT
><SAMP
CLASS="COMPUTEROUTPUT"
>time excd</SAMP
></DT
><DD
> Indicates a packet's time-to-live value expired before it got
to its destination. Mostly happens if a destination is too far away.
Also used by the traceroute program.</DD
><DT
><SAMP
CLASS="COMPUTEROUTPUT"
>router adv</SAMP
></DT
><DD
> ICMP router advertisement </DD
><DT
><SAMP
CLASS="COMPUTEROUTPUT"
>router sol</SAMP
></DT
><DD
> ICMP router solicitation </DD
><DT
><SAMP
CLASS="COMPUTEROUTPUT"
>timestmp req</SAMP
></DT
><DD
> ICMP timestamp request</DD
><DT
><SAMP
CLASS="COMPUTEROUTPUT"
>timestmp rep</SAMP
></DT
><DD
> ICMP timestamp reply </DD
><DT
><SAMP
CLASS="COMPUTEROUTPUT"
>info req</SAMP
></DT
><DD
> ICMP information request </DD
><DT
><SAMP
CLASS="COMPUTEROUTPUT"
>info rep</SAMP
></DT
><DD
> ICMP information reply </DD
><DT
><SAMP
CLASS="COMPUTEROUTPUT"
>addr mask req</SAMP
></DT
><DD
> ICMP address mask request </DD
><DT
><SAMP
CLASS="COMPUTEROUTPUT"
>addr mask rep</SAMP
></DT
><DD
> ICMP address mask reply </DD
><DT
><SAMP
CLASS="COMPUTEROUTPUT"
>param prob</SAMP
></DT
><DD
> ICMP parameter problem </DD
><DT
><SAMP
CLASS="COMPUTEROUTPUT"
>bad/unknown</SAMP
></DT
><DD
> An unrecognized ICMP packet was received, or the packet is corrupted.</DD
></DL
></DIV
> The destination unreachable message also includes information on the
 type of error encountered. Here are the destination unreachable codes:<DIV
CLASS="VARIABLELIST"
><DL
><DT
><SAMP
CLASS="COMPUTEROUTPUT"
>ntwk</SAMP
></DT
><DD
> network unreachable </DD
><DT
><SAMP
CLASS="COMPUTEROUTPUT"
>host</SAMP
></DT
><DD
> host unreachable </DD
><DT
><SAMP
CLASS="COMPUTEROUTPUT"
>proto</SAMP
></DT
><DD
> protocol unreachable </DD
><DT
><SAMP
CLASS="COMPUTEROUTPUT"
>port</SAMP
></DT
><DD
> port unreachable </DD
><DT
><SAMP
CLASS="COMPUTEROUTPUT"
>pkt fltrd</SAMP
></DT
><DD
> packet filtered (normally by an access rule on a router or firewall) </DD
><DT
><SAMP
CLASS="COMPUTEROUTPUT"
>DF set</SAMP
></DT
><DD
> the packet has to be fragmented somewhere, but its don't fragment
 (DF) bit is set.</DD
><DT
><SAMP
CLASS="COMPUTEROUTPUT"
>src rte fail</SAMP
></DT
><DD
> source route failed </DD
><DT
><SAMP
CLASS="COMPUTEROUTPUT"
>src isltd</SAMP
></DT
><DD
> source isolated (obsolete) </DD
><DT
><SAMP
CLASS="COMPUTEROUTPUT"
>net comm denied</SAMP
></DT
><DD
> network communication denied </DD
><DT
><SAMP
CLASS="COMPUTEROUTPUT"
>host comm denied</SAMP
></DT
><DD
> host communication denied </DD
><DT
><SAMP
CLASS="COMPUTEROUTPUT"
>net unrch for TOS</SAMP
></DT
><DD
> network unreachable for specified IP type-of-service </DD
><DT
><SAMP
CLASS="COMPUTEROUTPUT"
>host unrch for TOS</SAMP
></DT
><DD
> host unreachable for specified IP type-of-service </DD
><DT
><SAMP
CLASS="COMPUTEROUTPUT"
>prec violtn</SAMP
></DT
><DD
> precedence violation </DD
><DT
><SAMP
CLASS="COMPUTEROUTPUT"
>prec cutoff</SAMP
></DT
><DD
> precedence cutoff </DD
><DT
><SAMP
CLASS="COMPUTEROUTPUT"
>dest net unkn</SAMP
></DT
><DD
> destination network unknown </DD
><DT
><SAMP
CLASS="COMPUTEROUTPUT"
>dest host unkn</SAMP
></DT
><DD
> destination network unknown</DD
></DL
></DIV
> For more information on ICMP, see RFC 792.</DIV
><DIV
CLASS="SECT3"
><H3
CLASS="SECT3"
><A
NAME="AEN871"
>3.2.1.2. OSPF</A
></H3
>OSPF messages also include a little more information. The format of an
OSPF message in the window is:<PRE
CLASS="SYNOPSIS"
>OSPF <TT
CLASS="REPLACEABLE"
>type</TT
> (a=<TT
CLASS="REPLACEABLE"
>area</TT
> r=<TT
CLASS="REPLACEABLE"
>router</TT
>) (<TT
CLASS="REPLACEABLE"
>size</TT
>bytes) from <TT
CLASS="REPLACEABLE"
>source</TT
> to <TT
CLASS="REPLACEABLE"
>destination</TT
>
[(src HWaddr <TT
CLASS="REPLACEABLE"
>srcMACaddress</TT
>)] on <TT
CLASS="REPLACEABLE"
>interface</TT
></PRE
> The type can be one of the following:<DIV
CLASS="VARIABLELIST"
><DL
><DT
><SAMP
CLASS="COMPUTEROUTPUT"
>hlo</SAMP
></DT
><DD
> OSPF hello. Hello messages establish OSPF communications and keep routers informed of each other's presence. </DD
><DT
><SAMP
CLASS="COMPUTEROUTPUT"
>DB desc</SAMP
></DT
><DD
> OSPF Database Description </DD
><DT
><SAMP
CLASS="COMPUTEROUTPUT"
>LSR</SAMP
></DT
><DD
> OSPF Link State Request </DD
><DT
><SAMP
CLASS="COMPUTEROUTPUT"
>LSU</SAMP
></DT
><DD
> OSPF Link State Update. Messages indicating the states of the OSPF network links </DD
><DT
><SAMP
CLASS="COMPUTEROUTPUT"
>LSA</SAMP
></DT
><DD
> OSPF Link State Acknowledgment</DD
></DL
></DIV
> The entries in parentheses:<DIV
CLASS="VARIABLELIST"
><DL
><DT
><SAMP
CLASS="COMPUTEROUTPUT"
>a=<TT
CLASS="REPLACEABLE"
>area</TT
></SAMP
></DT
><DD
> The area number of the OSPF message</DD
><DT
><SAMP
CLASS="COMPUTEROUTPUT"
>r=<TT
CLASS="REPLACEABLE"
>router</TT
></SAMP
></DT
><DD
> The IP address of the router that generated the message. It
 is not necessarily the same as the source address
 of the encapsulating IP packet.</DD
></DL
></DIV
> Many times, the destination addresses for OSPF packets are class D
 multicast addresses in standard dotted decimal notation or (if reverse
 lookup is enabled), hosts under the <SAMP
CLASS="COMPUTEROUTPUT"
>MCAST.NET</SAMP
> domain. Such multicast
 addresses are defined as follows:<DIV
CLASS="VARIABLELIST"
><DL
><DT
><SAMP
CLASS="COMPUTEROUTPUT"
>224.0.0.5 (OSPF-ALL.MCAST.NET)</SAMP
></DT
><DD
>OSPF all routers</DD
><DT
><SAMP
CLASS="COMPUTEROUTPUT"
>224.0.0.6 (OSPF-DSIG.MCAST.NET)</SAMP
></DT
><DD
>OSPF all designated routers</DD
></DL
></DIV
> See RFC 1247 for details on the OSPF protocol.</DIV
></DIV
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="c429.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
ACCESSKEY="H"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="x938.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>The IP Traffic Monitor</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="c429.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Additional Information</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>

${this.title}

Code Editor : x606.html