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.

That was it, thank you!

Good that it works. On that note - is your system clock sane? Cannot imagine why'd something say it's uptodate when it's ages behind.

You have to enter the server sides local subnet or the particular hosts you want to access in "IPv4 Local network(s)".
Try to access the file share by its IP, e.g. \192.168.1.25\share
Bear in mind that Windows firewall blocks access from other network. So allow the access in the Windows firewall or disable it.

Thanks jimp, that did it.

Didn't occur to me since I didn't need to do that for my LAN subnets, but now that I've added an allow for the VPN subnet they can resolve.

Hi,

Answering to myself ;)

There is no need of "local network" option anymore and my problem was a switching issue !!!

I made a firewall rule to allow 10.8.0.0/24 in windows firewall.
That works, but it would be better If I could get it to show private, and not have all traffic go through the vpn.

Publicly signed certs have no business being on OpenVPN and no client would have problems because of that. You're making things much more difficult for no benefit.