The status, as shown, is the status output directly given from OpenVPN. We do not correlate that with internal info in any way. We could try, but it wouldn't necessarily be a proper match. It's safer to just show what OpenVPN gives in these cases.

The config is correct. I noticed that other logs are not writed since some days ago. For example work: General Firewall IPSec Not work: Gateways DNS Resolver Open VPN NTP

Hi altiris, I had the same problem. The key-direction 1 in the .ovpn file should be before the <tls-auth>section and not after. I think it is a bug in the auto-generated file. key-direction 1 <tls-auth># 2048 bit OpenVPN static key –---BEGIN OpenVPN Static key V1----- ...</tls-auth></tls-auth>

I have tried aes128 and was pushing 70 mbit at max. That's more than half my speed. Pity! Thanks for your help though.

If your goal is to have the traffic from your home go to your VPS then out to the internet, then yes you have it backwards.

That is a use case for policy routing. See the many, many threads about only sending traffic from certain hosts to, for instance, PIA. You will just need to alter the rules to match certain destinations instead.

Never mind… sorted it now, changed the Gateway on the LAN interface to that of the Watchguard. Tested to make sure that clients on the SBS2011 network couldn't use the pfSense as a gateway to circumnavigate the Watchguard - it still picks up their originating IP and asks for authentication.

It works! Thanks guys :D I needed to NAT the VPN which seems obvious now. I did NAT before, but I probably had some other setting set wrong at that time.

Thank you very much…it worked

Did you figure out or get answers. I previously had expressvpn working with 3 client locations in a gateway failover configuration with opnsense 16.7.9. gateway monitoring was working fine with google dns servers After the system upgraded to 16.7.10, i decided to move to pfsense think there was more support and user base, but haven't found it yet. I have the issue like you. 3x vpn clients, gateway config - getting offline due to 50% errors when using opendns or google dns servers as the monitoring addresses. It seems to be ExpressVPN not passing ICMP as best as i can tell. If i traceroute from ubuntu it goes through without error, but if i traceroute with "-I" or from windows I get request timeouts at the same spots where i get packet loss using dpinger from the command line on pfsense.

Thank you very much Mr. Derelict. My VPN is working now :)

Redirect Gateway needed to be set on the client specific override. The server settings' "IPv4 Local network" and "redirect gateway" weren't needed.

i can upload at 120mb so why cant my brother with his 100mb nearly max my line out.  i get 30/40 tops Mat

You're probably right. I may make it even simpler and just install the client directly onto a dedicated VM, that way the VMPC itself will just tunnel out and I don't have to deal with getting it all working in PFSense, routing, etc. Thanks for the suggestions.

" i've managed to solve my problem by upgrading from the stable branch to the development release" That sure and the hell was not the issue… Not sure what you did, but upgrading to a nonstable dev release would not be what I would suggest.. So while the process of doing the upgrade - maybe you did a clean install and didn't try and nat your inbound connections.  No idea but running dev your more than likely going to run into other odd issues.