From mboxrd@z Thu Jan 1 00:00:00 1970 From: Adolf Belka To: development@lists.ipfire.org Subject: Re: IPFire 2.29 - Core Update 184 is available for testing Date: Wed, 28 Feb 2024 22:08:24 +0100 Message-ID: <0061d634-1ca8-4388-b207-58f139711e4c@ipfire.org> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============8073911173494747030==" List-Id: --===============8073911173494747030== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi All, The additional patches mentioned in the mail below for the DROP_HOSTILE=20 fix have been merged into CU184 and everything is now working. Looks good. With CU184 I have also tested the borgbackup changes, OpenVPN RW and N2N=20 connections, both existing ones and creating new ones. Everything worked=20 fine for the connections. When creating a new N2N connection and uploading it to the "client" end=20 there is a bug in the status not being shown properly but nothing=20 related to CU184. This is bug#13548 and a patch fix has been submitted.=20 This can wait for CU185 as there is a simple workaround. There was a bug introduced in CU183 with the latest OpenSSL which was=20 missed in the testing. An OpenSSL bugfix introduced a bug for IPFire=20 when creating a new root/host certificates set.=C2=A0In future I intend to=20 also test out creating new root/host certificates in the Testing phase.=20 This problem is bug#13595 and a bug fix patch has been submitted. This=20 might be good to get into CU184 if at all possible but if not then there=20 is a workaround process involving removing two lines from the ovpn.conf=20 file. Apart from the above, which weren't caused by the CU184 update but were=20 just noticed at the same time, all other functions I have tested out=20 have worked without problems. Regards, Adolf. On 14/02/2024 12:51, Adolf Belka wrote: > Hi All, > > The fix for bug#12981 of choosing to log or not log the Hostile=20 > traffic coming in and out separately has one bug if you are doing a=20 > core update and another if you do a fresh install. > > For the Core Update the collectd.conf file changes were not shipped so=20 > the DROP_HOSTILE_IN & DROP_HOSTILE_OUT directories are not created and=20 > 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=20 > directories are created but the code errors as it tries to open the=20 > 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=20 >> 2.29 - Core Update 184. It comes with a number of improvements all=20 >> around the system and a lot of package updates. This change log reads=20 >> a lot more compact than our usual release, but nevertheless give this=20 >> update a good test and report any found issues back to the=20 >> development team. If you would like to support us financially, please=20 >> help us with a donation. >> =E2=80=8C=C2=A0=E2=80=8C=C2=A0=E2=80=8C=C2=A0=E2=80=8C=C2=A0=E2=80=8C=C2= =A0=E2=80=8C=C2=A0=E2=80=8C=C2=A0=E2=80=8C=C2=A0=E2=80=8C=C2=A0=E2=80=8C=C2= =A0=E2=80=8C=C2=A0=E2=80=8C=C2=A0=E2=80=8C=C2=A0=E2=80=8C=C2=A0=E2=80=8C=C2= =A0=E2=80=8C=C2=A0=E2=80=8C=C2=A0=E2=80=8C >> >> >> =C2=A0 IPFire_ >> >> >> =C2=A0 IPFire 2.29 - Core Update 184 is available for testing >> >> Today we are releasing the next version of IPFire for testing: IPFire=20 >> 2.29 - Core Update 184. It comes with a number of improvements all=20 >> around the system and a lot of package updates. This change log reads=20 >> a lot more compact than our usual release, but nevertheless give this=20 >> update a good test and report any found issues back to the=20 >> development team. If you would like to support us financially, please=20 >> help us with a donation. >> >> Read The Full Post On Our Blog=20 >> >> >> The IPFire Project, c/o Lightning Wire Labs GmbH, Gerhardstra=C3=9Fe 8,=20 >> 45711 Datteln, Germany >> >> Unsubscribe >> --=20 Sent from my laptop --===============8073911173494747030==--