OVPN client unable to ping LAN other side of site to site VPN

kwriley87

I have two PFSense firewalls connected with an IPsec site to site VPN tunnel.

LAN A: 192.168.0.0/23
LAN B: 192.168.5.0/24

LAN A can ping firewall on LAN B
LAN B can ping firewall on LAN A

LAN A PFSense is running an OVPN server issuing 192.168.200.0 IP addresses. The issue is that LAN A OVPN clients are unable to ping LAN B firewall at 192.168.5.1.

I've defined a route on the OVPN server residing on LAN A under its custom options:
push "route 192.168.5.0 255.255.255.0"

I can confirm that this route is established after connecting my OVPN client by issuing a ROUTE PRINT command on my PC:
Network Destination Netmask Gateway Interface Metric
192.168.5.0 255.255.255.0 192.168.200.1 192.168.200.2 257

There is a Phase 2 (tunnel) configuration set up on the LAN A firewall for IPSec for OVPN traffic as follows:
Local Subnet: 192.168.200.0/24
Remote Subnet: 192.168.5.0/24

See below:
Phase 2 Config

However, I am still running into the issue of not being able to ping the firewall on LAN B (192.168.5.1) from LAN A OVPN connections.
From diagnostics > ping, I run a ping test to 192.168.5.1 from the OVPN server and am unable to get any replies.

Can someone please point me in the right direction? I would greatly appreciate it!

kwriley87

Ahh this is resolved. Would have helped to read the post directly below mine...
https://forum.netgate.com/topic/183242/how-to-route-traffic-from-openvpn-remote-clients-to-subnets-through-site-to-site-tunnels

Creating a P2 for the other site of the OVPN network on the LAN B firewall resolved this issue.