I did run into various bugs involving interfaces != LAN. One common one is that
the other interfaces are missing a default allow rule for reaching pfSense on
53/udp. This makes all your DNS requests fail and then it can seem like none of
your stuff is working. Another problem you can find is, if
you are missing something like ca certificate that is used to verify remote
endpoint
routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
Dec 24 00:53:16 openvpn 10563 VERIFY ERROR: depth=0,
error=unable to
get local issuer certificate: C=VG, ST=BVI, O=ExpressVPN, OU=Ex
On Fri, Dec 22, 2017 at 8:25 PM, Antonio wrote:
> Hi,
>
> I'm not sure how you move traffic between the above interfaces. I was
> under the impression that all you needed was a "Default allow LAN to any
> rule" and job done. Yet i'm struggling to get devices of different
> interfaces to communica
Hi,
I've tried to set up a VPN tunnel using the this guide (
https://www.expressvpn.com/support/vpn-setup/pfsense-with-expressvpn-openvpn/#additional
) which covers the setting up of the tunnel and relative firewall rules
for ExpressVPN. However, it seems like I was having trouble at the early
sta
