Odd setup with opnsense wireguard and udmpro

[jhawn]

So to start off with im using a udmpro at my office, we have a few remote sites that are going to be running opnsense. udmpro is acting as wireguard "server" opensense is a peer on the network.

There are services I need to hit on each of the client sites from the main office for reports.

What I have right now is the vpn connection is up. I cant ping the remote site over the vpn, but remote site clients can hit the udm at the gateway address.

I tried a few things and never see any changes... let me know what you need.

[Patrick M. Hausen]

Firewall rules on OPNsense for the WireGuard interface - did you create one on each of the remote sites? You need to explicitly permit traffic originating from the central site in, WireGuard does not create any automatic firewall rules.

The traffic originating at the remote towards the central site is probably permitted by the default rule on LAN.

[jhawn]

So I have some rules I made from following this https://docs.opnsense.org/manual/how-tos/wireguard-client.html

its the road warrior setup,

I tried making fire wall and nat rules, but I never got any closer.

main site we will call network a is 192.168.6.0/24
site b is 10.160.0.0/16 wireguard address is 192.168.14.2

wire guard 192.168.14.0/24

I have no idea what rule would fix?