v2.5 broke ExpressVPN Interface to Gateway Monitoring
-
Hello,
After upgrading to PFSense 2.5 on both a SG-3100 and an ProtectLI x86 system, the interface to gateway functionality broke. I’ve taken several screen shots to help explain observations.The OpenVPN connection has been established by using the ExpressVPN guidelines.
OpenVPN client is defined with correct values.
Connection is successful.
However, the monitor IP does not seem to respond and therefore the gateway is marked offline.
Reviewing the Gateway details.
Disabling Gateway Monitoring destabilizes all traffic flow (not just VPN traffic).
Currently I’m not able to route any traffic through the OpenVPN Gateway. The problem is specifically tied to 2.5 and did not exist in 2.4.5.
-
@thaddeusf said in v2.5 broke ExpressVPN Interface to Gateway Monitoring:
After upgrading to PFSense 2.5 on both a SG-3100 and an ProtectLI x86 system,
Hi,
A lot of things have changed (2.5.0) that I can suggest about these:
https://docs.netgate.com/pfsense/en/latest/releases/2-5-0.html
this is always a problem, f.e.:
BTW:
TLS keys + new export client (pfSense) yes these are problems...... :)+++edit:
While SS VPNEVPN allows GW PING, z EVPN does not...
-
A little more information.
I can change the monitoring IP address in the routing>gateways>monitoring to the WAN IP address and the gateway reports good (because it is ping status from the WAN interface).
However, the firewall LAN still report Blue Gateway status and no traffic is routing via the LAN rule.
...
