pfSense OpenVPN Server Question

---

Hello all!
I created a OpenVPN server over pfSense and I'm making a large test before going into production.

Now I have some strange disconnects time to time, with an unknown error 10060. I'm on Windows 10 and latest updates (1809) and also the latest version of OpenVPN for Windows.

I added keepalive to push client configuration and made some changes to server config. But after looking in the server logs I have something like:

PUSH_REPLY,dhcp-option DOMAIN redecorp.local,dhcp-option DNS 10.x.x.x,dhcp-option DNS 10.x.x.x,dhcp-option DNS 10.x.x.x,block-outside-dns,dhcp-option NTP 10.x.x.x,dhcp-option NTP 10.x.x.x,redirect-gateway def1,redirect-gateway autolocal,route-gateway 172.26.254.1,topology subnet,ping 10,ping-restart 60,route 172.20.3.0 255.255.255.240,ifconfig 172.26.254.220 255.255.255.0,peer-id 0' (status=1)

My question is regarding ping 10,ping-restart 60,route 172.20.3.0 255.255.255.240. I don't have these options on the server config part (over the gui or the server.conf) and I don't understand why is adding ping 10 and ping-restart 60, that I don't want to avoid the disconnects. Also this route add is also automatic and not configured by me.

Might the problem be related to these configurations?
Thank you in advance!

@fabio-teles,

This is a Windows socket error 10060...
this is normally because the connection timed out when the remote server didn't respond to the connection request.

So the question is did you use the openvpn-client-export package from pfSense to create your Windows client? or did you just download your client from OpenVPN?

• If you used the package, you should have been able to generate an export per user account through the openvpn server on pfSense. This would configure the proper IP settings for the client.

• If you didn't and downloaded the latest client, then you might have to fix your client configuration destination and ip address assignments by using the config file with the OpenVPN client.

Let me know...maybe I can help more.

Hello Ronnie!
In this case I didn't export because we have a very customized installation with RADIUS, etc. So after many, many issues I found out that because we are using TCP 443 Windows was throwing TCP error 10060 because it had a greatter latency than UDP.
So I looked for Windows error 10060 and I found out a MS FIX with a registry setting that mittigated this.
Very strange...I think the latest Windows updated caused this to occur always, but managed to find out. Thank you for the help!

@fabio-teles, Way to work the problem!