OpenVPN up but unable to contact daemon
-
Is this client using a hostname to find the server, by chance?
-
DNS name.
-
I don't see it right now but I think there is an open redmine ticket for that. Something happens to OpenVPN when it stops and restarts when using a hostname and infinite resolve. Somehow it ends up with a different process ID disconnected from the management port.
-
Yes - I get that on some installs but not others.
Seems it never really stops anything from working for me. -
My clients all use a public DynDNS name that is kept up-to-date by the server-end pfSense (that has multi-WAN and offers the server end on the highest tier WAN of a gateway group…).
I haven't tried hard to find a reproducible test case, it just happens from time to time. When I am at home I will try some combinations of failing the client-end link, switching the server end link and name... to see if I can induce it.
From an end-user perspective it is not a show-stopper - user traffic is still passing through the tunnel. -
That's probably this.
https://redmine.pfsense.org/issues/3894I haven't had time to dig far enough to find out where and why it's getting started multiple times in that circumstance.
-
Do you believe that running a pfsense instance in esxi might make this condition more likely to occur?
Its the only time I ever see it myself and the setting on physical machines are not really any different. -
If there's something about your ESX environment or setup in general that makes those VMs network connectivity take longer to come online, possibly. Generally speaking that wouldn't be the case though. I was testing and replicating it on a VK-T40E4 appliance where I blocked or degraded its network access upstream on its WAN network. Same end result with a VM.
-
Possibly. Slower HDD access?
I think the one in question is spread pretty thin. The drive is running on a NAS connected with a gigabit switch and maybe 10 VMs sharing access to the NAS on that one switch.
I could see it running abit slow at times. That is the one that is consistently having this issue no matter if it is wiped and completely reinstalled. -
I just saw this today, first time I updated snapshots after installing OpenVPN. Bare hardware, not stretched at all (Atom D2550). Client connection to Private Internet Access was shown as down, yet it was up & running. Kill by hand, restart by GUI, and things are fine.