Project

General

Profile

Actions
Copy link

Bug #2779

closed

Snort unexpectedly terminates / signal 11 error

Added by Cimpean Andrei almost 12 years ago. Updated almost 12 years ago.

Status:
Rejected
Priority:
Urgent
Assignee:
-
Category:
-
Target version:
-
Start date:
01/26/2013
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Affected Version:
Affected Plus Version:
Affected Architecture:

Description

Hello, It's not a hardware issue, I tested on several pc-s Intel and AMD processors, It seems to be a rule issue, When I put these two rules

#tcp
alert tcp !$HOME_NET any -> $HOME_NET ![27000:30000,9987] (flags: S; msg:"Possible TCP DoS"; flow: stateless; threshold: type both, track by_src, count 200, seconds 1; sid:10001;rev:1;)

#udp
alert udp !$HOME_NET any -> $HOME_NET ![27000:30000,9987] (msg:"Possible UDP DoS"; flow: stateless; threshold: type both, track by_src, count 300, seconds 1; sid:10002;rev:1;)

when the alert is triggerd snort is exiting on signal 11.

Those 2 rules were verry important to me, can you plese tell me an alternative to them or can you please solve this problem?

With the old snort package in pfsense those 2 rules worked just fine.

Thank you.

Actions
Copy link

Also available in: Atom PDF