ntop as it's own (limited) built in web server.  We've never had problems
with interactions.


-----Burton

(Please note that I am speaking only as an individual and not as a
representative of my employer) 

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
Brian Loe
Sent: Monday, July 10, 2006 9:21 AM
To: [email protected]
Subject: Re: [Ntop] request help on best practice

Ahh, so you can have them both export to the same nic and port and they'll
be combined. That may prove interesting in the future.
Basically I'm just wanting information on that particular ISP connection, so
I should only need to worry about exporting from the one router.

This server is also runing Cacti and Nagios - each, obviously, with their
own web interface. Any special considerations that need to be made there? I
had planned to use that same IP (new domain name) for the NTOP web interface
but seperate NICs to collect flow data (I have three "extra" NICs to choose
from, but I should be able to just choose different ports, right?).

On 7/8/06, Burton Strauss <[EMAIL PROTECTED]> wrote:
> However, I don't think your netFlow configuration will show all of the 
> traffic - you would need to have BOTH routers exporting their own 
> flows.  If you define two ntop netflow devices, then the traffic will 
> be displayed one at a time.  If you configure both netFlow devices to 
> export to the same ntop netflow device (i.e. port #), ntop will 
> combine them.  This may give the single point view you want.
>
_______________________________________________
Ntop mailing list
[email protected]
http://listgateway.unipi.it/mailman/listinfo/ntop

_______________________________________________
Ntop mailing list
[email protected]
http://listgateway.unipi.it/mailman/listinfo/ntop

Reply via email to