index.docbook

knetfilter-3.3.0.tar Linux

<!DOCTYPE book PUBLIC  "-//KDE//DTD DocBook V3.1-Based Variant V1.0//EN" 
" "[

  <!ENTITY kappname "&knetfilter;">
  <!ENTITY % addindex "IGNORE">
  <!ENTITY % English "INCLUDE"> <!-- change language only here -->
  <!-- Do not define any other entities; instead, use the entities
       from kde-genent.entities and <lg>/user.entities. -->
]>
<bookinfo>

<!-- kdoctemplate v0.8 October 1 1999
     Minor update to "Credits and Licenses" section on August 24, 2000   -->

<!--
This template was designed by: David Rugge [e-mail]
with lots of help from: Eric Bischoff [e-mail]
and Frederik Fouvry [e-mail]
of the KDE DocBook team.

You may freely use this template for writing any sort of KDE documentation.
If you have any changes or improvements, please let us know.

In the future, we may want to change from SGML-based DocBook to XML-based
DocBook. To make this change easier, please be careful :
- in XML, the case of the <tags> and attributes is relevant ;
- also, quote all attributes.

Please don't forget to remove all these comments in your final documentation,
thanks ;-).
-->

<!-- ................................................................ -->

<!-- The language must NOT be changed. -->

<book lang="&language;">

<!-- This header contains all of the meta-information for the document such
as Authors, publish date, the abstract, and Keywords -->

<bookinfo>
<title>The KNetFilter Handbook</title>

<authorgroup>
<author>
<firstname>Luigi</firstname>
<!--<othername>N.</othername>-->
<surname>Genoni</surname>
<affiliation>
<address><email>[e-mail]</email></address>
</affiliation>
</author>
</authorgroup>


<copyright>
<year>1999</year>
<year>2000</year>
<holder>George N. Ugnacious</holder>
</copyright>
<!-- Translators: put here the copyright notice of the translation -->
<!-- Put here the FDL notice.  Read the explanation in fdl-notice.docbook
     and in the FDL itself on how to use it. -->
<legalnotice>&FDLNotice;</legalnotice>

<!-- Date and version information of the documentation
Don't forget to include this last date and this last revision number, we
need them for translation coordination !
Please respect the format of the date (DD/MM/YYYY) and of the version
(Major.minor.lesser), it could be used by automation scripts.
Do NOT change these in the translation. -->

<date>06/11/2000</date>
<releaseinfo>2.0.00</releaseinfo>

<!-- Abstract about this handbook -->

<abstract>
<para>
&kapp; is an application specially designed to configure the new 2.4 kernel ip
filtering and NAT rules
</para>
</abstract>

<!-- This is a set of Keywords for indexing by search engines.
Please at least include KDE, the KDE package it is in, the name
 of your application, and a few relevant keywords. -->

<keywordset>
<keyword>KDE</keyword>
<keyword>KNetFilter</keyword>
<keyword>security</keyword>
<keyword>kernel 2.4</keyword>
</keywordset>

</bookinfo>

<!-- The contents of the documentation begin here.  Label
each chapter so with the id attribute. This is necessary for two reasons: it
allows you to easily reference the chapter from other chapters of your
document, and if there is no ID, the name of the generated HTML files will vary
from time to time making it hard to manage for maintainers and for the CVS
system. Any chapter labelled (OPTIONAL) may be left out at the author's
discretion. Other chapters should not be left out in order to maintain a
consistent documentation style across all KDE apps. -->

<chapter id="introduction">
<title>Introduction</title>

<!-- The introduction chapter contains a brief introduction for the application
that explains what it does, where to report problems, and a brief revision
history of the app. Basically a long version of the abstract. -->

<para>
Welcome to &kapp;. This application manages netfilter rules. &kapp; gives you the option to close a
port to the rest of your network or the internet. There is a list of the most commonly exploited
ports later. There is probably some qt and KDE guru out there who thinks this application sucks,
or that the code is poorly. I have to say that I am not a very good coder, the knetfilter code may
be poor, or/and bad but it works (here anyway). As model i took kfirewall, that was good for his
own purpose, but i tried to make possible to manage all common things that everyone would like to
do with his own firewall. I also addedd interface to tcpdump, to make it possible to manage
seriously security issues. The main scope of this application is to be useful, easy to understand
and to be further developed.

This application has been thought to be used not only within lans, but also with ppp, slip, isdn
connections, if someone would like to connect more than one computer to the internet trough his
modem. This is an eredity from kfirewall that I am happy to keep.

The possibility to save the port settings and to reload them is already implemented, but in the
reality it does not work, since iptables lacks those commands. Right now i am waiting netfilter
guys to implement this possibility the same way as ipchains.
</para>

<!-- Note that the revhistory tags apply to the documentation version and not to
the app version. That is why we use an itemizedlist here. -->

<sect1 id="kapp-revhistory">
<title>&kapp; Revision History</title>
<para>
<itemizedlist>
<listitem><para>2.0 - first public release for kde2</para></listitem>
</itemizedlist>
</para>
</sect1>
</chapter>

<chapter id="installation">
<title>Installation</title>

<sect1 id="getting-kapp">
<title>How to obtain Kapp</title>

<para>
&kapp; is part of the KDE project
<ulink url="http://www.kde.org">http://www.kde.org</ulink>.
&kapp; can be found in the kdeutils package on
<ulink url="ftp://ftp.kde.org/pub/kde/">ftp://ftp.kde.org/pub/kde/</ulink>, the
main ftp site of the KDE project. </para>
</sect1>

<sect1 id="requirements">
<title>Requirements</title>

<!--
List any special requirements for your application here. This should include:
.Libraries or other software that is not included in kdesupport,
kdelibs, or kdebase.
.Hardware requirements like amount of RAM, disk space, graphics card
capabilities, screen resolution, special expansion cards, etc.
.Operating systems the app will run on. If your app is designed only for a
specific OS, (you wrote a graphical LILO configurator for example) put this
information here.
-->

<para>
In order to successfully use &kapp;, you need KDE 2.0 and Qt 2.2.x. You'll also
need a recent kernel 2.4.x (at least 2.4.0-test9) and a recent iptables
package.
</para>

<para>
All required libraries as well as &kapp; itself can be found
on <ulink url="ftp://ftp.kapp.org">The &kapp; home page</ulink>.
</para>

</sect1>

<sect1 id="compilation">
<title>Compilation and installation</title>

<para>
In order to compile and install &kapp; on your system, type the following in the base
directory of the Icon Editor distribution:
<screen width="40">
<prompt>%</prompt> <userinput>./configure</userinput>
<prompt>%</prompt> <userinput>make</userinput>
<prompt>%</prompt> <userinput>make install</userinput>
</screen>
</para>

<para>Since &kApp; uses autoconf and automake you should have not trouble compiling it.
Should you run into problems please report them to the Authors.</para>
</sect1>

<sect1 id="configuration">
<title>Configuration</title>

<para>Don't forget to tell your system to start the <filename>dtd</filename>
dicer-toaster daemon first, or KApp won't work !</para>

</sect1>

</chapter>

<chapter id="using-kapp">
<title>Using Kapp</title>

<!-- This chapter should tell the user how to use your app. You should use as
many sections (Chapter, Sect1, Sect3, etc...) as is necessary to fully document
your application. -->

<para>

<!-- Note that all graphics should be in .png format. Use no gifs because of
patent issues. -->

<screenshot>
<screeninfo>Here's a screenshot of &kapp;</screeninfo>
	<mediaobject>
	  <imageobject>
	    <imagedata fileref="screenshot.png" format="png">
	  </imageobject>
	  <imageobject>
	    <imagedata fileref="screenshot.eps" format="eps">
	  </imageobject>
	  <textobject>
	    <phrase>Screenshot</phrase>
	  </textobject>
	</mediaobject>
</screenshot>
</para>


<sect1 id="kapp-features">
<title>More Kapp features</title>

<para>It slices! It dices! and it comes with a free toaster!</para>
<para>
The Squiggle Tool <guiicon><inlinemediaobject>
	  <imageobject>
	    <imagedata fileref="squiggle.png" format="png">
	  </imageobject>
	  <imageobject>
	    <imagedata fileref="squiggle.eps" format="eps">
	  </imageobject>
	  <textobject>
	    <phrase>Squiggle</phrase>
	  </textobject>
</inlinemediaobject></guiicon> is used to draw squiggly lines all over
the &kapp; main window. It's not a bug, it's a feature!
</para>

</sect1>
</chapter>

<chapter id="commands">
<title>Command Reference</title>

<!-- (OPTIONAL, BUT RECOMMENDED) This chapter should list all of the
application windows and their menubar and toolbar commands for easy reference.
Also include any keys that have a special function but have no equivalent in the
menus or toolbars. This may not be necessary for small apps or apps with no tool
or menu bars. -->

<sect1 id="kapp-mainwindow">
<title>The main Kapp window</title>
<para></para>

<sect2>
<title>The File Menu</title>
<para>
<variablelist>