You should not have gateways set on LAN or OPT1. (or possibly OPT2). Only the WAN should have a gateway set for pfSense and that is added automatically for DHCP. When you add a gateway to an interface pfSense treats it as a WAN and that is not the case for LAN or OPT1. Additionally whatever is at 10.0.2.2 is not responding to ping. That's probably because it's the VBox NAT host. You should set some the external IP address for pfSense to monitor on the WAN. Steve

@viragomann It is policy-based tunnel (Tunnel IPv4). Phase2 is working (status connected). Status->SystemLogs->IPSEc has no corresponding entries. But you said " and the subnet is not routed through the tunnel": This is exactly the problem - how to do this? As there are no thus options in the IPSec tunnel settings ("NAT/BINAT translation" should not be the corresponding option.)

@viktor_g Thanks for your help.

So what I discovered is that the no protocols are being set (checked) for the TAP-Windows Adapter during installation of the OpenVPN client. Why would that all of a sudden change when nothing else changed from the OpenVPN end? Still using same process. Still using same version of client, etc.