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 185 released Date: Mon, 22 Apr 2024 12:25:37 +0200 Message-ID: <21973f0e-5a87-425a-a384-975add88ec14@ipfire.org> In-Reply-To: <53E01B9A-76F2-4CEE-9F42-3DB20B3B3EDC@ipfire.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0218058527885604830==" List-Id: --===============0218058527885604830== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi Michael, On 18/04/2024 23:40, Michael Tremer wrote: > Hello Adolf, >=20 >> On 18 Apr 2024, at 09:37, Adolf Belka wrote: >> >> Hi Michael, >> >> I am sorry but the ovpn.cnf file was not updated with CU185 full release. >=20 > Meh. >=20 >> I don't understand this as I tested it with CU185 Testing and cleared the = OpenVPN x509 certificate set and recreated it successfully. However now with = CU185 full release it is not working because the ovpn.cnf was not changed. >> >> I checked the exclude file in the config/rootfile/core/185 directory and i= t has the line >> >> /var/ipfire/ovpn >> >> Does this mean that everything under ovpn is excluded from being updated? = If yes then that would explain why it is not working now with the full releas= e but would not explain why it worked for me with CU185 Testing. >=20 > It should not be excluded. However, since /var/ipfire is so complicated wit= h what we control and what the user controls I think it is best to move the c= onfiguration out of that directory. >=20 > I would propose this: >=20 > https://patchwork.ipfire.org/project/ipfire/list/?series=3D4261 >=20 > I haven=E2=80=99t *fully* tested this because I did not want to destroy my = production system and it is late that I do not want to set up a test box. So,= if someone has a change, please let me know if this is breaking anything :) Sorry for the late reply, IO have been busy completing my Netherlands Tax Ret= urn. I will have a go at testing your changes out and let you know what I find. Regards, Adolf. >=20 >> How do we deal with this now. >> >> Sorry, >=20 > No need to be sorry :) This happens and we should have fixed this when we f= ound that little speck of doubt. >=20 > -Michael >=20 >> >> Adolf. >> >> On 17/04/2024 18:10, IPFire Project wrote: >>> I am happy to announce that we finally have a new release of IPFire: IPFi= re 2.29 - Core Update 185. It comes with a brand new IPFire IPS based on Suri= cata 7, a number of bug fixes across the distribution and a good amount of pa= ckage updates. >>> =E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2= =80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C = =E2=80=8C =E2=80=8C =E2=80=8C >>> IPFire_ >>> IPFire 2.29 - Core Update 185 released >>> I am happy to announce that we finally have a new release of IPFire: IPFi= re 2.29 - Core Update 185. It comes with a brand new IPFire IPS based on Suri= cata 7, a number of bug fixes across the distribution and a good amount of pa= ckage updates. >>> Read The Full Post On Our Blog >>> The IPFire Project, c/o Lightning Wire Labs GmbH, Gerhardstra=C3=9Fe 8, 4= 5711 Datteln, Germany >>> Unsubscribe >=20 --===============0218058527885604830==--