[Snort-users] FlexResp and react keyword

Rob Collins robtompc at ...131...
Sat Oct 6 11:11:02 EDT 2001


Having some trouble with the react keyword (and
probably the resp keyword??) with snort-1.8.1-RELEASE,
on Linux Mandrake 7.2 (kernel 2.2.17).

Details:
compile snort with './configure --enable-flexresp'
create a snort.conf file:
=========================
ruletype suspicious
{
  type log
  output log_tcpdump: suspicious.log
}
suspicious tcp any any -> 127.0.0.1 80 \
   (msg: "http attempt"; react: block, msg;)
=========================
mkdir /var/log/snort
run '/usr/local/bin/snort -dev -i lo -l /var/log/snort
-c ./snort.conf'
and run 'lynx localhost'

Results:
lynx gets the web page, takes exactly 104 packets.  I
was expecting snort to 'magically' block the
connection
I get a /var/log/snort/1006 at ...3712..., and
an empty alert file in the same dir.  Running
'/usr/local/bin/snort -dvr
/var/log/snort/1006\@0845-suspicious.log' I get:
===================================================
Log directory = 

        --== Initializing Snort ==--
TCPDUMP file reading mode.
Read network traffic from
"/var/log/snort/1006 at ...3712..." file.
snaplen = 1514
===================================================
After that it freezes, have to kill -9 it.  Running
'tcpdump -F /var/log/snort/1006\@0845-suspicious.log'
I get:
======================
tcpdump: illegal char 'o'
======================
the o is a lowercase o with a hat '^' over it.

So;
1> The rule is triggered, because snort creates the
logfile.  How come the react keyword doesn't block the
connection?
2> The logfile is unreadable.  Any idea why?

=====
--r
"Experience is that marvelous thing that enables you to recognize a mistake when you make it again." -- F. P. Jones

__________________________________________________
Do You Yahoo!?
NEW from Yahoo! GeoCities - quick and easy web site hosting, just $8.95/month.
http://geocities.yahoo.com/ps/info1




More information about the Snort-users mailing list