Ethical Hacking

Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package.
Computer Forensics Training at InfoSec Institute

Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors.




Network Security Snort-Users
[Top] [All Lists]

RE: [Snort-users] packet loss

Subject: RE: [Snort-users] packet loss
Date: Wed, 29 Sep 2004 11:17:27 -0400
If you have plenty of cpu and  memory I am assuming you are not page
faulting, in which case you might just need to use the mmap version of
libpcap. It uses less cpu than the standard pcap, but also has much less
packet latency during sniffing so it does not drop as much.
 
 
 
-----Original Message-----
From: snort-users-admin@lists.sourceforge.net
[mailto:snort-users-admin@lists.sourceforge.net] On Behalf Of Larry
Wichman
Sent: Tuesday, September 28, 2004 10:14 AM
To: snort-users@lists.sourceforge.net
Subject: [Snort-users] packet loss
 
In the course of my testing of Snort I have averaged about 40% packet
loss. I am running Snort on Fedora. The segment I am monitoring is 100
mb and is very busy. Does anyone have any recommendations for tuning
Snort to not drop so many packets? Is there any recommendations for
hardware? The CPU is running at about 40% and the memory looks fine. 
 
~Larry
  _____  

Do you Yahoo!?
Yahoo!
<http://us.rd.yahoo.com/mail_us/taglines/50x/*http:/promotions.yahoo.com
/new_mail/static/efficiency.html>  Mail - 50x more storage than other
providers!
<Prev in Thread] Current Thread [Next in Thread>