From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: IPFire 2.29 - Core Update 184 is available for testing
Date: Wed, 14 Feb 2024 12:51:01 +0100 [thread overview]
Message-ID: <f8b5ad8c-ff26-43f6-bad2-480249efe9bc@ipfire.org> (raw)
In-Reply-To: <170790931523.1343897.16223721846821826212.ipfire@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 2136 bytes --]
Hi All,
The fix for bug#12981 of choosing to log or not log the Hostile traffic coming in and out separately has one bug if you are doing a core update and another if you do a fresh install.
For the Core Update the collectd.conf file changes were not shipped so the DROP_HOSTILE_IN & DROP_HOSTILE_OUT directories are not created and the graphs have an error then as they look for those directories.
I submitted a patch for that issue three days ago.
If you do a fresh install the DROP_HOSTILE_IN & DROP_HOSTILE_OUT directories are created but the code errors as it tries to open the DROP_HOSTILE directory that is not present.
I submitted a patch for that issue this morning.
Regards,
Adolf.
On 14/02/2024 12:15, IPFire Project wrote:
> Today we are releasing the next version of IPFire for testing: IPFire 2.29 - Core Update 184. It comes with a number of improvements all around the system and a lot of package updates. This change log reads a lot more compact than our usual release, but nevertheless give this update a good test and report any found issues back to the development team. If you would like to support us financially, please help us with a donation.
>
>
>
> IPFire_
>
>
> IPFire 2.29 - Core Update 184 is available for testing
>
> Today we are releasing the next version of IPFire for testing: IPFire 2.29 - Core Update 184. It comes with a number of improvements all around the system and a lot of package updates. This change log reads a lot more compact than our usual release, but nevertheless give this update a good test and report any found issues back to the development team. If you would like to support us financially, please help us with a donation.
>
> Read The Full Post On Our Blog <https://www.ipfire.org/blog/ipfire-2-29-core-update-184-is-available-for-testing?utm_medium=email&utm_source=blog-announcement>
>
> The IPFire Project, c/o Lightning Wire Labs GmbH, Gerhardstraße 8, 45711 Datteln, Germany
>
> Unsubscribe <https://www.ipfire.org/unsubscribe>
>
next parent reply other threads:[~2024-02-14 11:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <170790931523.1343897.16223721846821826212.ipfire@ipfire.org>
2024-02-14 11:51 ` Adolf Belka [this message]
2024-02-28 21:08 ` 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=f8b5ad8c-ff26-43f6-bad2-480249efe9bc@ipfire.org \
--to=adolf.belka@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