-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Welcome to the world of big pipes and limitations of current
technology :) If your trying to run NTOP on a border pipe to the the
internet, good luck expect to enter the VIP club of 2GB of ram
minimum. I would say for highly used OC3s 2 gigabytes of ram is a
starting point. anytime a user goes to a website that is one host to
add to the has, and if you have 30,000+ workstations surfing the web
the hash will grow quickly. so if 30,000 hosts visit 40 different
sites each thats a possible hash of 1.2million :)
- -----Original Message-----
From: f. Andrew Lawton [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, October 02, 2002 6:28 AM
To: [EMAIL PROTECTED]
Subject: [Ntop] Command line suggestions. Was "Large hash"
On Wed, 2002-10-02 at 12:02, Luca Deri wrote:
> Where are you running ntop? On a border gw? Make sure you use the
> proper options.
>
I'm running ntop on the monitor port of our border.
The command line is:
/usr/local/bin/ntop -i eth1 -u ntop -m (local ip)/(net mask) -d -S2
- -E
- -j -P /var/ntop
Eth1 is a stealth port. Ntop seems to grab an extra 8k every 5
seconds
until all available RAM is filled. The -S parameter seems to be the
problem no matter what value is used.
Is this a reasonable command line?
_______________________________________________
Ntop mailing list
[EMAIL PROTECTED]
http://lists.ntop.org/mailman/listinfo/ntop
-----BEGIN PGP SIGNATURE-----
Version: PGPfreeware 7.0.3 for non-commercial use <http://www.pgp.com>
iQA/AwUBPZw1va1GcDuKcUnvEQKhXACgpPXowBBV8zZSGbN2hEXaFHvNqJkAoOE9
EIb45+HrnaycawADDQO6abyY
=kn+g
-----END PGP SIGNATURE-----
