OpenVPN Connect 3.8.0(4528) on Windows11 + IPFire CU202 Development Build

[tphz (iptom)]

Today I tested the OpenVPN Connect client setup on Windows 11

I based my next steps on the following posts/threads

Core 197: OpenVPN and firewall

Have you tried testing connections using the OpenVPN GUI community client? edit What do OpenVPN logs show? WUI–>Logs–>System Logs –> Select Section: OpenVPN then Update edit2 You may need to download the PKCS12 file. [obraz] then import certificate [obraz] [obraz] then select the certificate for the connection [obraz] [obraz] [obraz]

OPENVPN RoadWarrior please help

I am still in the learning phase and currently conducting research. My objective is to access the network behind IPFire. I am following the provided instructions, but when attempting to connect using the OpenVPN client, I receive a “CA not defined” error. I am using IPFire version 2.29 - Core Update 200 and OpenVPN Connect version 3.8. I have already generated the necessary certificates. [image]

---

The following steps resolved the issues with the “Username” and “Password” prompts

and the “CA not defined” error message

---

---

I downloaded the Client Configuration

Next, I downloaded the PKCS12 file

Next, I downloaded the Root Certificate (cacert.pem file)

Next, in the .ovpn configuration file, I deleted the lines containing the

auth-user-pass
auth-token-user USER

Next, I added the contents of the cacert.pem file to the client’s .ovpn configuration file

<ca>
-----BEGIN CERTIFICATE-----
...
-----END CERTIFICATE-----
</ca>

Next, I imported the .p12 file

Next, I imported .ovpn config file

After clicking “Connect,” I selected the certificate I had imported earlier.

After selecting the certificate and clicking Connect again, the client connected to IPFire.

Once connected, I had access to resources on the GREEN remote network.

Best Regards

[herman42 (herman junior)]

Nice write-up. The “CA not defined” issue seems to hit quite a few people with newer OpenVPN Connect versions on Windows 11, especially when the exported config from IPFire does not include the CA block directly inside the .ovpn file. Embedding the cacert.pem contents into the config and importing the .p12 separately was probably the key step here. Removing the extra auth lines also makes sense since certificate auth and username/password prompts can sometimes conflict depending on the client setup. Good to know the GREEN network access worked afterward too. That at least confirms routing/firewall rules on the IPFire side were already correct and the issue was mainly client-side certificate handling.