From: Stefan Schantl <stefan.schantl@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH 00/20] Suricata Configuration Updates
Date: Fri, 01 Mar 2019 18:09:42 +0100 [thread overview]
Message-ID: <d431847e54c9f97aefedb8e7c758102bcee3da8d.camel@ipfire.org> (raw)
In-Reply-To: <20190228142825.5153-1-michael.tremer@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 2101 bytes --]
Hello Michael,
thanks for working on optimizing the suricata configuration file.
I've merged all of the patches except number "8" and "10" which does
not apply with "git am".
When simple adding the changes with "patch" the changes can be applied
- any idea why this happened?
Thanks in advance,
-Stefan
> I have worked on suricata's configuration.
>
> My objective was to use more system resources (because suricata did
> not use much RAM, etc.)
> to make it faster and to be able to have some deeper decoding and
> matching.
>
> Please review these changes and let me know what you think.
>
> All in all, suricata should not use more than 1G of RAM which I think
> is a very good
> amount. If your system is weaker than that, there is no point in
> running an IPS.
>
> On my system in my office, this runs with a hand full of rules
> enabled from the
> Emerging Threats Community set at around 110MB of RAM.
>
> Michael Tremer (20):
> Revert "Suricata: detect DNS events on port 853, too"
> suricata: Set max-pending-packets to 1024
> suricata: Set default packet size to 1514
> suricata: Set detection profile to high
> suricata: Drop profiling section from configuration
> suricata: Drop some commented stuff from configuration
> suricata: Drop sections that require Rust
> suricata: Configure HTTP decoder
> suricata: Allow 32MB of RAM for DNS decoding
> suricata: Drop parsers I have never heard of
> suricata: We do not use any IP reputation lists
> suricata: Log to syslog
> suricata: Use the correct path for the magic database
> suricata: Use 64MB of RAM for defragmentation
> suricata: Use up to 256MB of RAM for the flow cache
> suricata: Log to syslog like a normal process
> suricata: Increase memory size for the stream engine
> suricata: Disable decoding for Teredo
> suricata: Start capture first and then load rules
> suricata: Fix syntax error
>
> config/etc/syslog.conf | 2 +-
> config/suricata/suricata.yaml | 282 +++++---------------------------
> ----------
> 2 files changed, 30 insertions(+), 254 deletions(-)
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next parent reply other threads:[~2019-03-01 17:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190228142825.5153-1-michael.tremer@ipfire.org>
2019-03-01 17:09 ` Stefan Schantl [this message]
2019-03-01 17:18 ` Michael Tremer
2019-03-01 19:01 ` Stefan Schantl
2019-03-02 16:52 ` Michael Tremer
2019-03-02 17:19 ` Michael Tremer
2019-03-03 9:57 ` Stefan Schantl
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=d431847e54c9f97aefedb8e7c758102bcee3da8d.camel@ipfire.org \
--to=stefan.schantl@ipfire.org \
--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