From: Arne Fitzenreiter <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 103aa06884f0d4a29e041545f091546fd384d654
Date: Wed, 10 Apr 2024 05:11:19 +0000 [thread overview]
Message-ID: <4VDrX80cHTz2xZ6@people01.haj.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1747 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 103aa06884f0d4a29e041545f091546fd384d654 (commit)
via 76ba16aef070d5efd10325b8a34a134ec04dcaf2 (commit)
from 833d42fed0d733952a95b98e016d0560b5142e1d (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 103aa06884f0d4a29e041545f091546fd384d654
Merge: 833d42fed0 76ba16aef0
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Wed Apr 10 07:11:02 2024 +0200
Merge remote-tracking branch 'origin/master' into next
-----------------------------------------------------------------------
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 dc142d690..041082b04 100644
--- a/config/suricata/suricata.yaml
+++ b/config/suricata/suricata.yaml
@@ -1118,7 +1118,7 @@ stream:
#memcap-policy: ignore
checksum-validation: yes # reject incorrect csums
midstream: true
- midstream-policy: pass-packet
+ midstream-policy: pass-flow
inline: auto # auto will use inline mode in IPS mode, yes or no set it statically
bypass: yes # Bypass packets when stream.reassembly.depth is reached.
reassembly:
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2024-04-10 5:11 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=4VDrX80cHTz2xZ6@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