Works like this for me: Single OpenVPN road-warrier server instance bound to Localhost. Port forward on both WAN-1 and WAN-2 to the same OpenVPN localhost instance. Add appropriate FW rules to allow forward VPN traffic Separate DDNS entries for each WAN. Then In the Client config file, simple add two entries for the VPN host connections, i.e. remote wan1.ddns.com 1194 tcp-client remote wan2.ddns.com 1194 tcp-client Note: I used TCP for my OpenVPN, because UDP didn't work well in my scenario, but UDP should also work. This way when your two WAN gateways switch from High to Low tier, the VPN clients should reconnect to the second DDNS.  Only downside is they will remain connected to the Low tier GW when the high tier comes back online, however when they disconnect & reconnect later they will get the high tier as it's the first in the client list.

Fixed my problem by unchecking the block outside dns button in settings on Torguard app, now works as expected.

Tunnel Network is 10.0.8.0/24 Pfsense gateway 192.168.1.1/24 client gets 10.0.0.8.2

My OpenVPN client configuration on a freshly installed FreeBSD 10.3 and openvpn 2.3.14 works fine. It is unfortunate that this does not work on pfSense :(

You need a Phase 2 definition on the IPsec tunnel that covers the OpenVPN subnet going to the remote IPsec network.

It is. I would start by going back to your VPN provider and looking at their tutorials. Most providers these days have them and there's usually a generic openvpn one disguised as other / ddwrt / openwrt etc. Some providers even have a pfsense specific tutorial. I recommend this because they also usually supply the correct parameters specific to them, or even ovpn files you can use as reference in pfsense. There is an additional parameters section in the pfsense openvpn client config which override any of the specific settings entered prior. You will be able to paste most of your ovpn stuff in the additional parameters which will be user and perhaps have to give some fake values in the non advanced section to satisfy the UI validation. This is the one thing I'd like to see in pfsense: the ability to define a client by linking / uploading an ovpn file from the UI. If you know how to use the advanced parameters, you can actually link to one in there assuming you know how to copy it into the install. The one thing I don't recall is if all traffic in the firewall automatically flows through this client because my configuration is to VPN on a per host basis.

Thank you very much for the solution! I made an alias for localdomain so it makes things easier and cleaner in the rules. Thanks again!

Any resolution to this you found?  I may be having a similar issue.

me think… you get the same 192.168.X net at your inlaws as you have at home... " in vpn route all traffic" does not mean you dissapear from local LAN ( you still reach LOCAL LAN so you.. "get stuck in there" with your traffic.. you never Leave their LAN to reach yours... because of  the use of same NET numbers ) my suggestion is that you at YOUR home use a 192.168.X net which is not common as a default net .. common deafult net in home routers: 192.168.0.0/24 192.168.1.0/24 use 192.168.100.0/24 at your home instaed rgrds Johan

all setting was right ,  i havn't mentioned that one of the pfsense version is , 2.0.2  :-\  :( i'll install the new 2.3.3 version this week and try again ,  thank you for help any way ^^

"simple modem BT business hub." Pretty sure thats some marketing words and not referring to a "network hub". its probably a router provided by an ISP such as british telecom. Just a guess.

what a helpful forum… well -- the answer is to add a static route to the 10.10.222.1 router to route to the VPN network via the .10.10.222.250 interface.

That completly solve the problem, hope openvpn configuration can have a checkbox to enable this option in the future, and hope information in this topic can help anyone else in the same situation after the upgrade. Thanks Jimp!

i have noticed one user has forget his VPN on while he is on the office, he is connecting with the VPN from the LAN, when i disable his connection VPN start working. is there is a way to fix this ? even when the users forget to disconnect their VPN on the LAN won't cause the openVPN server to crash. is this related to the Crypto: AES-128-CBC/SHA1 D-H Params: 1024 bits we are using?

Morning - anyone have any information regarding this? I need to be able to save the mtu size of my openvpn so after a reboot, it doesn't change back to 1500. thanks