From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] CU184-update.sh: Add drop hostile in & out logging entries
Date: Mon, 18 Mar 2024 10:15:33 +0000 [thread overview]
Message-ID: <BA3D074F-F990-4BFE-A8C7-C1878BAF66A0@ipfire.org> (raw)
In-Reply-To: <20240316093254.8643-1-adolf.belka@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 2035 bytes --]
Hallo Adolf,
Okay. I have merged this and as soon as the build is done I will push the new update out.
What are we doing with the people who have already installed the update?
-Michael
> On 16 Mar 2024, at 09:32, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
>
> - My drop hostile patch set updated the WUI entries to include in and out logging options
> but the values need to be added to the optionsfw entries for existing systems being
> upgraded.
> - After the existing CU184 update the LOGDROPHOSTILEIN and LOGDROPHO)STILEOUT entries
> are not in the settings file which trewats them as being set to off, even though they
> are enabled in the WUI update.
> - This patch adds the LOGDROPHOSTILEIN and LOGDROPHOSTILEOUT entries into the settings
> file and then runs the firewallctrl command to apply to the firewall.
> - Ran a CU184 update on a CU183 vm system and then ran the comands added into the update.sh
> script and then did a reboot. Entries include and DROP_HOSTILE entries start to be
> logged again.
>
> Tested-by: Adolf Belka <adolf.belka(a)ipfire.org>
> Signed-off-by: Adolf Belka <adolf.belka(a)ipfire.org>
> ---
> config/rootfiles/core/184/update.sh | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/config/rootfiles/core/184/update.sh b/config/rootfiles/core/184/update.sh
> index aa593047d..1a0e67c66 100644
> --- a/config/rootfiles/core/184/update.sh
> +++ b/config/rootfiles/core/184/update.sh
> @@ -80,6 +80,12 @@ xz --check=crc32 --lzma2=dict=512KiB /lib/modules/6.6.15-ipfire/extra/wlan/8812a
> # Apply local configuration to sshd_config
> /usr/local/bin/sshctrl
>
> +# Add the drop hostile in and out logging options
> +# into the optionsfw settings file and apply to firewall
> +sed -i '$ a\LOGDROPHOSTILEIN=on' /var/ipfire/optionsfw/settings
> +sed -i '$ a\LOGDROPHOSTILEOUT=on' /var/ipfire/optionsfw/settings
> +/usr/local/bin/firewallctrl
> +
> # Start services
> telinit u
> /etc/init.d/vnstat start
> --
> 2.44.0
>
next prev parent reply other threads:[~2024-03-18 10:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-16 9:32 Adolf Belka
2024-03-18 10:15 ` Michael Tremer [this message]
2024-03-18 11:10 ` Adolf Belka
2024-03-18 16:15 ` Michael Tremer
2024-03-18 17:19 ` Adolf Belka
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=BA3D074F-F990-4BFE-A8C7-C1878BAF66A0@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