From mboxrd@z Thu Jan 1 00:00:00 1970 From: Adolf Belka To: development@lists.ipfire.org Subject: Re: IPFire 2.27 - Core Update 164 is available for testing Date: Mon, 21 Feb 2022 16:01:20 +0100 Message-ID: In-Reply-To: <164537850759.17885.12515633604045912133.ipfire@ipfire.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0094202773470155702==" List-Id: --===============0094202773470155702== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi All, Just tested out CU164 on my vm testbed system. The update went without any problems. You see the pakfire log status again on= the wui page during the update. OpenVPN RW setup ran without any issues. Connection successfully made. IPS has the multiple providers option successfully in place. I eventually fou= nd the Force Update of rules button, which was very useful for my vm testbed = as it is not running all the time and so the rules were a bit out of date. As far as I can tell everything is working fine on it. No issues detected. I will let it run over the next few days during the daytime and see how thing= s go. Regards, Adolf. On 20/02/2022 18:35, IPFire Project wrote: > IPFire Logo >=20 > there is a new post from Michael Tremer on the IPFire Blog: >=20 > *IPFire 2.27 - Core Update 164 is available for testing* >=20 > It is time to test another release for IPFire: IPFire 2.27 - Core Updat= e 164. It comes with a vastly improved firewall engine, a new kernel and vari= ous security and bug fixes. Please help us testing this release and if you wo= uld like to support us, please donate. >=20 > Click Here To Read More >=20 > The IPFire Project > Don't like these emails? Unsubscribe . >=20 --===============0094202773470155702==--