From: Adolf Belka <adolf.belka@ipfire.org>
To: "IPFire: Development-List" <development@lists.ipfire.org>
Subject: Re: IPFire 2.29 - Core Update 196 is available for testing
Date: Tue, 8 Jul 2025 15:59:58 +0200 [thread overview]
Message-ID: <c185e10a-cb60-4087-9d1c-7c9d383aa4ab@ipfire.org> (raw)
In-Reply-To: <175135621663.3203771.11080679674251259064.ipfire@ipfire.org>
Hi All,
Here my feedback on testing of CU196.
The fixes for the following bugs have all been verified with CU196 Testing.
10245
12060
13804
13834
13836
13857
13858
13860
13861
Working DRM has been confirmed with a fresh install of CU196 Testing.
DRM has been confirmed to work on existing updated systems by removing the /etc/modprobe/framebuffer.conf file.
Existing n2n connections for IPSec, OpenVPN & WireGuard have all been confirmed to work.
Existing rw connections for IPSec (PSK and certificate), OpenVPN & WireGuard have all been confirmed to work.
ExtraHD works fine with mounting and unmounting of HDD's
All graphs are being updated as expected.
Suricata confirmed to be logging issues by sending a test signal to trigger an alert.
The dma email system is confirmed working.
dhcp process, both with fixed leases and dynamic leases confirmed operational.
DDNS is being updated and DNS is functional. All accesses via FQDN have been successfully resolved.
Web proxy via wpad is working correctly and so is the Local Authentication.
Backup and Restore are both working correctly.
Regards,
Adolf.
On 01/07/2025 10:02, IPFire Project wrote:
> Hot on the heels of our recent WireGuard release, the next IPFire update is ready for testing! It comes packed with further WireGuard enhancements, high- resolution consoles, many package updates, and important bug and security fixes.
>
>
>
> IPFire_
>
>
> IPFire 2.29 - Core Update 196 is available for testing
>
> Hot on the heels of our recent WireGuard release, the next IPFire update is ready for testing! It comes packed with further WireGuard enhancements, high- resolution consoles, many package updates, and important bug and security fixes.
>
> Read The Full Post On Our Blog <https://www.ipfire.org/blog/ipfire-2-29-core-update-196-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>
>
parent reply other threads:[~2025-07-08 14:00 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <175135621663.3203771.11080679674251259064.ipfire@ipfire.org>]
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=c185e10a-cb60-4087-9d1c-7c9d383aa4ab@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