It's also possible to fool ntop WRT to ps_drop in the structure. If it's increasing ntop assumes it's the total, if it doesn't increase between reads ntop assumes it's the # since last queried. There's no standard - different drivers report ps_drop differently.
-----Burton -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Simon Sent: Wednesday, August 31, 2005 2:16 PM To: [email protected] Subject: RE: [Ntop] % dropped (libpcap) increases over time Hi Burton, Thanks for your reply. Actually, I have already gone through what you have attached to your email from the FAQ. > A. Long Answer: There are four places packets drop "in" ntop. One in > the NIC, one in the OS kernel, one in the libpcap library and one > actually in ntop. I guess in my case, the packets do not drop in the NIC, because ifconfig reports no packet dropped; the packets do not drop in the OS kernel, because CPU usage is not high according to top; the packets do not drop in the ntop according to the traffic report from ntop. So, the packets are dropping in libpcap. I want to know why that happens? Anything that I can do to improve it? Also, what I don't understand is how come the %dropped (libpcap) keeps on increasing? Thanks, Simon <snip /> _______________________________________________ Ntop mailing list [email protected] http://listgateway.unipi.it/mailman/listinfo/ntop
