OpenVPN just stopped working



  • Hello,

    I am running PfSense on VMWare ESX 4.1.  I had this setup and running perfectly, and had users connecting though OpenVPN, and then, it just stopped working.  By "it just stopped working", I mean that there are no routes in the client to route anything to the VPN tunnel, hence, traffic tries to go out the client's WAN and fails.  Nothing was touched or configs changed, just stopped routing out of the blue.

    When this was working (for a few days until today), the client would receive the route 10.1.0.0/16, which routed to the VPN tunnel, and successfully reached its destination.  Now, I do not see the 10.1.0.0/16 network in my ROUTE PRINT on the client.  Clients that were connected before the issue occurred were just fine, until they logged off and back on again.

    I tried restarting the OpenVPN service, rebooting the server, double checked my configs, made sure I was pushing routes either with the IPV4 Local Networks statement or using push "route 10.1.0.0 255.255.0.0";, was able to ping my network resources from the firewall, IPSec is turned off and there are no other VPN services running on the server but OpenVPN.  Nothing in the logs that tell me that there is an issue.

    Currently, the VPN does connect, but no routes are presented to the client, so the only thing that pings on the VPN is the client's IP address assigned to it.

    I am running:
    2.2.1-RELEASE (amd64)
    built on Fri Mar 13 08:16:49 CDT 2015
    FreeBSD 10.1-RELEASE-p6

    Does anyone else have similar issues?  VMWare issue?  Is there more information that I can provide?

    Thanks



  • …And so I fixed the issue, kind of.  Reading through the forum, I realized that I did not "Run as Administrator".  Curious though, why would it work for a while and just stop, unless now, running the program as Administrator, where as before, my users did not have to "Run as Administrator", until today.  Puzzling indeed.


Log in to reply