Router passing traffic, but unpingable and sometimes not passing ICMP

I have an odd situation, that so far I haven't been able to find a solution to. Perhaps I am googling the wrong terms?

I have two campuses linked by an inter-office bridge, using a Cisco RV130 VPN/Firewall. In this example, the bridge is 192.168.2.253 on one side and 192.168.1.253 on the other. I've been having inter-office connectivity issues, manifesting in two weird behaviors:

1) ICMP packets, for the most part (see behavior 2) seem to pass over the bridge just fine. Tracert from 192.168.2.11 -> 192.168.1.15 shows packets hopping at 192.168.2.253 and complete as normal. If I try to ping 192.168.2.253, it times out. This behavior is seen on multiple devices on the 192.168.2.0 subnet. Pinging 192.168.1.253 from the 192.168.1.0 subnet completes without issue.

2) When passing over the bridge, I am not able to ping some devices, but I am able to access the device's web interface. Ping requests for as expected on all other devices within the same subnet as the target. So for example, from 192.168.2.1 I can ping 192.168.1.1, 192.168.1.10, but not 192.168.1.20. From I AM able to ping 192.168.1.20 from 192.168.1.10 so I know that the host is responsive to ICMP

Checking the router, there are no ACLs that should be affecting ICMP packets.

Has anyone ever seen similar behavior?