From: Stefan Schantl <stefan.schantl@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH 3/9] suricata: Define bypass mark
Date: Tue, 19 Oct 2021 06:03:20 +0200 [thread overview]
Message-ID: <5fa81bb91fbc4b7e044723bb783a7f4e96fe391f.camel@ipfire.org> (raw)
In-Reply-To: <20211018101022.15448-3-michael.tremer@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1213 bytes --]
Tested-by: Stefan Schantl <stefan.schantl(a)ipfire.org>
> Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
> ---
> config/suricata/suricata.yaml | 4 ++--
> src/initscripts/system/suricata | 2 ++
> 2 files changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/config/suricata/suricata.yaml
> b/config/suricata/suricata.yaml
> index 1ce013dc7..f02b93d76 100644
> --- a/config/suricata/suricata.yaml
> +++ b/config/suricata/suricata.yaml
> @@ -348,8 +348,8 @@ nfq:
> mode: repeat
> repeat-mark: 2147483648
> repeat-mask: 2147483648
> -# bypass-mark: 1
> -# bypass-mask: 1
> + bypass-mark: 1073741824
> + bypass-mask: 1073741824
> # route-queue: 2
> # batchcount: 20
> fail-open: yes
> diff --git a/src/initscripts/system/suricata
> b/src/initscripts/system/suricata
> index 111bd9df3..981471c7c 100644
> --- a/src/initscripts/system/suricata
> +++ b/src/initscripts/system/suricata
> @@ -37,6 +37,8 @@ enabled_ips_zones=()
> # Mark and Mask options.
> REPEAT_MARK="0x80000000"
> REPEAT_MASK="0x80000000"
> +BYPASS_MARK="0x40000000"
> +BYPASS_MASK="0x40000000"
>
> # PID file of suricata.
> PID_FILE="/var/run/suricata.pid"
next prev parent reply other threads:[~2021-10-19 4:03 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-18 10:10 [PATCH 1/9] suricata: Set most significant bit as repeat marker Michael Tremer
2021-10-18 10:10 ` [PATCH 2/9] suricata: Rename MARK/MASK to REPEAT_MARK/REPEAT_MASK Michael Tremer
2021-10-18 20:42 ` Peter Müller
2021-10-19 4:02 ` Stefan Schantl
2021-10-18 10:10 ` [PATCH 3/9] suricata: Define bypass mark Michael Tremer
2021-10-18 20:43 ` Peter Müller
2021-10-19 4:03 ` Stefan Schantl [this message]
2021-10-18 10:10 ` [PATCH 4/9] suricata: Enable bypassing unhandled streams Michael Tremer
2021-10-19 4:03 ` Stefan Schantl
2021-10-18 10:10 ` [PATCH 5/9] suricata: Always append rules instead of inserting them Michael Tremer
2021-10-19 4:03 ` Stefan Schantl
2021-10-18 10:10 ` [PATCH 6/9] suricata: Add rule to skip IPS if a packet has the bypass bit set Michael Tremer
2021-10-19 4:04 ` Stefan Schantl
2021-10-18 10:10 ` [PATCH 7/9] suricata: Store bypass flag in connmark and restore Michael Tremer
2021-10-19 4:04 ` Stefan Schantl
2021-10-18 10:10 ` [PATCH 8/9] suricata: Introduce IPSBYPASS chain Michael Tremer
2021-10-19 4:04 ` Stefan Schantl
2021-10-18 10:10 ` [PATCH 9/9] firewall: Keep REPEAT bit when saving rest to CONNMARK Michael Tremer
2021-10-19 4:05 ` Stefan Schantl
2021-10-18 20:42 ` [PATCH 1/9] suricata: Set most significant bit as repeat marker Peter Müller
2021-10-19 4:02 ` 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=5fa81bb91fbc4b7e044723bb783a7f4e96fe391f.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