Snort - the de facto standard for intrusion detection/prevention
the de facto standard in IPS  
Got Source? About Snort About Sourcefire Snort FAQ
Sourcefire Network Security - the creators of Snort
Snort News Snort Downloads Snort Rules Snort Docs Snort Training Snort Forums Snort Community Snort Store
Search Site
Search Rules
Account
email
password
not registered?
can't login?
user preferences
next up previous
Next: 3.22 How do I Up: 3 Configuring Snort Previous: 3.20 How do you

3.21 How do I use a remote syslog machine?

Add the syslog switch, -s, and put this statement syslog.conf: 

    auth.alert         @managmentserverIP

Look at your snort.conf file for more info on the facility and Priority settings.

Make sure you have syslogd on the management server configured to allow syslog over UDP. Under RedHat, you can do this by editing /etc/sysconfig/syslog and adding the following line: 

    SYSLOGD_OPTIONS="-r -m 0"
This will start syslogd with the mark interval set to 0 (turning it off) and set it to receive network connections.

Then restart syslog. ``man syslogd'' for more info. You might also want to investigate syslog-ng
(http://www.balabit.hu/en/downloads/syslog-ng/).

Example invocation of snort: 

    /usr/local/bin/snort -c /etc/snort/snort.conf -I -A full -s 192.168.0.2:514
    -i rl0
Note for Win32 users:

Frank Knobbe wrote a patch for Snort to allow you to use `-s $<$host$>$' on the command line under Windows without nullifying the snort.conf. In other words, Snort still uses all settings from snort.conf but in addition uses the host from `-s' to send syslog alerts to. You can find the patch at:

http://www.snort.org/dl/contrib/patches/win32syslog/

next up previous
Next: 3.22 How do I Up: 3 Configuring Snort Previous: 3.20 How do you
site feedback | Terms of Use | Privacy Policy | forum archives ©2008 Snort and Sourcefire are registered trademarks of Sourcefire, Inc. All rights reserved.