From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: [PATCH 7/9] suricata: Store bypass flag in connmark and restore
Date: Mon, 18 Oct 2021 10:10:20 +0000 [thread overview]
Message-ID: <20211018101022.15448-7-michael.tremer@ipfire.org> (raw)
In-Reply-To: <20211018101022.15448-1-michael.tremer@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1156 bytes --]
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
---
src/initscripts/system/suricata | 12 ++++++++----
1 file changed, 8 insertions(+), 4 deletions(-)
diff --git a/src/initscripts/system/suricata b/src/initscripts/system/suricata
index 2577621b8..72d01b91d 100644
--- a/src/initscripts/system/suricata
+++ b/src/initscripts/system/suricata
@@ -154,10 +154,14 @@ function generate_fw_rules {
done
done
- # Clear repeat bit, so that it does not confuse IPsec or QoS
- iptables -w -A "${IPS_INPUT_CHAIN}" -j MARK --set-xmark "0x0/${REPEAT_MASK}"
- iptables -w -A "${IPS_FORWARD_CHAIN}" -j MARK --set-xmark "0x0/${REPEAT_MASK}"
- iptables -w -A "${IPS_OUTPUT_CHAIN}" -j MARK --set-xmark "0x0/${REPEAT_MASK}"
+ # Add common rules at the end of the chain
+ for chain in "${IPS_INPUT_CHAIN}" "${IPS_FORWARD_CHAIN}" "${IPS_OUTPUT_CHAIN}"; do
+ # Clear repeat bit
+ iptables -w -A "${chain}" -j MARK --set-xmark "0x0/${REPEAT_MASK}"
+
+ # Store bypass bit in CONNMARK
+ iptables -w -A "${chain}" -m mark --mark "${BYPASS_MARK}/${BYPASS_MASK}" -j CONNMARK --save-mark
+ done
fi
}
--
2.20.1
next prev parent reply other threads:[~2021-10-18 10:10 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
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 ` Michael Tremer [this message]
2021-10-19 4:04 ` [PATCH 7/9] suricata: Store bypass flag in connmark and restore 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=20211018101022.15448-7-michael.tremer@ipfire.org \
--to=michael.tremer@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