I can certainly understand that. In my setup I tried to have multiple virtual interfaces listening on the same udp port. This is because you can only configure a Cisco device to send netflow data to one IP address on one port (afaik you can't send to more than one collector ip or udp port). Or maybe anyone knows of a simple way to send netflow streams from Cisco to more than one udp port?
So at this point there is no way for me to break down netflow data by segments unless they come from deferent routers to different ports on ntop server. The other alternative solution, IMHO, to Cisco's (or ntop's) limitation is to use one(or two) of the flow-tools programs to collect and resend the same netflow data to different udp ports on ntop server. If anybody has a simpler idea/workaround I'll be happy to know. I appreciate all the input/clarification provided so far. Thanks, -Tomas On Thu, 31 Mar 2005 16:30:01 -0600, Burton Strauss <[EMAIL PROTECTED]> wrote: > Nothing intentional. It's probably an artifact of the > listen()/select()/bind() et al calls - that you can only have ONE active > connection to a port at a time. It's most likely the last, but I guess it > could be any - being undefined behavior and all. > > Chris is right - if you need to differentiate among netFlow streams, then > send them to different ports. Otherwise, just configure ONE listener and it > will 'magically' aggregate everything. > > -----Burton > _______________________________________________ Ntop-dev mailing list [email protected] http://listgateway.unipi.it/mailman/listinfo/ntop-dev
