From: Stefan Schantl <stefan.schantl@ipfire.org>
To: development@lists.ipfire.org
Subject: [PATCH 4/5] red.up: Generate Suricata DNS servers file on reconnect.
Date: Tue, 05 Nov 2019 10:32:01 +0100 [thread overview]
Message-ID: <20191105093202.4488-4-stefan.schantl@ipfire.org> (raw)
In-Reply-To: <20191105093202.4488-1-stefan.schantl@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 903 bytes --]
Signed-off-by: Stefan Schantl <stefan.schantl(a)ipfire.org>
---
src/initscripts/networking/red.up/23-suricata | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/src/initscripts/networking/red.up/23-suricata b/src/initscripts/networking/red.up/23-suricata
index 1514909ee..c0628e9f9 100644
--- a/src/initscripts/networking/red.up/23-suricata
+++ b/src/initscripts/networking/red.up/23-suricata
@@ -19,8 +19,12 @@ if($ids_settings{'ENABLE_IDS'} eq "on") {
# Regenerate the file with HOME_NET details.
&IDS::generate_home_net_file();
- # Set correct ownership.
+ # Regenerate the file with DNS_SERVERS details.
+ &IDS::generate_dns_servers_file();
+
+ # Set correct ownerships.
&IDS::set_ownership("$IDS::homenet_file");
+ &IDS::set_ownership("$IDS::dns_servers_file");
# Check if suricata is running.
if(&IDS::ids_is_running()) {
--
2.20.1
next prev parent reply other threads:[~2019-11-05 9:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-05 9:31 [PATCH 1/5] ids-functions.pl: Introduce generate_dns_servers_file() Stefan Schantl
2019-11-05 9:31 ` [PATCH 2/5] ids.cgi: Generate and store the DNS server configuration Stefan Schantl
2019-11-05 9:32 ` [PATCH 3/5] convert-snort: Generate DNS servers file Stefan Schantl
2019-11-05 9:32 ` Stefan Schantl [this message]
2019-11-05 9:32 ` [PATCH 5/5] suricata: Use DNS_SERVERS declaration from external file Stefan Schantl
2019-11-05 10:22 ` Michael Tremer
2019-11-05 12:45 ` Stefan Schantl
2019-11-05 15:47 ` Michael Tremer
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=20191105093202.4488-4-stefan.schantl@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