OpenVPN client service on pfSense terminates when OpenVPN remote server is rebooted/restarted
I have an OpenVPN (UDP) server running on a remote router. The remote OpenVPN server router is not a pfSense, it's Mikrotik RouterOS.
pfSense is configured as OpenVPN client, and connects without problems to the Mikrotik OpenVPN server for a LAN to LAN routing.
When the OpenVPN server is rebooted, the local pfSense openVPN client service is terminated, and never restarted. So I have to manually restart the OpenVPN client service or reboot the pfSense.
And the OpenVPN logs:
Mar 18 15:05:31 openvpn 99632 /usr/local/sbin/ovpn-linkdown ovpnc1 1500 1621 10.67.42.249 255.255.255.0 init
Mar 18 15:05:31 openvpn 99632 SIGTERM[soft,remote-exit] received, process exiting
There are dozen of posts about OpenVPN server terminating on "exit-notify", but in my case the OpenVPN client is stopping, not the server.
How can I have OpenVPN client service restarted automatically, or never killed, after a remote OpenVPN server reboot?
viragomann last edited by
Did you enable the inactivity check in "Ping settings" area?A failing in this would cause the client service to terminate.
Not enabled ;(