Now we are on the same page. Loved the farm analogy. :(
As I just found out, netflow only seems to create the virtual interface if you enter a port on the "Local Collector UDP port line". The note below it "[default port is 2055]" is deceiving making one think that if a port is not specified then 2055 is used. Not true. Now I see 2055 (or some other port) must be entered for the virtual NIC to be created.
Perhaps the plug-in config page should read "[You must enter a port, 2055 is default]". Please consider that a feature request. ;)
Tony
------------------------
Whoa
Please put pigs in the sty and horses in the barn.
When you tell ntop to accept netFlow data, it CREATES a pseudo device at
that time and listens on the physical interface(s) for netFlow packets.
That's completely separate from the issue of telling ntop about it's
physical interfaces so it can classify traffic from them.
Although it's all farm related, as you would use -m to tell ntop about local
addresses from both physical and virtual (pseudo) devices. (Think of the
virtual interface address on the netFlow plugin as equivalent to ONE address
on the -m parameter).
-----Burton
________________________________________________________________________
This email has been scanned for all viruses by the MessageLabs Email
Security System. For more information on a proactive email security
service working around the clock, around the globe, visit
http://www.messagelabs.com
________________________________________________________________________
