@Gertjan

that make sense!

My servers/clients certs are long time ago ecdsa-with-SHA512 but I see this drop down and it look like the default has changed.

ExportVPN 2023-12-01_15-40.png

Maybe some of my VPN exports in 2022 was still in the old legacy version and thats the problem now.

@viragomann thanks for the long reply, I appreciate your help and your patience ;-) (btw. it seems we could "talk" in german as far as I understand ... would have to happen in the "German" section of this Forum, I assume)

No, I don't want to bridge 60 client subnets. I wondered if a bridge would help in the shops where the openvpn client appliances run. Right now in my test shop the specific PCs run behind the SG1100 and are in a separated LAN there.

I should draw a new diagram ...

Right now the customer is testing things and sounds happy so far. I expect him to plug more PCs into that subnet today ... maybe the current setup already is good enough (while not yet perfect maybe).

It's very likely that I mix up concepts. You list NAT and routing as 2 ways of doing that, I maybe still don't fully see the lines between. As far as I understand right now, I currently have NAT and routing in place ...

Let me come up with another diagram, this time maybe more beautiful and with more details. I'd really like to get this as clean as possible before I have to scale it up to N vpn clients.

good morning from my side ...

Even if you get past that encryption error it will reject the certificates since Yealink's firmware only supports SHA1 certificates, and SHA1 certificates are not valid on OpenSSL 3.x

@ndemarco
You have to use different CAs on each server. So only users, who owns a client certificate from a certain server, can connect.

@viragomann Thank you for these explanations, everything is clear now :)

Ok, so I suggest to review the description of the input field from:

The virtual IPv4 network or network type alias with a single entry used for private communications between this client and the server expressed using CIDR (e.g. 10.0.8.5/24). With subnet topology, enter the client IP address and the subnet mask must match the IPv4 Tunnel Network on the server. With net30 topology, the first network address of the /30 is assumed to be the server address and the second network address will be assigned to the client.

to:

The virtual IPv4 network (or, just for net30 topology, a network type alias with a single entry) used for private communications between this client and the server expressed using CIDR (e.g. 10.0.8.5/24). ...

@dimnovotny

thank you for your howto. Did you find a way to detect id-changes and automate the configuration generation für pkcs11-id?

It shouldn't be a problem either way if you use a current version of pfSense with the current version of the export package. It properly sets the encryption on the PKCS#12 archive to be "high" by default which is compatible with OpenSSL 3.x. If you need to export for macOS/iOS (which don't support "high" level encryption on PKCS#12) you can set it to "low" which uses an older algorithm that is supported by both OpenSSL 3.x and macOS/iOS.

@dave-opc I had the workstation as my work computer for a while and it had no updates, it's an old Fujitsu Celsius M740. I will check again, have to switch to the 2nd machine and put back the windows disk.

@viragomann said in Tried to change ovpn p2p from shared key to SSL/TLS... Connection done but no rooting... same settings:

@gsp said in Tried to change ovpn p2p from shared key to SSL/TLS... Connection done but no rooting... same settings:

So in any case CSO is mandatory?

If you want to access a network behind the client, it is, as mentioned.

The CSO sets the iroute inside the OpenVPN server. This is needed to route the traffic to the proper client.
This routes will not shown up in the routing table of pfSense. There you will only see the network, which you stated in the server settings.

Thank you for your help! I have some sites interconnected with shared key option... Should I go to IPSec or ovpn p2p ssl , what do you think better? Because for many sites IPSec is now much easier setup... :)

Any Help ?

@luquinhasdainfra yes you cannot upgrade packages for a later version. See my sig.

@SteveITS Since posting that I tried and got working and came back here and noticed your reply. I didn't forward a port since my pfsense is static but good to know that it can be done.

However it seems to go offline a couple times sometimes and needed "coaxing" to get it back connnected (but in all fairness I was messing around with it lots)... I found changing a setting like tunnel name on UniFi S2S VPN Page would make it work again (reset button in status column didn't do anything when in this state, nor did pausing/unpausing). Using hostname instead of IP does not appear to work even though it is a new feature, and unifi does not show any status that it is connected like OpenVPN, but that is support issues for UniFi, I suppose not here.

@viragomann

No my firewall rule only accept specific vpn network to specific local subnet

The linux behaviour was exacly a test on any/any
Therefor i found this issue where windows obey and linux does not give a shit

:)

@viragomann
Yes, the users are already created on the current server.

@talaverde said in VPN DNS (i.e. PIA or NordVPN) and/or DNS over TLS - Which way to go?:

o DNSSEC/TLS enabled DNS servers. No issues of leakage that I'm aware of. DNS requests are much quicker than using the VPN

This is 4 and half years too late, but can you please share the instructions on how you route your VPN DNS queries through your local DNS

@tbgu87
Hi,
das ist der internationale Bereich. Hier sollten Posts in Englisch verfasst sein. Für Deutsch gibt es einen eigenen Bereich.

Die Endgeräte bekommen die Routen richtig gepuscht.

Hast du dir das in der Routingtabelle am Client angesehen?

Oft wird die Route auf den entfernten Netzen zum Access Server Tunnel Netz vergessen. Also je nachdem, wie du die Site-to-Site Verbindungen eingerichtet hast, ist das Client Tunnel Netzwerk da irgendwo als "Remote network" einzutragen.

@jimp
Hi,

thanks for the answers !

Regarding the fact that the pfsense 2.6.0 CE version is impacted, for my part I was able to confirm that last week that on one of my firewalls in 2.6.0 not up to date I had available the 2.5.4 package of openvpn while today I have version 2.6.4.
What is strange is that as https://cve.mitre.org/ indicates, only versions 2.6.0 to 2.6.6 are impacted...

09adf418-f563-483c-a369-5e4d60d0cff7-image.png

0ee2dbd6-cc83-41b3-9214-51f9a43b7792-image.png

911df671-4911-41c9-8a99-96362055474f-image.png

49e14baa-a9bd-40b3-997f-36603c82f552-image.png

To conclude, you must upgrade to pfsense CE version 2.7.1