'conifg stateful' option

[Jeremy Hoel <jthoel () gmail com>]

We noticed that our snort boxes didn't trigger on a rule that was
reported by an upstream provider.  Taking the pcaps and playing them
back against a stock snort.conf shows that the rule triggers. Once of
the differences between the configs is that ours included "config
stateful". From most of the documentation, this is a holdover from the
stream4 processor and we are configured to use stream5 (2.9.5.5), but
when that statement was in the config, the udp packets wouldn't
trigger the rule.  Comment it out and it did.

Is that by design?

The manual (http://manual.snort.org/node58.html &
http://manual.snort.org/node16.html) mentions "Sets assurance mode for
stream (stream is established)." but I would think that would only
apply to tcp and it would continue to inspect udp either way since
state can never be established.

------------------------------------------------------------------------------
DreamFactory - Open Source REST & JSON Services for HTML5 & Native Apps
OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access
Free app hosting. Or install the open source package on any LAMP server.
Sign up and see examples for AngularJS, jQuery, Sencha Touch and Native!
http://pubads.g.doubleclick.net/gampad/clk?id=63469471&iu=/4140/ostg.clktrk
_______________________________________________
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://sourceforge.net/mailarchive/forum.php?forum_name=snort-users

Please visit http://blog.snort.org to stay current on all the latest Snort news!