Sophie: ksnuffle-2.2-6mdk i586

ksnuffle-2.2-6mdk.i586.rpm

<HTML>
  <HEAD>
   <TITLE>KSnuffle: General Description </TITLE>
  </HEAD>
  <BODY TEXT="#000000" BGCOLOR="#FFFFFF" LINK="#AA0000">
    <FONT FACE="Helvetica">
    <A HREF="http://www.kde.org/"><IMG SRC="logotp3.gif" ALT="The K Desktop Environment" BORDER="0"></A>
    <HR WIDTH="100%" SIZE="2" ALIGN="CENTER" NOSHADE>
    <DIV ALIGN="right">
      <A HREF="index-4.1.html">Next</A><A HREF="index-2.html">Previous</A><A HREF="index.html#toc3">Table of Contents</A>
    </DIV>
    <BR>&nbsp;
    <H3>
      3. General Description
    </H3>
    <P>
      KSnuffle is a network traffic monitor, which can monitor, display, log
      and replay information about traffic passing through or by a network
      interface.
    </P>
    <P>
      It comprises two main components:
      <UL>
        <LI>
	  Network traffic display and logging - this is referred to as a
	  <I>sniffer</I> in this documentation.
        </LI>
        <LI>
	  Log replay - this is referred to as a <I>replayer</I> in this
	  documentation.
        </LI>
      </UL>
    </P>
    <P>
      In addition to the display pages for the above, there are three extra
      display pages:
      <UL>
	<LI>
	  Parallel display of multiple load graphs (for both <I>sniffers</I>
	  and <I>replayers</I>)
	</LI>
	<LI>
	  Global setup
	</LI>
	<LI>
	  Privileged user setup (when running as root)
	</LI>
      </UL>
    </P>
    <P>
      The <I>sniffer</I> and <I>replay</I> components each have five display
      screens:
      <UL>
	<LI>Main configuration</LI>
	<LI>Filter and trigger configuration</LI>
	<LI>Event command configuration</LI>
	<LI>Graphic display - this shows a load histogram and time-averaged
	    load monitor</LI>
	<LI>Packet display - this shows specific packet details</LI>
      </UL>
      These may be augmented by plugins.
    </P>
    <HR>
    <P>
      <A NAME="buttons"></A>An important point to note about the
      <I>configuration</I> screen is the use of the <B>Set</B>, <B>Clear</B>,
      <B>Reset</B> and <B>Go</B> buttons.
    </P>
    <P>
      The configuration maintains a state which is the values of the various
      control fields at the time that the <B>Set</B> button was last pressed.
      Hence, further changes to the control fields have no affect[*] until
      <B>Set</B> is pressed once more. The <B>Clear</B> button clears most
      control fields to a default state, but does not affect[*] the
      underlying state; the <B>Reset</B> restores the control fields to the
      underlying state (ie., the values the last time <B>Set</B> was pressed).
    </P>
    <P>
      In a <I>sniffer</I>, when <B>Set</B> is pressed, the packet filter and
      trigger programs are verified (and an error will be reported if it
      is invalid). Provided that there are no errors, the <B>Go</B> button
      is then enabled, however execution of the <I>sniffer</I> or
      <I>replayer</I> is not started until the <B>Go</B> button is pressed.
    </P>
    <P>
      [*] Note that no control has any <I>impact</I> on anything. An impact
      is a physical event, and is not synonymous with the verb <I>effect</I>,
      nor with <I>affect</I>. This use of the word <I>impact</I> is a
      consequence of letting a bunch of illiterates from the US-of-A loose
      on the English language.
    </P>
    <P>
      <A HREF="index-4.1.html">Next</A>
      <A HREF="index-2.html">Previous</A>
      <A HREF="index.html#toc3">Table of Contents</A>
    </P>
    <CENTER>
      <HR WIDTH="100%" SIZE="3" ALIGN="CENTER" NOSHADE>
    </CENTER>
  </BODY>
</HTML>