Very good! Is it correct to assume that we have no more outstanding issues regarding the OpenVPN changes in this update, or did I overlook anything?
Best, -Michael > On 14 Aug 2025, at 20:00, Adolf Belka <adolf.be...@ipfire.org> wrote: > > Hi All, > > On 11/08/2025 16:51, Adolf Belka wrote: >> Hi All, >> Further testing feedback of OpenVPN-2.6 >> I tested out the existing client connections to my android phone and my >> linux laptop. >> Both connections connected. Ping worked on the laptop but not on the >> android. Accessing the IPFire WUI via the openvpn rw tunnel worked for both >> android and laptop. >> I then created new client connections. >> The linux laptop connection worked without any issues. >> The android client did not want to work with the .ovpn file with the >> certificates built in. It said that it had obtained the required info from >> inline but the connection failed within a couple of lines in the log, so >> some problem. >> I then removed the inline certificate lines from the .ovpn file and used the >> .p12 and ta.key files, adding the appropriate lines into the .ovpn file to >> reference them. >> The connection worked without any problem. In addition the ping now worked >> with this android connection. >> Regards, >> Adolf. >> On 11/08/2025 16:01, Adolf Belka wrote: >>> Hi All, >>> >>> Have found a little issue. Not sure if it is critical or not. >>> >>> My existing connections on OpenVPN are working fine and the network >>> topology has been changed in most places but not in the ccd files. >>> >>> I have a connection called ipfiretesting which before the upgrade had >>> 10.110.30.5 and 10.110.30.6. >>> >>> After the upgrade to 197 if I edit the entry it shows that it is using >>> 10.110.30.6 >>> >>> However if I look in /var/ipfire/ovpn/ccd/ipfiretesting it still has the >>> line >>> >>> ifconfig-push 10.110.26.6 10.110.26.5 >>> >>> If I then create a new client connection then all the ccd files get updated >>> and ipfiretesting now contains >>> >>> ifconfig-push 10.110.30.6 255.255.255.0 >>> >>> So if a user upgrades but doesn't create a new client connection all the >>> ccd files will stay with the old format. Not sure what this would or >>> wouldn't do for the connection but I think after the upgrade it would be >>> good to update all the ccd files but not sure how to make that happen. > > I can confirm that the recent commits on ovpnmain.cgi have resolved the issue > of the ccd files not being updated during the update. > > I also noted that backup.pl was modified to do the same thing. I had not > thought about testing an old backup yet. It seems obvious but it just hadn't > come to my mind. > > However with this backup.pl commit it triggered me to test out doing a > restore from CU106 into CU197 and I can confirm that the ccd settings are > updated as are the client connection .ovpn contents. > > I can also confirm that my CU196 client connection that was restored and > updated to the CU197 openvpn-2.6 settings connected successfully. > > So this issue that I reported can be considered fixed. > > Regards, > > Adolf. > > >>> >>> Regards, >>> >>> Adolf. >>> >>> On 11/08/2025 11:28, IPFire Project wrote: >>>> **IPFire 2.29 – Core Update 197** is now available for testing. This >>>> release introduces a significant overhaul of OpenVPN, upgrading to version >>>> 2.6 with improved security, broader client compatibility, and a modernised >>>> codebase — all without requiring changes to existing configurations. >>>> System performance has also been optimised to allow the CPU to remain in >>>> power-saving states more often, reducing energy consumption. As with every >>>> release, this update includes a large number of package updates to ensure >>>> your system remains secure and reliable. >>>> >>>> >>>> >>>> IPFire_ >>>> >>>> >>>> IPFire 2.29 - Core Update 197 is available for testing >>>> >>>> **IPFire 2.29 – Core Update 197** is now available for testing. This >>>> release introduces a significant overhaul of OpenVPN, upgrading to version >>>> 2.6 with improved security, broader client compatibility, and a modernised >>>> codebase — all without requiring changes to existing configurations. >>>> System performance has also been optimised to allow the CPU to remain in >>>> power-saving states more often, reducing energy consumption. As with every >>>> release, this update includes a large number of package updates to ensure >>>> your system remains secure and reliable. >>>> >>>> Read The Full Post On Our Blog >>>> <https://www.ipfire.org/blog/ipfire-2-29-core-update-197-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>
