public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: "Peter Müller" <peter.mueller@link38.eu>
To: development@lists.ipfire.org
Subject: Re: Core116 - Guardian Priority Not Working
Date: Sat, 11 Nov 2017 19:12:33 +0100	[thread overview]
Message-ID: <20171111191233.5399f78e.peter.mueller@link38.eu> (raw)
In-Reply-To: <CAAKHBKmskd_0n08wPVWy=wQ+or9SK_0WGC=Tx9Lfd40A4rYKoQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1568 bytes --]

Hello,

could you please file this issue into a bug at:
	https://bugzilla.ipfire.org/

Thank you. :-)

Best regards,
Peter Müller

> Hi
> 
> I have Guardian set to only block Snort Priority Level 1 alerts but it's
> blocking Level 2 as well.
> 
> Alert:
> 
> [**] [1:2402000:4623] ET DROP Dshield Block Listed Source group 1 [**]
> [Classification: Misc Attack] [Priority: 2]
> 11/11-12:18:49.554499 77.72.82.7:53790 -> myip:4569
> TCP TTL:246 TOS:0x28 ID:53722 IpLen:20 DgmLen:40
> ******S* Seq: 0xFBE35F5A  Ack: 0x0  Win: 0x400  TcpLen: 20
> [Xref => http://feeds.dshield.org/block.txt]
> 
> syslog:
> 
> Nov 11 12:18:49 ipfire guardian[3955]: <info> Blocking 77.72.82.7 for 86400
> seconds...
> 
> /var/ipfire/guardian/guardian.conf:
> 
> # Autogenerated configuration file.
> # All user modifications will be overwritten.
> 
> # Log settings.
> LogFacility = syslog
> LogLevel = info
> 
> # IPFire related settings.
> FirewallEngine = IPtables
> SocketOwner = nobody:nobody
> IgnoreFile = /var/ipfire/guardian/guardian.ignore
> 
> # Configured block settings.
> BlockCount = 1
> BlockTime = 86400
> FirewallAction = DROP
> 
> # Enabled modules.
> Monitor_SSH = /var/log/messages
> Monitor_SNORT = /var/log/snort/alert
> Monitor_HTTPD = /var/log/httpd/error_log
> 
> # Module settings.
> SnortPriorityLevel = 1
> 
> Does anyone know of a fix?
> 
> Thanks,
> 
> Douglas Duckworth, MSc, LFCS
> HPC System Administrator
> Scientific Computing Unit
> Physiology and Biophysics
> Weill Cornell Medicine
> E: doug(a)med.cornell.edu
> O: 212-746-6305
> F: 212-746-8690



       reply	other threads:[~2017-11-11 18:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAAKHBKmskd_0n08wPVWy=wQ+or9SK_0WGC=Tx9Lfd40A4rYKoQ@mail.gmail.com>
2017-11-11 18:12 ` Peter Müller [this message]
     [not found] <CAAKHBKkst=2p37A23+kpaoQKc_w-BdoPizNeM9KKDzy3y2tZeA@mail.gmail.com>
2017-11-11 21:17 ` Matthias Fischer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20171111191233.5399f78e.peter.mueller@link38.eu \
    --to=peter.mueller@link38.eu \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox