ntop works fine listening on an unnumbered interface where it's collecting packets.
At present, the netFlow collector will not work unnumbered - the packets have to be directed TO a specific address. I had done some Proof-of-concept stuff a while back - it's possible to make ntop sniff netFlow, like it sniffs dns packets. If you want to sponsor the work, contact me off list. As for the address to use, READ the docs/FAQ entry on this topic and the back traffic on this list. -----Burton ---------- Original Message ---------------------------------- From: "Naman Latif" <[EMAIL PROTECTED]> Reply-To: [EMAIL PROTECTED] Date: Wed, 12 Nov 2003 15:17:48 -0800 >Hi, >I am using Ntop 2.2.96 on Suse 8.2. >We are trying to configure NTOP as NetFlow collector. At this moment it >is configured to listen on 1 un-numbered interface for our internal >traffic. The un-numbered interface is a SPAN port on a switch and cannot >be used for any unicast (netFlow) traffic. >Is possible to run NTOP to > >1. Listen on an Un-numbered interface for All traffic >AND >2. Listen on a numbered interface for NetFlow traffic and ignore All >other traffic. > >Which address is supposed to be defined on "Virtual NetFlow Interface >network address" parameter ? > >Regards, >Naman > > > ____________________________________________________________ Free 20MB Web Site Hosting and Personalized E-mail Service! Get It Now At Doteasy.com http://www.doteasy.com/et/ _______________________________________________ Ntop mailing list [EMAIL PROTECTED] http://listgateway.unipi.it/mailman/listinfo/ntop
