Bajate ficheros necesarios de: http://whw3.pointclark.net:8080/index.php?option=com_docman&task=view_category&Itemid=1&subcat=7&catid=8&orderby=dmdatecounter&ascdesc=DESC

Transferir el fichero ntop-3[1].0-1.i386.rpm al directorio TMP (con el winscp podemos editar/tranferir/borrar/etc desde una

consola windows)

Tranferir tambien el modulo gdome2-0[1].8.1-1.i386.rpm al mismo directorio TMP

Instalar ambos RPMS (accediendo via SSH con Putty tambien desde consola windows a traves del puerto 22)

En primer lugar el Gdome

[root@gateway tmp]# rpm -ivh gdome2-0[1].8.1-1.i386.rpm

Preparing... ########################################### [100%]

1:gdome2

########################################### [100%]

En segundo lugar el Ntop

[root@gateway tmp]# rpm -ivh ntop-3[1].0-1.i386.rpm

Preparing... ########################################### [100% ]

1:ntop ########################################### [100%]

***********************************************************************

***********************************************************************

***********************************************************************

Creating default ntop config

Sat Oct 2 16:43:32 2004 Initializing gdbm databases

Sat Oct 2 16:43:32 2004 Now running as requested user '(null)' (0:0)

Please enter the password for the admin user:

Please enter the password again:

Sat Oct 2 16:43:45 2004 Admin user password has been set

***********************************************************************

Questions? See the FAQ in /usr/share/doc/ntop-<release>

ls: /usr/share/ntop/rrd/interfaces/*/hosts/: No such file or directory

***********************************************************************

***********************************************************************

* You may access the server at https://gateway.tecseg.com:3000/ *

* Please note: SSL is enable by default in this version *

***********************************************************************

***********************************************************************

* IT'S ALSO RECOMMEDED TO GENERATE A NEW CERT FOR NTOP *

* by using the command below *

***********************************************************************

/usr/bin/openssl req -new -x509 -nodes -days 365 -out /etc/ntop/ntop-cert.pem -keyout /etc/ntop/ntop-cert.pem

***********************************************************************

***********************************************************************

Generamos la RSA

[root@gateway tmp]# /usr/bin/openssl req -new -x509 -nodes -days 365 -out /etc/ntop/ntop-cert.pem -keyout /etc/ntop/ntop-cert.pem

Generating a 1024 bit RSA private key

.........++++++

....++++++

writing new private key to '/etc/ntop/ntop-cert.pem'

-----

You are about to be asked to enter information that will be incorporated

into your certificate request.

What you are about to enter is what is called a Distinguished Name or a DN.

There are quite a few fields but you can leave some blank

For some fields there will be a default value,

If you enter '.', the field will be left blank.

-----

Country Name (2 letter code) [GB]:ntop

string is too long, it needs to be less than 2 bytes long

Country Name (2 letter code) [GB]:service ntop start

string is too long, it needs to be less than 2 bytes long

Country Name (2 letter code) [GB]:ES

State or Province Name (full name) [Berkshire]:VALENCIA

Locality Name (eg, city) [Newbury]:GANDIA

Organiza tion Name (eg, company) [My Company Ltd]:SAFORWIRELESS

Organizational Unit Name (eg, section) []:

Common Name (eg, your name or your server's hostname) []:SAFORWIRELESS

Email Address []:inphower@gmail.com

y antes de levantar el servicio modificamos en /etc/ntop.conf en la linea "--user ntop" a "--user root".

(con el winscp podemos editar/tranferir/borrar/etc desde una consola windows)

Levantamos el servico y reiniciamos

[root@gateway tmp]# service ntop start [FAILED]

Starting ntop:

[root@gateway tmp]# reboot

Broadcast message from root (pts/0) (Sat Oct 2 16:55:22 2004):

The system is going down for reboot NOW!

Cuando vuelva a arrancar el servidor tendremos en https://xxx.xxx.xxx.xxx:3000 (atentos es https!!) un control

barbaro de todo lo que atraviesa nuestro Firewall.