Testing out CU198 with OpenVPN-2.7_alpha3

Testing out CU198 with OpenVPN-2.7_alpha3

[Adolf Belka]

Hi All,

I have built and done initial testing of CU198 with OpenVPN-2.7_alpha3. Here is my initial feedback.

My N2N connection connected and I could ping between both ends. The status on the OpenVPN WUI page showed as Connected.

Only item was that when rebooting the following message shows up in the boot log when the N2N connection is started

DEPRECATED: --persist-key option ignored. Keys are now always persisted across restarts.


I the tested out the old existing Android and Linux Laptop client connections.

In both cases at the client ends they said they were connected.

On the Linux Laptop I could ping to a PC on the green network. For both the Linux Laptop and Android phone I could access the WUI page of the IPFire system. The logs showed that the clients were connected.

However in both cases the OpenVPN WUI page stayed showing the RW connections as disconnected. Accessing the OpenVPN Connection Statistics never showed any connection existing.

So the status methodology for the RW's does not seem to be working with OpenVPN-2.7, even though the connections were successfully connected and the standard openvpn logs show the rw clients as connected.

I will have another go with new client connections and see if that shows anything different with regard to the status.

Also need to remember this is the alpha3 release so there might be bugs still and maybe that is what I am experiencing.

So RW connections get made but stay showing as disconnected when they are actually connected.
N2N connections show as connected and are connected.

Regards

Adolf

Re: Testing out CU198 with OpenVPN-2.7_alpha3

[Michael Tremer]

Hello Adolf,

This is really valuable work because we might have to start transitioning OpenVPN changes a lot sooner than the final release is coming out because of all this bad, static configuration stuff on both sides of the connection.

But this actually proves the opposite. The —-persist-key option can be easily dropped then. We use it everywhere and it will then become the default. Very good.

Regarding the status, there have been many changes over the years and it usually should be easy to fix it. Normally more information is being added and we just need to account for it. Hopefully that is a 5 minute job.

So with this information, I am very relaxed and hopeful that the new 2.7 release will be an easy update for us and everyone using OpenVPN.

Best,
-Michael

> On 17 Aug 2025, at 14:43, Adolf Belka <adolf.belka@ipfire.org> wrote:
> 
> Hi All,
> 
> I have built and done initial testing of CU198 with OpenVPN-2.7_alpha3. Here is my initial feedback.
> 
> My N2N connection connected and I could ping between both ends. The status on the OpenVPN WUI page showed as Connected.
> 
> Only item was that when rebooting the following message shows up in the boot log when the N2N connection is started
> 
> DEPRECATED: --persist-key option ignored. Keys are now always persisted across restarts.
> 
> 
> I the tested out the old existing Android and Linux Laptop client connections.
> 
> In both cases at the client ends they said they were connected.
> 
> On the Linux Laptop I could ping to a PC on the green network. For both the Linux Laptop and Android phone I could access the WUI page of the IPFire system. The logs showed that the clients were connected.
> 
> However in both cases the OpenVPN WUI page stayed showing the RW connections as disconnected. Accessing the OpenVPN Connection Statistics never showed any connection existing.
> 
> So the status methodology for the RW's does not seem to be working with OpenVPN-2.7, even though the connections were successfully connected and the standard openvpn logs show the rw clients as connected.
> 
> I will have another go with new client connections and see if that shows anything different with regard to the status.
> 
> Also need to remember this is the alpha3 release so there might be bugs still and maybe that is what I am experiencing.
> 
> So RW connections get made but stay showing as disconnected when they are actually connected.
> N2N connections show as connected and are connected.
> 
> Regards
> 
> Adolf
> 
>