root/trunk/README @ 108

 -----------------------------
|       Install resume        |
 -----------------------------

        $ tar xvzf renetcol-0.0.14beta.tar.gz
        $ cd renetcol-0.0.14beta
        {./configure  |  ./configure --enable-ipv4agg=no }
        Steps 1&2 , see below
        $ make
        $ make install (optional)

 ----------------------
| Step 1: before compil |
 ----------------------

OS requirements : Linux distribution (tested on Debian Etch and Ubuntu7.1)

You must changed some values in renetcolParam.h, values are detailed in the file.

IPC System V MUST be installed on your OS.

Specials packages requirements:
 - libc6-dev
 - libc6-prof
 - librrd{0|2}-dev (if aggregation enabled)
 
 -------------------------------------
| Step 2: before start                |
 -------------------------------------

   - create your IPv4 prefix/subnet file (or keep the default for test: 
conf/IPv4_prefix.txt). If you don't need aggregation you can keed the default 
and select "--enable-ipv4agg=no" in configure procedure
   
   - create your router list file *REQUIRED* 
          (exemple in conf/routers.txt):
     syntax: <id> <name> <first IPv4 address> <second IPv4 or NULL>

Note: no comment lines in this two files.


 ----------
| Commands |
 ----------

        ./renetcol ... : launch the collector (you must be root)
        ./renetcolSender ... : to use remote client
        ./renetcolMsgCtl ... : to kill the IPC message queue if you kill renetcol 

We recommand to use the script *check.sh* (in tool/) to launch renetcol. 
This script required in parameters the path to renetcol.
We can also put the script in your root crontab to verify the collector state, 
for exemple:
5,10,15,20,25,30,35,40,45,50,55 * * * * \
 /bin/sh <path>/renetcol-0.0.14beta/tool/check.sh <path>/renetcol-0.0.14beta/

 --------------------------
| Others Commands exemples |
 --------------------------

colnet:/tmp/renetcol_user/src# killall renetcol
colnet:/tmp/renetcol_user/src# killall renetcolSender
colnet:/tmp/renetcol_user/src# ./renetcolMsgCtl renetcol

 ----------------------------------
| Use the client tool (python+GTK) |
 ----------------------------------

    on Linux:
       cd tool
       python renetcolGUI.py
    on Win32:
       copy the file renetcolGUI.py on your system
       install python, GTK and requirements:
               for python:
                   http://www.python.org/ download section
               for pyGTK:
                   http://www.pcpm.ucl.ac.be/~gustin/win32_ports/
                   section pygtk on win32
               for GTK+:
                   http://gladewin32.sourceforge.net/

     *REQUIRED* Collector (renetcolSender) and remote client communication:
        you MUST change few values in the renetcolGUI.py file:
                - line 28 : path to GTK
                - line 47 to 53 : IP protocol choice and collector address

    *REQUIRED* In this release the client tool host MUST be have a
 reverse DNS for his name. If not the collector will not be able to 
communicate with the client. Explication: filters are registered on the 
collector in a file (rules.txt) in such way:
        N 53.renater.fr
        O socket 53.renater.fr 2222
        C 60 = 6
        
For your first action from the client to the collector it's possible to have a
 delay before the first flow view (>20s, it depends on the delay between two 
routers template definition) 

The client tool can be used on the collector box or in remote mode. You can 
used few clients instantiations (on differents remotes computers).