In the startup sequence (you want to add -t 5 to force more messages),
there will be a couple about your NIC card identification.
Also, make sure you don't have an odd-ball/mismatched -i switch set to
force ntop to the 'wrong' card.
I'd guess that the 2nd NIC is being recognized as eth0, and you have -i
eth0 -- so ntop is trying to listen on a NIC w/o an IP address or one
that is on the wrong LAN segment. If you can't ping the ntop machine,
you have a network not ntop problem...
Finally, read the FAQ article on switched infrastructure - if you are
looking at the switched port to be your ntop monitor of the backbone,
you need to force the port to span (Cisco) mode or the equivalent or it
won't see any traffic.
-----Burton
Chris Harner wrote:
We decided to configure a second NIC with the server which is plugged
into the backbone (L3) switch. I came back and noticed that the NTop
page now fails to load. I restarted the ntop process and that did not
work. I re-ran the cron (/usr/bin/ntop) and it looks like it works, but
the page does not get hosted. I tried it on both addresses and it does
not work.
I enabled it to run as a daemon when it was working. ANy suggestions on
how i can get this working again? Thank you all.
------------------------------------------------------------------------
_______________________________________________
Ntop mailing list
[email protected]
http://listgateway.unipi.it/mailman/listinfo/ntop
_______________________________________________
Ntop mailing list
[email protected]
http://listgateway.unipi.it/mailman/listinfo/ntop
