Access entire local network through Wireguard tunnel

Hey folks, sorry if this is a common question but I’ve been all over Google/DDG and can’t find all the pieces I need. If there’s an answer I missed, please feel free to link it from here and maybe this page will direct anyone else who might be lost. :slight_smile:
Running Home Assistant and the WireGuard addon on Home Assistant OS, all updates applied. My home network uses 192.168.0.0/24. My WireGuard server config looks like so:

addresses:
  - 172.27.66.1
dns:
  - 172.30.32.1
host: myhostname.duckdns.org

DNS is hosted by AdGuard and also works. Here’s a sample peer for my phone, which also works in that I can connect to Home Assistant and DNS:

- name: pixel4a5g
  addresses:
    - 172.27.66.7
  allowed_ips: []
  client_allowed_ips: []

With that, I can access Home Assistant on 172.30.32.1. But I’d like to access other addresses on my 192.168.0.0/24 address space, including HA at its canonical address of 192.168.0.2. I’d also like to route everything over WireGuard so traffic gets the benefits of AdGuard.

I can’t tell whether this is just a matter of enabling ip_forwarding, which apparently is impossible in the addon due to it being on a read-only FS, or whether this is or can be enabled in Home Assistant OS. Or maybe I need to set up a route? All the examples I’m finding are either simple and just seem to set up a single client, or are more complex and route traffic through multiple WireGuard clients connected to remote VPSs. In this case, I just want to access 192.168.0.0/24 through the addon hosted at 172.27.66.1.

Thanks for any help, and again, if I missed a good post or guide then feel free to link me to it. I suspect there may be something in the long WireGuard addon thread, but there are hundreds of posts and skimming them was taking forever.