<?xml version = '1.0' encoding = 'UTF-8' ?>
<!DOCTYPE book PUBLIC "-//KDE//DTD DocBook XML V4.1-Based Variant V1.0//EN" "dtd/kdex.dtd">
<!-- change language only here --><!--
Local Variables:
mode: sgml
sgml-omittag: nil
sgml-shorttag: t
sgml-general-insert-case: lower
End:
--><book lang="" >
  <bookinfo>
    <title>KNetworkConf Manual</title>
    <authorgroup>
      <author>
        <firstname>Christoph</firstname>
        <surname>Eckert</surname>
        <affiliation>
          <address>
            <email>mchristoph.eckert |at| t-online.de</email>
          </address>
        </affiliation>
      </author>
    </authorgroup>
    <date>date</date>
    <releaseinfo>0.2</releaseinfo>
    <abstract>
      <para>
      KNetworkConf is a KDE Control Center Module which lets you easily configure the settings of your network devices. It replaces the multiple different distribution dependend tools and offers a perfect integration into the KDE desktop.
      </para>
    </abstract>
    <keywordset>
      <keyword>KDE</keyword>
      <keyword>KNetworkConf</keyword>
    </keywordset>
  </bookinfo>
  <chapter id="introduction" >
    <title>Introduction</title>
    <sect1 id="first-words" >
      <title>First words</title>
      <para>
      Welcome to KNetworkConf. KNetworkConf makes the configuration of your networking devices very easy. All commonly needed settings can be made quickly from the KDE control center.
      </para>
      <sect2 id="intention" >
        <title>Intention</title>
        <para>
      KNetworkConf has been made to be intuitive. All functions are avaible via the graphical user interface. But if you use KNetworkConf for the first time, please read on to get an idea how to use this Network config tool.
      </para>
      </sect2>
      <sect2 id="scope-of-services" >
        <title>Scope of Services</title>
        <para>
Let's have a look what KNetworkConf can do for you...
      </para>
        <para>
          <itemizedlist>
            <listitem>
              <para>
Applying IP addresses to interfaces
        </para>
            </listitem>
            <listitem>
              <para>
Applying netmasks to interfaces
        </para>
            </listitem>
            <listitem>
              <para>
Start and stop interfaces' activities
        </para>
            </listitem>
            <listitem>
              <para>
Configure Routing
        </para>
            </listitem>
            <listitem>
              <para>
Configure Host- and Domainname
        </para>
            </listitem>
            <listitem>
              <para>
Configure Resolving
        </para>
            </listitem>
            <listitem>
              <para>
Manage known hosts
        </para>
            </listitem>
          </itemizedlist>
        </para>
        <para>
...and what not:
      </para>
        <para>
          <itemizedlist>
            <listitem>
              <para>
Install drivers for the network hardware
        </para>
            </listitem>
            <listitem>
              <para>
Configure Samba (for setting up filesharing with Win machines)
        </para>
            </listitem>
            <listitem>
              <para>
Configure NetaTalk (for setting up filesharing with Mac machines)
        </para>
            </listitem>
            <listitem>
              <para>
Configure NFS (for setting up filesharing with other UN*X machines)
        </para>
            </listitem>
            <listitem>
              <para>
Configure webservers
        </para>
            </listitem>
            <listitem>
              <para>
Configure Peer-to-Peer-networks (for sharing files over the internet)
        </para>
            </listitem>
            <listitem>
              <para>
Prepare coffee
        </para>
            </listitem>
          </itemizedlist>
        </para>
        <para>
This means that KNetworkConf helps you setting up the networking functionality between the hardware and the network applications.
        </para>
      </sect2>
    </sect1>
  </chapter>
  <chapter id="usage" >
    <title>Usage</title>
    <para>This chapter describes the normal usage of <application>KNetworkConf</application>.</para>
<!--
/ I'm a comment line
-->    <para>
Start KNetworkConf by involing the control center. Klick on the button <guimenu>Administrator Mode</guimenu>:
      </para>
    <mediaobject>
      <imageobject>
        <imagedata fileref="11.png" format="PNG" align="center" />
      </imageobject>
      <textobject>
        <phrase>Invoking the admin mode</phrase>
      </textobject>
    </mediaobject>
    <para>
Or press <menuchoice>
        <guimenu>Alt - F2</guimenu>
      </menuchoice> and type <guimenu>kdesu kcontrol</guimenu> in the input line:

<mediaobject>
        <imageobject>
          <imagedata fileref="01.png" format="PNG" align="center" />
        </imageobject>
        <textobject>
          <phrase>Mini-cli</phrase>
        </textobject>
      </mediaobject>

Press the button
<menuchoice>
        <guimenu>Run</guimenu>
      </menuchoice>
 to start the control center with root privileges.
       </para>
    <para>
 In both cases you'll be promted to give the root-password:
      </para>
    <para>
      <mediaobject>
        <imageobject>
          <imagedata fileref="10.png" format="PNG" align="center" />
        </imageobject>
        <textobject>
          <phrase>Please enter the root passphrase</phrase>
        </textobject>
      </mediaobject>
    </para>
    <para>
While starting, KNetworkConf tries to guess which platform you're using:
      </para>
    <para>
      <mediaobject>
        <imageobject>
          <imagedata fileref="02.png" format="PNG" align="center" />
        </imageobject>
        <textobject>
          <phrase>Which OS is used</phrase>
        </textobject>
      </mediaobject>
    </para>
    <para>
After that, the main window will be shown.
      </para>
<!--
/ I'm a comment line
-->    <sect1 id="MainWindow" >
      <title>Main program window</title>
      <para>

The main window is divided into the following pages: <guibutton>Network Interfaces</guibutton>, <guibutton>Routes</guibutton> and <guibutton>Domain Name System</guibutton>.
      </para>
      <para>
Let's stay on the page <guibutton>Network Interfaces</guibutton> to learn more about its options.
      </para>
      <sect2 id="Interfaces" >
        <title>Available Network Interfaces</title>
        <para>
In the list, all currently known interfaces are displayed:
      </para>
        <para>
          <mediaobject>
            <imageobject>
              <imagedata fileref="03.png" format="PNG" align="center" />
            </imageobject>
            <textobject>
              <phrase>Main-window</phrase>
            </textobject>
          </mediaobject>
        </para>
        <para>
The columns of the list offer different informations:
      </para>
        <table id="ListView" >
          <title>List Elements</title>
          <tgroup cols="2" align="char" >
            <thead>
              <row>
                <entry>Column</entry>
                <entry>Meaning</entry>
              </row>
            </thead>
            <tbody>
              <row>
                <entry>Interface</entry>
                <entry>Shows the name of the network interfaces (ie. eth0, eth1,wlan0, etc)</entry>
              </row>
              <row>
                <entry>IP Address</entry>
                <entry>Shows the currently assigned IP address for every interface</entry>
              </row>
              <row>
                <entry>Protocol</entry>
                <entry>Shows the boot protocol which is used by the interfaces</entry>
              </row>
              <row>
                <entry>State</entry>
                <entry>Shows the current state (up or down) for every interface</entry>
              </row>
              <row>
                <entry>Comment</entry>
                <entry>Shows the (freely assignable) comment</entry>
              </row>
            </tbody>
          </tgroup>
        </table>
        <para>
It is important to understand, that KNetworkConf is not intended to configure the hardware and its drivers, but only the software network settings to use the device(s) in your network.
      </para>
        <para>
The hardware gets most often configured while installing Linux. If you add further hardware after the installation, you can load the drivers by editing the file <screen>
            <prompt>/etc/modules.conf</prompt>
          </screen> (until Kernel 2.4) or the file <screen>
            <prompt>/etc/modprobe.conf</prompt>
          </screen> (for Kernel from 2.6).
      </para>
        <para>
For changing an interface, select it in the list. The changes can be made by one of the two buttons <guibutton>Enable/Disable interface</guibutton> and <guibutton>Configure Interface</guibutton>.
      </para>
        <para>
The button <guibutton>Enable/Disable interface</guibutton> starts and stops an interface. This means, that your computer will not use the interface for network traffic. No packets are transmitted or sent over an interface when it's down. The computer is not reachable from the network over this interface.
      </para>
        <para>
In the list, the current status for every device is displayed in the column <guibutton>Status</guibutton>.
      </para>
        <para>
As soon as you select an interface from the list, you can use the button <guibutton>Configure...</guibutton> to define the parameters for this interface:
      </para>
        <para>
          <mediaobject>
            <imageobject>
              <imagedata fileref="04.png" format="PNG" align="center" />
            </imageobject>
            <textobject>
              <phrase>Interface configuration dialog</phrase>
            </textobject>
          </mediaobject>
        </para>
        <para>
First of all,  you can select the behaviour of the network interface at boot time from the Boot Protocol combo box. The following options are available:
      </para>
        <para>
          <itemizedlist>
            <listitem>
              <para>
                <guibutton>Manual</guibutton> makes the device to read the locally configured values during boot time
        </para>
            </listitem>
            <listitem>
              <para>
                <guibutton>dhcp</guibutton> makes the device to look for a DHCP server during boot time, which offers the configuration (like IP address and netmask) for the device
        </para>
            </listitem>
            <listitem>
              <para>
                <guibutton>bootp</guibutton> makes the device to load the whole operating system via the network when switching on the computer. This is often used for computers without an operating system of their own installed. Such computers often also lack any mass storage device and are usually called Thin client
        </para>
            </listitem>
          </itemizedlist>
        </para>
        <para>
The option <guibutton>Enable at boot time</guibutton> starts the device automatically during the computer's boot time. You then have to start the interface manually after the computer has started to use it.
      </para>
        <para>
In the section <guibutton>Basic Device Information</guibutton> you'll find two of the most important settings. On <guibutton>IP-Address</guibutton> and <guibutton>Netmask</guibutton>, you enter the IP-address and the netmask to use. See the section <link linkend="KNetworkConf-tech" >Technical Informations</link> for help selecting the right values. The popup menu offers some reasonable preconfigured values for the netmask.
      </para>
        <para>
If you want to add a free netmask, click on the button <guibutton>Advanced...</guibutton>. This will show more options and change the popup menu <guibutton>Netmask:</guibutton> to a combo box, so you can enter a free netmask:
      </para>
        <para>
          <mediaobject>
            <imageobject>
              <imagedata fileref="05.png" format="PNG" align="center" />
            </imageobject>
            <textobject>
              <phrase>Free netmask</phrase>
            </textobject>
          </mediaobject>
        </para>
        <para>
Additionally, you can now enter a free comment for the device, and you can define a broadcast address. See the section <link linkend="KNetworkConf-tech" >Technical Informations</link> if you do not know what broadcast addresses are.
      </para>
        <para>
Click on the button <guibutton>OK</guibutton> to confirm your settings.
      </para>
      </sect2>
    </sect1>
<!--
/ I'm a comment line
-->    <sect1 id="Routing" >
      <title>Routes</title>
      <para>
Switch to the page <guibutton>Routes</guibutton>.
      </para>
      <para>
Here you can add the IP address of the default gateway which grants your network internet connectivity. If you do not know anything about gateways, please ask your network administrator for the correct IP address, or see the section <link linkend="KNetworkConf-tech" >Technical Informations</link> for further details.
      </para>
      <para>
If your computer offers more than one network interface, please select the interface which is connected to the gateway computer.
      </para>
    </sect1>
<!--
/ I'm a comment line
-->    <sect1 id="Domain" >
      <title>Domain Name System</title>
      <para>
Switch to the page <guibutton>Domain Name System</guibutton>.
      </para>
      <para>
        <mediaobject>
          <imageobject>
            <imagedata fileref="07.png" format="PNG" align="center" />
          </imageobject>
          <textobject>
            <phrase>Domain dialog</phrase>
          </textobject>
        </mediaobject>
      </para>
      <para>
Here you can configure the Host- and domain name, nameservers, their priority and keep a list of known hosts.
      </para>
      <sect2 id="host-and-domain-name" >
        <title>Host and domain name</title>
        <para>
Here you define the host and the domain names. If your computer is not reachable from the internet, you can choose any names here.
      </para>
      </sect2>
      <sect2 id="name-servers" >
        <title>Nameservers</title>
        <para>
Here you enter your nameservers. If you have, for example, booked an internet connection from any provider, the provider usually offers you one or more name servers. Consult the webpages of your provider to get the IP addresses for its nameservers.
      </para>
        <para>
Nameservers are needed to convert your requests (like www.google.com) into the respective IP-addresses, which will be used to get the desired page.
      </para>
        <para>
Use the <guibutton>Up</guibutton> and <guibutton>Down</guibutton> arrows which enable you to move the nameservers in the list. It is useful to put the fastest and most solid nameserver to the top, because the name servers are asked from top to buttom. In the case that the first server in the list cannot get the IP address of a given URL, the next server gets asked.
      </para>
        <para>
Use the buttons <guibutton>Add</guibutton> and <guibutton>Remove</guibutton> to add and remove nameservers.
      </para>
        <para>
Please pay attention to the table <link linkend="resolv.conf" >Where to find resolv.conf</link> to learn more where this information is stored on your system.
      </para>
      </sect2>
      <sect2 id="known-hosts" >
        <title>Known hosts</title>
        <para>
If you have only few computers in your network, you can add their names and IP addresses to the list of <guibutton>Known Hosts</guibutton>
        </para>
        <para>
          <mediaobject>
            <imageobject>
              <imagedata fileref="08.png" format="PNG" align="center" />
            </imageobject>
            <textobject>
              <phrase>List of known hosts</phrase>
            </textobject>
          </mediaobject>
        </para>
        <para>
If you have such a list on every machine in your network, you are not in need to set up a nameserver of your own, and every computer is reachable using its hostname instead of its IP address.
      </para>
        <para>
But in larger Networks, this method is unconvenient, because it is to much work to keep these files up to date on every machine.
      </para>
        <para>
Please note, that you can assign every IP address not only one, but also multiple names when desired.
      </para>
      </sect2>
      <sect2 id="known-host-edit" >
        <title>Editing the list of known hosts</title>
        <para>
Use the buttons <guibutton>Add</guibutton>, <guibutton>Edit</guibutton> and <guibutton>Remove</guibutton> to manage this list. When you choose <guibutton>Add</guibutton> or <guibutton>Edit</guibutton>, the following dialog will appear:
      </para>
        <para>
          <mediaobject>
            <imageobject>
              <imagedata fileref="09.png" format="PNG" align="center" />
            </imageobject>
            <textobject>
              <phrase>Known hosts edit dialog</phrase>
            </textobject>
          </mediaobject>
        </para>
        <para>
Please pay attention to the table <link linkend="hosts" >Where to find the file hosts</link> to learn more where this information is stored on your system.
      </para>
      </sect2>
    </sect1>
    <sect1 id="About" >
      <title>About-Dialog</title>
      <para>
In the about box, you'll find information about the current program version, the homepage, the author and some contributors as well as the license:
      </para>
      <para>
        <mediaobject>
          <imageobject>
            <imagedata fileref="about1.png" format="PNG" align="center" />
          </imageobject>
          <textobject>
            <phrase>About-Box</phrase>
          </textobject>
        </mediaobject>
      </para>
      <para>
Clicking the URL in the dialog will directly take you to homepage of KNetworkConf.
      </para>
    </sect1>
  </chapter>
  <chapter id="installation" >
    <title>Installation</title>
    <sect1 id="requirements" >
      <title>Requirements</title>
      <para>
You need KDE 3.x and QT 3.x installed to use KNetworkConf.
      </para>
      <para>
KNetworkConf can be used with the following platforms:
      </para>
      <itemizedlist>
        <listitem>
          <para>Conectiva</para>
        </listitem>
        <listitem>
          <para>Debian</para>
        </listitem>
        <listitem>
          <para>Fedora Core</para>
        </listitem>
        <listitem>
          <para>FreeBSD</para>
        </listitem>
        <listitem>
          <para>Gentoo</para>
        </listitem>
        <listitem>
          <para>Mandrake</para>
        </listitem>
        <listitem>
          <para>PLD</para>
        </listitem>
        <listitem>
          <para>OpenNA</para>
        </listitem>
        <listitem>
          <para>Red Hat</para>
        </listitem>
        <listitem>
          <para>SuSE</para>
        </listitem>
      </itemizedlist>
    </sect1>
    <sect1 id="how-to-obtain-KNetworkConf" >
      <title>How to obtain KNetworkConf</title>
      <para>
KNetworkConf's home page is at


<ulink url="http://knetworkconf.sourceforge.net" >http://knetworkconf.sourceforge.net</ulink>
where you at least can download source packages.
      </para>
    </sect1>
    <sect1 id="installing-binaries" >
      <title>Installing binaries</title>
      <para>
      When using the binary distributions (most often rpm packages), it is enough to have the KDE and QT binaries installed.
      </para>
      <para>
Installing binaries is recommended for less experienced users. Simply download the rpm packages. Install them by typing

<screen>
          <prompt>bash:</prompt>
          <userinput>
            <command>rpm -i knetworkconf-versionnumber.rpm</command>
          </userinput>
        </screen>

or using a graphical frontend like <application>kpackage</application> or the installation tool of your distribution.

      </para>
    </sect1>
    <sect1 id="compilation-and-installation" >
      <title>Compilation and Installation</title>
      <para>
In this case, it is not enough to have the binaries of QT and KDE installed; you also need the development packages which include libraries and other stuff.
      </para>
      <para>
      Recommended for advanced users only. Otherwise, compiling KNetworkConf is not difficult. The following commands should do it. Please note that <screen>
          <prompt>make install</prompt>
        </screen> has to be executed as user root:
      <screen>
          <prompt>bash:</prompt>
          <userinput>
            <command>./configure --prefix=$(kde-config --prefix)</command>
          </userinput>
          <prompt>bash:</prompt>
          <userinput>
            <command>make</command>
          </userinput>
          <prompt>bash:</prompt>
          <userinput>
            <command>make install</command>
          </userinput>
        </screen>
      </para>
      <para>That should do it. Should you run into any problems,
	please let us know.</para>
    </sect1>
  </chapter>
  <chapter id="KNetworkConf-tech" >
    <title>Technical Informations</title>
    <para>
In the first section of this chapter, you'll find some valuable information about networking basics. In the second, all configuration files on your disk which can be changed by KNetworkConf will be discussed.
    </para>
    <sect1 id="networking-overview" >
      <title>IPv4 Networking</title>
      <para>
This section cannot be a replacement for further lecture of IP-Networking. In this appendix, you'll only find the basic informations to get you started integrating your machine into a small (home) network.
    </para>
      <para>
Currently, IP-networking is done using TCP/IP version 4 (IPv4). IPv5 has never been used much. IPv6 is expected to get spread in the near future. So, this manual is based on the currently most spread IPv4.
    </para>
      <para>
One of the most important informations for setting up an interface is the IP-address which you have to assign to the interface. In foreign networks, e.g. your office, you have to ask the network administrator to tell you a valid IP-address, or you can use DHCP if this is available.
In any case, you are not allowed to simply choose any IP-address!
    </para>
      <para>
If you want to set up a small (home) network of your own, you should use IP-addresses from a range which has especially reserved for this purpose to prevent IP-address-conflicts with the global (internet) network. The addresses from the table shown below are not routed in the internet, so it is save to use them as you like.
    </para>
      <para>
Of course these machines can later be configured for internet access by using a gateway machine.
    </para>
      <para>
You can freely use the following addresses:
    </para>
      <table id="private-ip-addresses" >
        <title>IP-Addresses for private networks</title>
        <tgroup cols="2" align="char" >
          <thead>
            <row>
              <entry>Class</entry>
              <entry>Range</entry>
            </row>
          </thead>
          <tbody>
            <row>
              <entry>A</entry>
              <entry>10.0.0.0 to 10.255.255.255</entry>
            </row>
            <row>
              <entry>B</entry>
              <entry>172.16.0.0 to 172.31.0.0</entry>
            </row>
            <row>
              <entry>C</entry>
              <entry>192.168.0.0 to 192.168.255.0</entry>
            </row>
          </tbody>
        </tgroup>
      </table>
      <para>
For smaller networks, the most often used addresses are these in the range of 192.168.1.1 to 192.168.1.254. This is enough for networks up to over 250 computers.
    </para>
      <para>
Furthermore, the netmask is most often set to 255.255.255.0, so that all of these machines are members of the same subnet.
    </para>
      <para>
Some addresses are reserved for special things, e.g. 0.0.0.0 and 127.0.0.1. The first one is the so called default route, the second the loopback address. The default route is needed by IP routing.
    </para>
      <para>
The network 127.0.0.1 is reserved for the IP-traffic which works on the local machine only. Usually, the address 127.0.0.1 is assigned to a special device, the so called loopback interface, which works like a closed circle.
    </para>
      <para>
A default gateway is a computer which connects two different networks. If you have configured a small network of your own, it is most likely that you want all (or some) of your machines to grant internet access. But this is not possible directly, because these machines use local private IP-addresses, which are not routed in the internet.
The solution is a computer which translates between the two different networks. This computer uses at least two interfaces. One of them, maybe an ethernet card, points to the local network, the other one, maybe an ISDN card, points to the internet. In this case, both interfaces use different IP-addresses.
This computer performs a so called network address translation (NAT, aka IP-forwarding). To enable a local machine the internet access, you have only to tell them the default gateway, the local IP-address of the gateway-computer.
    </para>
    </sect1>
    <sect1 id="list-of-configuration-files" >
      <title>Configuration files</title>
      <para>
In this section you'll find the configuration files which are touched by KNetworkConf and where they reside in the filesystem of the different distributions.
    </para>
      <sect2 id="resolv.conf" >
        <title>resolv.conf</title>
        <para>
In this file, the list of name servers is stored.
    </para>
        <table id="resolv.conf-table" >
          <title>Where to find resolv.conf</title>
          <tgroup cols="3" align="char" >
            <thead>
              <row>
                <entry>Platform</entry>
                <entry>Release number</entry>
                <entry>Location</entry>
              </row>
            </thead>
            <tbody>
              <row>
                <entry>Conectiva</entry>
                <entry>9.2</entry>
                <entry>/etc/resolv.conf</entry>
              </row>
              <row>
                <entry>Debian</entry>
                <entry>3.0</entry>
                <entry>/etc/resolv.conf</entry>
              </row>
              <row>
                <entry>Fedora Core</entry>
                <entry>1</entry>
                <entry>/etc/resolv.conf</entry>
              </row>
              <row>
                <entry>FreeBSD</entry>
                <entry>5</entry>
                <entry>/etc/resolv.conf</entry>
              </row>
              <row>
                <entry>Gentoo</entry>
                <entry/>
                <entry>/etc/resolv.conf</entry>
              </row>
              <row>
                <entry>Mandrake</entry>
                <entry>9.2</entry>
                <entry>/etc/resolv.conf</entry>
              </row>
              <row>
                <entry>PLD</entry>
                <entry>2.0</entry>
                <entry>/etc/resolv.conf</entry>
              </row>
              <row>
                <entry>OpenNA</entry>
                <entry>1.0</entry>
                <entry>/etc/resolv.conf</entry>
              </row>
              <row>
                <entry>Red Hat</entry>
                <entry>9.0</entry>
                <entry>/etc/resolv.conf</entry>
              </row>
              <row>
                <entry>SuSE</entry>
                <entry>9.0</entry>
                <entry>/etc/resolv.conf</entry>
              </row>
            </tbody>
          </tgroup>
        </table>
        <para>
This file is sometimes dynamically changed by DSL-connections, so do not wonder if the file doesn't contain what you have put there when a DSL connection is established.
    </para>
      </sect2>
      <sect2 id="hosts" >
        <title>hosts</title>
        <para>
In this file, the list of known hosts is stored.
    </para>
        <table id="hosts-table" >
          <title>Where to find the file hosts</title>
          <tgroup cols="3" align="char" >
            <thead>
              <row>
                <entry>Distribution</entry>
                <entry>Releasenumber</entry>
                <entry>Location</entry>
              </row>
            </thead>
            <tbody>
              <row>
                <entry>Conectiva</entry>
                <entry>9.0</entry>
                <entry>/etc/hosts</entry>
              </row>
              <row>
                <entry>Debian</entry>
                <entry>3.0</entry>
                <entry>/etc/hosts</entry>
              </row>
              <row>
                <entry>Fedora Core</entry>
                <entry>1</entry>
                <entry>/etc/hosts</entry>
              </row>
              <row>
                <entry>FreeBSD</entry>
                <entry>5</entry>
                <entry>/etc/hosts</entry>
              </row>
              <row>
                <entry>Gentoo</entry>
                <entry/>
                <entry>/etc/hosts</entry>
              </row>
              <row>
                <entry>Mandrake</entry>
                <entry>9.2</entry>
                <entry>/etc/hosts</entry>
              </row>
              <row>
                <entry>PLD</entry>
                <entry>2.0</entry>
                <entry>/etc/hosts</entry>
              </row>
              <row>
                <entry>OpenNA</entry>
                <entry>1</entry>
                <entry>/etc/hosts</entry>
              </row>
              <row>
                <entry>Red Hat</entry>
                <entry>9.0</entry>
                <entry>/etc/hosts</entry>
              </row>
              <row>
                <entry>SuSE</entry>
                <entry>9.0</entry>
                <entry>/etc/hosts</entry>
              </row>
            </tbody>
          </tgroup>
        </table>
        <para>
On SuSE it is known that this file gets occasionally resorted by the script SuSEconfig. So do not wonder if you do not find in a state you have expected.
    </para>
      </sect2>
    </sect1>
  </chapter>
  <chapter id="questionsanswersandtips" >
    <title>Questions, Answers and Tips</title>
    <qandaset id="faq" >
      <title>Frequently asked questions</title>
      <qandaentry>
        <question>
          <para>I'd like to contribute. How can I do so?</para>
        </question>
        <answer>
          <para>Please note that KNetworkConf is still early stage. So, please do not do unasked tasks like translation or anything else. Maybe, tomorrow something will change and you have spent your worthy time doing something useless.
Of course, we will need some help, please contact us when interested.</para>
        </answer>
      </qandaentry>
      <qandaentry>
        <question>
          <para>
How can I start KNetworkConf after installation?
	  </para>
        </question>
        <answer>
          <para>
In KDE, you can use the key combo <guimenu>Alt - F2</guimenu> and type <guimenu>kdesu knetworkconf</guimenu>. But also your K-menu should contain a matching entry after installation.
	  </para>
          <para>
On the other hand, some distributions change the behaviour of the K-Menu, so it can be that our entry is missing after the installation.
	  </para>
        </answer>
      </qandaentry>
    </qandaset>
  </chapter>
  <chapter id="credits-licence" >
    <title>Credits and license</title>
    <sect1 id="credits" >
      <title>Credits</title>
      <para>
Thanks to all who have worked on KNetworkConf:
    </para>
      <itemizedlist>
        <listitem>
          <para>Juan Luis Baptiste <email>juan.baptiste@kdemail.net</email>
          </para>
        </listitem>
        <listitem>
          <para>David Sansome <email>me@davidsansome.com</email>
          </para>
        </listitem>
        <listitem>
          <para>Carlos Garnacho <email>garnacho@tuxerver.net</email>
          </para>
        </listitem>
        <listitem>
          <para>Simon Edwards <email>simon@simonzone.com</email>
          </para>
        </listitem>
        <listitem>
          <para>Pedro Jurado Maquedo <email>pjmelenas@biwemail.com</email>
          </para>
        </listitem>
        <listitem>
          <para>Florian Fernandez <email>florian.fernandez2@wanadoo.fr</email>
          </para>
        </listitem>
        <listitem>
          <para>Unai Garro <email>Unai.Garro@ee.ed.ac.uk</email>
          </para>
        </listitem>
        <listitem>
          <para>Christoph Eckert <email>mchristoph.eckert |at| t-online.de</email>
          </para>
        </listitem>
        <listitem>
          <para>Jaime Torres <email>jtorres@telecorp.net</email>
          </para>
        </listitem>
        <listitem>
          <para>All the others which I have forgotten to list here ;-) - you know who you are <email>you@foo.tld</email>
          </para>
        </listitem>
      </itemizedlist>
    </sect1>
    <sect1 id="licence" >
      <title>License</title>
      <para>
The Copyright on KNetworkConf at least for the years 2003 and 2004 is by Juan Luis Baptiste: <email>juan.baptiste@kdemail.net</email>.
    </para>
      <para>
KNetworkConf was published under the terms and conditions of the GNU General Public License (GPL).
    </para>
      <para>
The Copyright of this documentation for KNetworkConf at least for the year 2004 is by Christoph Eckert: <email>mchristoph.eckert |at| t-online.de</email>.
    </para>
      <para>
This documentation was published under the terms and conditions of the GNU Free Documentation License (FDL).
    </para>
      <para>
You'll find both licenses in your KDE-Installation. Have a look into the directory /$KDEDIR/share/doc/HTML/en/common.
    </para>
    </sect1>
  </chapter>
  <chapter id="glossary" >
    <title>Glossary</title>
    <para>
In this glossary there are some often needed things described shortly.
    </para>
    <table id="glossary-table" >
      <title>Glossary</title>
      <tgroup cols="2" align="char" >
        <thead>
          <row>
            <entry>Term</entry>
            <entry>Description</entry>
          </row>
        </thead>
        <tbody>
          <row>
            <entry>TCP/IP</entry>
            <entry>Transmission Control Protocol / Internet Protocol. The internet is based on this networking protocol</entry>
          </row>
          <row>
            <entry>IP-Address</entry>
            <entry>Computers in a TCP/IP-networkare identified by a unique number in dotted quad notation. Example: 192.168.1.170</entry>
          </row>
          <row>
            <entry>Netmask</entry>
            <entry>Netmasks are used to divide multiple machines in a network into subgroups. Example: 255.255.255.0</entry>
          </row>
          <row>
            <entry>Fill</entry>
            <entry>me with content</entry>
          </row>
        </tbody>
      </tgroup>
    </table>
  </chapter>
</book>