From: Adolf Belka <adolf.belka@ipfire.org>
To: "IPFire: Development-List" <development@lists.ipfire.org>
Subject: Re: IPFire 2.29 - Core Update 197 is available for testing
Date: Mon, 11 Aug 2025 16:01:51 +0200 [thread overview]
Message-ID: <8c5b754f-002b-4a80-b757-9a74aeb57f7e@ipfire.org> (raw)
In-Reply-To: <175490371612.107547.14288613781884197415.ipfire@ipfire.org>
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.
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>
>
next parent reply other threads:[~2025-08-11 14:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <175490371612.107547.14288613781884197415.ipfire@ipfire.org>
2025-08-11 14:01 ` Adolf Belka [this message]
2025-08-11 14:51 ` Adolf Belka
2025-08-11 19:29 ` Peer Dietzmann
2025-08-14 19:00 ` Adolf Belka
2025-08-19 15:11 ` Michael Tremer
2025-08-19 15:56 ` Adolf Belka
2025-08-19 18:39 ` [PATCH] ovpnmain.cgi: Apply default settings when neccessary Stefan Schantl
2025-08-20 16:59 ` IPFire 2.29 - Core Update 197 is available for testing Adolf Belka
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8c5b754f-002b-4a80-b757-9a74aeb57f7e@ipfire.org \
--to=adolf.belka@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox