From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail02.haj.ipfire.org (localhost [IPv6:::1]) by mail02.haj.ipfire.org (Postfix) with ESMTP id 4c5tMX2lmGz2y17 for ; Tue, 19 Aug 2025 15:11:20 +0000 (UTC) Received: from mail01.ipfire.org (mail01.haj.ipfire.org [IPv6:2001:678:b28::25]) (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 4c5tMS5RVYz2xMF for ; Tue, 19 Aug 2025 15:11:16 +0000 (UTC) Received: from [127.0.0.1] (localhost [127.0.0.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail01.ipfire.org (Postfix) with ESMTPSA id 4c5tMR1tfDzJr; Tue, 19 Aug 2025 15:11:15 +0000 (UTC) DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003ed25519; t=1755616275; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=lEFjLwN08zlsQt51vTJwt3DCiB7nFTxs8NypMEj4bWs=; b=QnZQ86ZNcFgyvCcANfnV3dDtQ8lXZry4+2kuxsOHXrfoTdjl1bBdls2bCj/nKmzqW9HpPr 4E36d5KIo/nTrMAQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003rsa; t=1755616275; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=lEFjLwN08zlsQt51vTJwt3DCiB7nFTxs8NypMEj4bWs=; b=fS6TyqttUUHUygvlAkwUwnMmEvbi9F6EPaXb7/aINc6ZEco7m7/6bYIrKt4GJ9ZYxpp5ui QNDnk5XAkt4DPfKcZCm7lOLpP2zQlyDnZXXZG01KrupiSJ7fkEKMB27VWSxllARCp8aHsM Ns3uMOZ2SYQWCOHKSQdbGQuqGWSbMwcXseZI0rC2fq/3Qg63GR5/9mk0J87241AAjK7C6s 5kJeiUqx/7zZzTME6u6w25ZF4WTqvM08HTnK2UYh+yBlS887oEZ0VBqbLnHZ79DPD6Qau5 y66B7ScNJBMoQpuMvSGm/ImTrE37fwYFPBkEF7izXvNdJsld3DIa1di27tJeAQ== Content-Type: text/plain; charset=utf-8 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 197 is available for testing From: Michael Tremer In-Reply-To: <2dab97ce-9ac8-4661-bed6-db20bd4dc42f@ipfire.org> Date: Tue, 19 Aug 2025 16:11:14 +0100 Cc: "IPFire: Development-List" Content-Transfer-Encoding: quoted-printable Message-Id: <16AE21F7-0184-4E62-B9E1-C89FE9B5B674@ipfire.org> References: <175490371612.107547.14288613781884197415.ipfire@ipfire.org> <8c5b754f-002b-4a80-b757-9a74aeb57f7e@ipfire.org> <29a112a2-0ada-43a1-b0c6-43f336745d43@ipfire.org> <2dab97ce-9ac8-4661-bed6-db20bd4dc42f@ipfire.org> To: Adolf Belka 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 wrote: >=20 > Hi All, >=20 > 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, >>>=20 >>> Have found a little issue. Not sure if it is critical or not. >>>=20 >>> My existing connections on OpenVPN are working fine and the network = topology has been changed in most places but not in the ccd files. >>>=20 >>> I have a connection called ipfiretesting which before the upgrade = had 10.110.30.5 and 10.110.30.6. >>>=20 >>> After the upgrade to 197 if I edit the entry it shows that it is = using 10.110.30.6 >>>=20 >>> However if I look in /var/ipfire/ovpn/ccd/ipfiretesting it still has = the line >>>=20 >>> ifconfig-push 10.110.26.6 10.110.26.5 >>>=20 >>> If I then create a new client connection then all the ccd files get = updated and ipfiretesting now contains >>>=20 >>> ifconfig-push 10.110.30.6 255.255.255.0 >>>=20 >>> 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. >=20 > I can confirm that the recent commits on ovpnmain.cgi have resolved = the issue of the ccd files not being updated during the update. >=20 > 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. >=20 > 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. >=20 > I can also confirm that my CU196 client connection that was restored = and updated to the CU197 openvpn-2.6 settings connected successfully. >=20 > So this issue that I reported can be considered fixed. >=20 > Regards, >=20 > Adolf. >=20 >=20 >>>=20 >>> Regards, >>>=20 >>> Adolf. >>>=20 >>> On 11/08/2025 11:28, IPFire Project wrote: >>>> **IPFire 2.29 =E2=80=93 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 =E2=80=94 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. >>>> =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 >>>>=20 >>>>=20 >>>> IPFire_ >>>>=20 >>>>=20 >>>> IPFire 2.29 - Core Update 197 is available for testing >>>>=20 >>>> **IPFire 2.29 =E2=80=93 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 =E2=80=94 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. >>>>=20 >>>> Read The Full Post On Our Blog = >>>>=20 >>>> The IPFire Project, c/o Lightning Wire Labs GmbH, Gerhardstra=C3=9Fe = 8, 45711 Datteln, Germany >>>>=20 >>>> Unsubscribe