Sorry, I wasn't very clear. I meant the NetFlow timeouts set on the exporter. Shorter active and inactive timeouts will cause the exporter to expire flow cache entries more often thus increasing the flows per host rate.
On 7/14/05 12:12 PM, "Peter Valdemar Mørch" <[EMAIL PROTECTED]> wrote: > Thanks for your responses! > > Adam Powers apowers-at-lancope.com |Lists| wrote: >> Yeah, and your timeouts have a pretty significant impact as well. What are >> you using? > > NAT (or rather, PAT) translations time out after 3 hours, while TCP > connections time out after 1 hour. I guess if PAT timeout was tiny, like > 2 minutes, that would create many flows, because new PAT entries were > created on different ports all the time. Is that what you mean when you > say "pretty significant"? > > Jay, I was a bit unclear before. Yes I'm talking about 800 flows / > person / hour between the inside and the internet - not internally, > where it is bound to be higher! :-D > > Thanks for your data, Jay! We're trying to get an estimate of how huge > the data set is going to get, and so good estimates are very valuable > and your data points help! > > Peter _______________________________________________ Flow-tools mailing list [EMAIL PROTECTED] http://mailman.splintered.net/mailman/listinfo/flow-tools
