Gary, thanks for the reply. Here's some more info. I've messed with --local-subnets on this one quite a bit. I've tried not setting it and using the /19 (where 90% of my hosts are) solely as the netflow interface virtual address. I've tried putting a bogus /24 as the netflow virtual address and again put one of my CIDRs in local-subnets. All to no avail.
As for the number of hosts, the network is very small. NTOP has only about 884 active end nodes monitored. I doubt I'm bumping into the 1024 limit. The split is as follows: There are 7 pages of IP hosts on the L-L report, 1 page of hosts on the L-R report and less than half a page on the R-L report. Nothing on the R-R report. In regards to the overall configuration, over the last 5 years I've used ntop on and off to pull utilization stats from these routers. There have been no changes to the netflow config there. I'm only using "ip flow ingress" on the interfaces where traffic is interesting. "ip flow egress" is not configured on any interfaces. Previous versions of ntop did not exhibit this behavior. However, this is the first time I've run it on Fedora 9 with v3.3.8 of ntop. Tony _______________________________________________ Ntop mailing list [email protected] http://listgateway.unipi.it/mailman/listinfo/ntop
