From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail02.haj.ipfire.org (localhost [127.0.0.1]) by mail02.haj.ipfire.org (Postfix) with ESMTP id 4bc2mj6cDlz32f2 for ; Tue, 8 Jul 2025 14:00:05 +0000 (UTC) Received: from mail01.ipfire.org (mail01.haj.ipfire.org [172.28.1.202]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (secp384r1) server-digest SHA384 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mail01.haj.ipfire.org", Issuer "R11" (verified OK)) by mail02.haj.ipfire.org (Postfix) with ESMTPS id 4bc2mf2lfZz2y3W for ; Tue, 8 Jul 2025 14:00:02 +0000 (UTC) Received: from [127.0.0.1] (localhost [127.0.0.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mail01.ipfire.org (Postfix) with ESMTPSA id 4bc2md1m3zzVR for ; Tue, 8 Jul 2025 14:00:01 +0000 (UTC) DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003ed25519; t=1751983201; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=QY0Ywr6Jdyqu5jhCb9iuhVZznkNJg/2e2qWAFNgRmtk=; b=vLZv7e9JVPHzeryPm4EGXFRAronsH0kUKeq5RQM0N7WESW1Dw1FHL4awMZ4Xbgz0oVud88 dSWi8t/h4E01RgAw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003rsa; t=1751983201; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=QY0Ywr6Jdyqu5jhCb9iuhVZznkNJg/2e2qWAFNgRmtk=; b=UgHZOUsuEDBqf5BudW0JzetuBheHw9mHq3gwmZJ0JoL8/wE2yQLG2/Ou2nHP/HQSkFahXS tqFH0Ppg68dA4hF94nCw3IRMR92Ub8bSVO7RvKyI3N+oeL3cEWmzVbtYOafeh8hqVmIt+H mY5CBjDqxZkLq/mlJ8OokZHGz4F3+OSJzbS2xUOFbtwucIGWCExDRRpYIHvVGsEQ5PugdA +nuIZLLynab+6RBeZdsEGCFl2IzEoE427SK10+aa1n2F60ADSkXdeiUa75FiMbSgIRSyOU tSw4kEUM9BLcs+/35MXzzgi41ZFzeVa28lcXo+nrRjIqsmLrOd4TQqv5cO217g== Message-ID: Date: Tue, 8 Jul 2025 15:59:58 +0200 Precedence: list List-Id: List-Subscribe: , List-Unsubscribe: , List-Post: List-Help: Sender: Mail-Followup-To: MIME-Version: 1.0 Subject: Re: IPFire 2.29 - Core Update 196 is available for testing To: "IPFire: Development-List" References: <175135621663.3203771.11080679674251259064.ipfire@ipfire.org> Content-Language: en-GB From: Adolf Belka In-Reply-To: <175135621663.3203771.11080679674251259064.ipfire@ipfire.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit 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 > > The IPFire Project, c/o Lightning Wire Labs GmbH, Gerhardstraße 8, 45711 Datteln, Germany > > Unsubscribe >