SOLVED: the Client certificate was not present, apparently the OpenVPN configuration Wizar only create a "Server Certificate", so the user one have to be created manually.

alt text

@brunoforestier

you changed your tunnel IP ?

and if solved please mark als solved
brNP

@gertjan I took a look at the OpenVPN access server documentation and logs.
The connection issue is due to a TLS error. I have spent some time looking into it and learned more about the access server.
Long story short, I decided to switch from the access server to a pfSense OpenVPN server.
Main reason is that I found the amount of configuration options in the OpenVPN access server quite limited.
I managed to set up get connected to the pfSense OpenVPN server quite easily but I encountered a new problem. I can not connect to certain websites.

I will make a new thread for this 😰

@jknott
I finally solved creating another phase2 in ipsec, now works fine.
As described here:
https://docs.netgate.com/pfsense/en/latest/vpn/ipsec/multiple-subnets.html

Thanks again for help.

bye.

We ran into a similar issue with pfSense 2.5.1 running OpenVPN with RADIUS and 2FA/MFA. For us, the fix adding these options in the OpenVPN Client Export tool under Additional configuration options :

Now, our 2FA/MFA with RADIUS works very well.

@deanfourie It looks like you are trying to import Client/Server certificate on the CA page.

Please read https://docs.netgate.com/pfsense/en/latest/certificates/index.html
and watch https://www.netgate.com/resources/videos-certificate-management-on-pfsense-24

@cerberus2022 said in OpenVPN route to remote network:

I am working on deploying PFSense and i will be using it as a openvpn server for remote workers.

Is this the default gateway in the local network or is there another router?

Do you set up an access server for road warriors or a site2site?
You're talking about "remote workers" but also stated a "remote site".

All of the remote sites are set up on a different firewall that they connect to that sits on LAN at 192.168.45.3 .

What does this mean?

@umm12
I was part of the pfsense team before and I using pfsense for about 100 different projects now. But it is not possible to use two way/side SSL for openvpn in this job. You can use a shared certificate for all your clients that if clients do not have that certificate can not enter your service with a username and password.
thanks

@viragomann Yes, that's true. I will experiment with ssh.

Thank you for your help and time!

Here are both firewall rulesServer.png Client.png

Please be note: the client internet connection is 5G router, no static IP

@kom Ahh good point, hadn't thought of that. Thank you for the response. It's much appreciated!!

I'm guessing that there are limitations or bugs when trying to use a TAP interface in a peer to peer setup. Or maybe you have to add in some custom settings to make it work. Either way, I had to go with layer 3 TUN mode and use a dedicated PC client to relay DHCP and bridge the layer 2 traffic via a 2nd VPN connection using remote access. This method doesn't scale well and is a bit over complicated, but it does what I need for now.

Try using Ivacy's Netherlands VPN. I've never came across any of the problems mentioned. I get fast internet speeds with no throttling, be it for torrenting or streaming or any other purpose.

It had to do with cipher differences between the two versions.

https://community.openvpn.net/openvpn/wiki/CipherNegotiation

Had to edit some settings in both server and client side.

I’m having the same scenario. 2 Torgaurd VPN clients, and they end up with the same virtual IP addresses, and traffic through the VPN stops.

A restart of pfsense would previously resolve the issue by assigning different virtual IP’s, but over the last week or so both connections get the same.

Any ideas on how to stop this from happening.

@topogigio
Yes, with TLS auth, only clients with a certificate signed by the CA which is selected in the server settings are allowed to connect.
You can additionally check „strict user CN matching“ to ensure all clients can connect with their own cert.

Effectively, in It support we always have to use imagination for different solution for the dumbest users! :)

I've didn't implement and test the solution, but I'm sur it will works!!!

Thanks all and have a good day!