root/tags/renetcol-0.0.11/trunk/README

Revision 34, 3.0 KB (checked in by andreu, 16 years ago)

bug on bad reading of routers configuration file fixed
bug on wrong sampled value fixed
in tool, we add a supervisor script shell

  • Property svn:eol-style set to native
Line 
1 ----------------------
2|       Install        |
3 ----------------------
4
5        tar xvzf renetcol-0.0.9.tar.gz
6        cd renetcol-0.0.9
7        ./configure
8        (./configure --help)
9        (before the make command you MUST change some values in renetcol.h, see below)
10        make
11        make install (if you want)
12
13 --------------------------------------
14| Collector requirements before compil |
15 --------------------------------------
16
17Change the following values in renetcol.h *REQUIRED*:
18#define RECEPTION_ADDRESS "10.0.0.1"
19#define RECEPTION_PORT 9999
20(this two values are the values configured on your routers to export Netflow
21datagrams)
22
23 --------------------------------------
24| Collector requirements before start  |
25 --------------------------------------
26
27        - create your IPv4 prefix file (or keep the default for test:
28IPv4_prefix.txt, in "quick start" with "--enable-ipv4agg=no" you don't
29need a such file
30        - create your router list file *REQUIRED* (exemple in src/routers.txt):
31syntax: <id> <name> <first IPv4 address> <second IPv4 or NULL>
32keep this first line: 0 null 0.0.0.0 null
33
34Note: no comment lines in this two files.
35
36
37 ----------
38| Commands |
39 ----------
40
41        ./renetcol ... : launch the collector (you must be root)
42        ./renetcolSender ... : to use remote client
43        ./renetcolMsgCtl ... : to kill the message queue if you kill renetcol 
44
45 -------------------
46| Commands exemples |
47 -------------------
48
49colnet:/tmp/renetcol_user/src# ./renetcol routers.txt IPv4_prefix.txt rules.txt
50
51colnet:/tmp/renetcol_user/src# ./renetcolSender renetcol 1 rules.txt
52
53colnet:/tmp/renetcol_user/src# killall renetcol
54colnet:/tmp/renetcol_user/src# killall renetcolSender
55colnet:/tmp/renetcol_user/src# ./renetcolMsgCtl renetcol
56
57We recommand to use in a crontab the script check.sh who is in tool/ directory.
58
59 ----------------------------------
60| Use the client tool (python+GTK) |
61 ----------------------------------
62
63    on Linux:
64       cd tool
65       python renetcolGUI_0_0_7.py
66    on Win32:
67       copy the file renetcolGUI_0_0_7.py on your system
68       install python, GTK and requirements:
69               for python:
70                   http://www.python.org/ download section
71               for pyGTK:
72                   http://www.pcpm.ucl.ac.be/~gustin/win32_ports/
73                   section pygtk on win32
74               for GTK+:
75                   http://gladewin32.sourceforge.net/
76
77    Collector (renetcolSender) and remote client communication *REQUIRED*:
78        you MUST change few values in the renetcolGUI_0_0_7.py file:
79                - line 28 : path to GTK
80                - line 47 to 53 : IP protocol choice and collector address
81
82    *REQUIRED* In this release (0.0.9) the client tool host MUST be have a
83 reverse DNS for his name. If not the collector will not be able to
84communicate with the client. Explication: the rules are registered on the
85collector in the conf file (rules.txt) in such way:
86        N 53.renater.fr
87        O socket 53.renater.fr 2222
88        C 60 = 6
89It's not a requirement for rules applied directly in this file (with an
90editor).
91       
92    Note: For your first action from the client to the collector it's
93possible to have a delay (>20s, it depends on the delay between two template
94definition).
Note: See TracBrowser for help on using the browser.