What changes are needed for site-to-site when wanting to tunnel internet?

[verulian]

I have a setup where I'm needing to bypass CGNAT and some other headaches from an ISP. I basically need ALL traffic to pass through a Linode "portal" node across WireGuard to my LAN with the headache ISP.


I have followed the site-to-site tutorial (https://docs.opnsense.org/manual/how-tos/wireguard-s2s.html) and it works well from what I can tell with communication between the two sites (the Linode doesn't have a "LAN" so to speak, only a singular WAN).


We will call the Linode OPNsense server "Site A". The second site behind the ISP will be "Site B".


I am not understanding how I can make "Site B" (192.168.0.1) act as a gateway that will tunnel all internet traffic across the WireGuard VPN tunnel after connection.


It seems like "Site B" should and does negotiate the connection just fine to "Site A", but the snag comes to me that when this link is established, it should then use the WireGuard link for ALL traffic from the LAN that goes across it to access through the Linode node and IP address.


Can anyone explain or point me to documentation that will explain how to do this with the two OPNsense sites?

[Bob.Dig]

Can anyone explain or point me to documentation that will explain how to do this with the two OPNsense sites?

I can't, but you have to create gateways on both sites and a route on A.