WireGuard between pfSense and OPNsense, pfSense don't add route as OPNsense do?

[iorx]

Hi,

Its-me-again! My journey into OPNsense makes progress. Fun stuff!

I banged my head a while on this one.
First try. Two OPNsense connected with WireGuard. This was a "walk in the park" when I figured out what goes where. Felt like Captain Slow before that...  ::)
Second attempt connecting a OPNsense and pfsense together. I read allot of the guides and tips on the subject.

At first I couldn't get traffic from pfSense to OPNsense. Found out that WireGuard on pfSense had not created routes required. To get pfSense-WireGuard to create routes it required allot more. Assign interface and create routes manually.
OpnSense has no such problem, routes where present without assigning an interface and creating routes manually.

So, I got this right? This is this "easy" on OPNsense and all that trouble on pfSense?
I understand the point of creating an interface, but in my case here I don't see that I need one.

[mimugmail]

You only need to assign and add a gateway If you have Special needs like route your guest net via WG Tunnel but LAN on plain internet

[iorx]

Got it!
No need for that in this particular scenario. But I may need it later on.

On my "remote" OPNsense.
Adding subnet to "Endpoint" Allowed IPs adds the route. Simple.

On the soon to be replaced pfSense at my home office.
Doing the same under pfSense "Peer" (aka EndPoint) nothing is added and it has to be done manually.
This instance have a couple of VLANs defined, guest-net, iot-net, game-net..., they could be candidates for routing through the tunnel but really not a have to.

Brgs,