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. |

| Subject: | Re: [Snort-users] Alert payloads not matching alert rules |
|---|---|
| Date: | Mon, 27 Nov 2006 16:10:17 -0500 |
-----Original Message----- Subject: Re: [Snort-users] Alert payloads not matching alert rules
For Joel's question : is there any reliable way to get know much traffic
is dropped ? Does this
information appear in the output of the "performance" preprocessor ?
You can send a USR1 signal to each of the Snort processes and Snort will dump stats to syslog, including a dropped packet percentage.* The way I collect this data is I have a very simple script that runs hourly. Each snort.conf file for each instance of snort specifies the pidfile by interface (snort_eth1.pid, snort_eth2.pid, etc.). This comes in handy for creating a history of packet loss by interface. It's not pretty, but it's short: #!/bin/sh for iface in eth1 eth2 eth3 do pid=`cat /var/run/snort_$iface.pid` kill -USR1 $pid grep Dropped /var/log/messages |grep $pid >> /var/log/snort/$iface_drops.txt done The file looks something like: Nov 27 00:00:01 petunia snort[14664]: Dropped: 0(0.000%) Nov 27 00:01:02 petunia snort[14664]: Dropped: 3599(11.267%) BTW, if you discover a solution to your problem, please post back to the list with details. It sounds like there are a number of people with very similar configurations that are interested to hear what you find out. PaulM * This has been unreliable for me in the past using RedHat libpcap on REHL4. Snort will massively underestimate the number of packets it actually analyzed, skewing statistics wildly. This is very obvious when it's the case - statistics will often be mathematically impossible with percentages in the tens of thousands. YMMV. ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Snort-users mailing list Snort-users@lists.sourceforge.net Go to this URL to change user options or unsubscribe: https://lists.sourceforge.net/lists/listinfo/snort-users Snort-users list archive: http://www.geocrawler.com/redir-sf.php3?list=snort-users
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [Snort-users] Looooots of "Outstanding" and "Analyzed" packets - counter wrap ?, Andreas Maus |
|---|---|
| Next by Date: | December 1st Chicago 2600 Meeting Reminder, Steven McGrath |
| Previous by Thread: | Re: [Snort-users] Alert payloads not matching alert rules, Joel Esler |
| Next by Thread: | [Snort-users] Snort 2.6.1 Stops Logging, Colin Grady |
| Indexes: | [Date] [Thread] [Top] [All Lists] |