@alexparedes Did you also update the client? Which client is it? Also check the server logs for hints on what is failing.

after review, this is coming from older version with the EXIT NOTIFY... how can i fix old upgraded router without having EXIT NOTIFY ? powershell command ? re-make the tunnel ? thanks !

I get even worse results ... Machine A (pfSense 2.6.0): time openvpn --test-crypto --secret /tmp/secret --verb 0 --tun-mtu 20000 --cipher aes-128-gcm 2022-02-26 19:22:27 Cipher negotiation is disabled since neither P2MP client nor server mode is enabled 0.192u 0.000s 0:00.19 100.0% 601+171k 1+0io 0pf+0w Machine B (pfSense 2.6.0): time openvpn --test-crypto --secret /tmp/secret --verb 0 --tun-mtu 20000 --cipher aes-128-gcm 2022-02-26 19:22:35 Cipher negotiation is disabled since neither P2MP client nor server mode is enabled 0.587u 0.023s 0:00.61 98.3% 618+176k 0+0io 0pf+0w I spent most of the day trying to reach reasonable speeds, and this is the result: iperf3 -c 172.16.16.1 -R Connecting to host 172.16.16.1, port 5201 Reverse mode, remote host 172.16.16.1 is sending [ 5] local 172.16.16.2 port 53032 connected to 172.16.16.1 port 5201 [ ID] Interval Transfer Bitrate [ 5] 0.00-1.00 sec 6.10 MBytes 51.2 Mbits/sec [ 5] 1.00-2.00 sec 8.03 MBytes 67.4 Mbits/sec [ 5] 2.00-3.00 sec 7.28 MBytes 61.1 Mbits/sec [ 5] 3.00-4.00 sec 7.60 MBytes 63.8 Mbits/sec [ 5] 4.00-5.00 sec 6.77 MBytes 56.8 Mbits/sec [ 5] 5.00-6.00 sec 7.17 MBytes 60.1 Mbits/sec [ 5] 6.00-7.00 sec 8.87 MBytes 74.4 Mbits/sec [ 5] 7.00-8.00 sec 7.41 MBytes 62.2 Mbits/sec [ 5] 8.00-9.01 sec 7.54 MBytes 62.9 Mbits/sec [ 5] 9.01-10.00 sec 6.44 MBytes 54.3 Mbits/sec - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-10.14 sec 73.4 MBytes 60.7 Mbits/sec 91 sender [ 5] 0.00-10.00 sec 73.2 MBytes 61.4 Mbits/sec receiver

@jknott said in OpenVPN Not working after update: Are there changes in the new version (again) that cause earlier versions to fail? There are always some pesky minor changes, that's why "just updating" pfSense == updating OpenVPN creates "OpenVPN Not working after update". The "OpenVPN server" is just a process that listens on a port, typically UDP/1194. That's just a firewall rule, no nat needed. When the connection doesn't work, that is because the 'client' doesn't understand the 'server', or the other way around.

@gertjan That setting doesn't work for me in the issue I've been having.

I also have encountered this issue. What occurs is that pfSense sometimes gloms the options together when OpenVPN is restarted, causing a syntax error. So pull-filter ignore "ifconfig-ipv6" pull-filter ignore "route-ipv6" becomes pull-filter ignore "ifconfig-ipv6"pull-filter ignore "route-ipv6" You can workaround this problem by adding a comment marker at the end of each affected line, like: pull-filter ignore "ifconfig-ipv6" # pull-filter ignore "route-ipv6" #

@viragomann sorry how do I do that? How do I get to the configuration file? Basically, when doing a whatmyip, I want a WAN address of my VPN endpoint, not my actual IP address at home. Also, I would expect to see the VPN route reflected in a tracert if I'm not mistaken. Thanks

@viragomann Hi All port seems to be closed on pfSense, even they are not. I use and "port checker" (on internet) and it shows that ports are closed but they are not. I already disabled AV and Squid.

After reverting this changes https://redmine.pfsense.org/issues/12232 in file after update, active connections shows again in OpenVPN status.

@johnpoz Thanks

@bob-dig Thank you!

@dlogan No, this cannot be done in OpenVPN. I think, you could achieve this with two failover groups with inverted gateway priorities. But this requires two different OpenVPN servers on the main site.

If you want to fix this regression pls apply this patch 3ade222beb2cae2c0681ed69d4e5a0c82c6303f9