From: Arne Fitzenreiter <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 551bc489408c1efc0d0899ead3894c3d04a0f300
Date: Wed, 08 Apr 2020 15:49:41 +0000 [thread overview]
Message-ID: <48y7xx4hnbz2y0q@people01.haj.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1611 bytes --]
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "IPFire 2.x development tree".
The branch, next has been updated
via 551bc489408c1efc0d0899ead3894c3d04a0f300 (commit)
from b8fcb4956758b88b8a46eff5641aa80f244ed605 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
commit 551bc489408c1efc0d0899ead3894c3d04a0f300
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Wed Apr 8 15:48:20 2020 +0000
suricata: disable dns flood protection
this causes errors in unbound and also other linux clients if
a dns rule triggers.
Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
config/suricata/suricata.yaml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Difference in files:
diff --git a/config/suricata/suricata.yaml b/config/suricata/suricata.yaml
index 1f33ea0f3..43f10c89d 100644
--- a/config/suricata/suricata.yaml
+++ b/config/suricata/suricata.yaml
@@ -435,7 +435,7 @@ app-layer:
# How many unreplied DNS requests are considered a flood.
# If the limit is reached, app-layer-event:dns.flooded; will match.
- request-flood: 2048
+ #request-flood: 512
tcp:
enabled: yes
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2020-04-08 15:49 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=48y7xx4hnbz2y0q@people01.haj.ipfire.org \
--to=git@ipfire.org \
--cc=ipfire-scm@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