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