@viragomann Here is the OpenVPN tab: [image: 1695075529041-d73061bc-c188-4aca-951e-d2acca9f8847-image.png]

[image: 1695058346462-7a56e8a4-1c89-45ec-9987-edb7bd193813-image.png] another interface WAN, it is working... so, this BUG on OpenVPN?

@petrt3522 Didn't know you were using a OpenVPN client. I used the wrong reply button - should have replied to @pwood999 @pwood999 522 was talking about a OpenVPN server process. /var/etc/openvpn/server1/sock These lines : Jul 18 13:12:55 pfSense-MX80 openvpn[5843]: MANAGEMENT: CMD 'state 1' Jul 18 13:12:55 pfSense-MX80 openvpn[5843]: MANAGEMENT: CMD 'status 2' is the widget questioning for the list with connected users. The 'socket' (file based) is only available locally. I'm not using the pfSense OpenVPN as a client myself, so, in that case, I can't tell, but I presume the widget can also connect to the openvpn client service socket and collect data about the Openvpn link. Again : presuming here. Btw : no intended. @petrt3522 the subject is wrong : Repeating connect & disconnect in logs. These log lines do not show any "OpenVPN" reconnections.

Anyone else struggeling with OTP after 2.7.0 update?

@Stef93 It gets stranger. When I use the client export utility to get the IOS config and then import it into the OpenVPN app on my iPad, it DOES connect, although I still cannot see anything on the permitted subnet. The iPad was just a test, I don't plan on using this via a mobile device.

@Hudson-1 So I expect, that pings to public IPs are working. However, 8.8.8.4 is not a good advice. The server doesn't respond to ping requests obviously. Try 8.8.8.8 instead.

@viragomann After the latest patch Fix OpenVPN selecting wrong interface address when VIPs are present (Redmine #14646) https://redmine.pfsense.org/issues/14646 I could be able to route out my traffic and the OPENVPN client works as it is requested.

@viragomann thank you, I'll check that out

Fixed !! ... I am so used to working on smaller 100% fibre based networks with min 1Gbe connectivity. I forget this is more complex. And takes longer to replicate. When you try and resolve the namespace it comes up with the primary DNS being the one furthest away that did not have a valid replication. Thanks John!

Also, even if your client is up-to-date, if your certs use a weak hash like SHA1, then builds of OpenVPN based on OpenSSL 3 will refuse those certificates as well. Nothing the client or server can do about that, you have to issue new certificates that don't use weak hashes. If it's the encryption on the PKCS#12 bundle that isn't being read by the OS, you can always install the client manually and then export an inline configuration with the certs inside rather than using PKCS#12, or you can export a PKCS#12 bundle separately from the certificate manager using a higher level of encryption. Any version of the export package newer than 1.9 should be capable of exporting a stronger PKCS#12 bundle directly in the export package: https://redmine.pfsense.org/issues/13255

Hi @Stef93 Thanks for the suggestion! However it looks like the client end of the tunnel (10.10.10.2) is NAT'ing the traffic prior to putting it in the tunnel. So by the time it reaches the pfSense OpenVPN NAT Policy it is already NAT'd. I was able to solve the issue by creating a similar NAT Bypass rule using the the GL-iNet NAT interface. And that seems to be working. I appreciate your feedback!

@Stef93 Turned out that I have missed to add a Client Specific Override, but couldn't get it to work anyway. Reading a bit more on Client Specific Override I found out that changing the tunnel network from /24 to /30 didn't need any override and then I got it working. Thanks, you lead me to the solution!

@kohenkatz I've had the same prefix for a few years. It's even survived replacing both the computer I run pfSense on and the cable modem. The IPv4 lease wouldn't survive either. IPv6 uses something called DUID, which is supposed to tell the ISP what your prefix is. I understand some ISPs ignore it. I have no idea what Verizon does. Maybe someone else here knows.

Looking at Logs can see these error too: ovpn.client/WANPFSENSE:26059 PID_ERR replay-window backtrack occurred [1] [SSL-0] [0_9EEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEE] 0:957 0:956 t=1693552393[0] r=[0,64,15,1,1] sl=[3,64,64,528] I've switched the ovpn.server to TCP protocol, now samba access works fine, also the http://SITEA/login can be loaded!

@big_blue [image: 1693540125080-ae3ff397-8c96-487f-91a7-41e3f0e4d517-image.png] [image: 1693540466886-656be457-7cc3-44aa-8035-74c9c894412a-image.png] and rules vlan19 [image: 1693540497808-5d5ee4cb-f017-44cb-8853-360f2360003c-image.png] be sure to put the first in the list of rules in vlan19 [image: 1693540719304-fe53de4a-6bd8-4ff1-bc48-3ae6fd435e30-image.png] [image: 1693540860293-6769f515-7213-4b90-9757-b759ee9a4896-image.png]