addon-wireguard VS wireguard-docs

I am fairly new to Wireguard and set it up using the add-on from Home Assistant. Git Link

There are three major cloud components. Alexa and Google integrations both have open options that are documented by NC and you are welcome to use them. There’s a lot of setup as you need to deal with a semi-complex config on AWS or GCP which can be challenging if you’re new to those environments, but they work as well as the paid NC option.

The remote access proxy service doesn’t really have an open equivalent but there are tons of other supported solutions out there for secure remote access to your Home Assistant install. One example add-on, developed and supported by an NC employee: https://github.com/hassio-addons/addon-wireguard

In short, the paid cloud services provide an easier path to solutions you can deploy for yourself if you wish. Those services cost NC money to host, so asking for money isn’t too far out there. Of course, that money is more than what the cloud parts cost, and what we all get in return is a team of skilled developers working on the project and releasing everything for free.

I'm running two Raspberry Pi 3 B+ on my network. One is running PiHole (w/ DHCP Server), and the other is running Home Assistant OS with WireGuard (https://github.com/hassio-addons/addon-wireguard).

Home Assistant Wireguard Addon: Interface: wg0 Tunnel Address: 172.27.66.1 Docker IP: 172.30.33.6 Homeassistant Address: 192.168.0.80 Docker added ip route add 192.168.1.0/24 dev wg0 Homeassistant added ip route add 192.168.1.0/24 via 172.30.33.6 Allowed IP: 172.27.66.4/32, 192.168.1.0/24

I can’t find info about this in the quickstart guide. Are these the docs you’re talking about?

I think the official documentation is clear enough on the settings, and I don’t think the project can necessarily be blamed for others misinterpreting it. True, the AllowedIPs label can lead to some confusion for those who don’t read the docs. I think of it as those destination IPs that can be reached through the peer, and those source IPs that are accepted from the peer. See also this site: https://docs.sweeting.me/s/wireguard

You prolly should give a /32 on your interface ips. Here is this as well https://github.com/pirate/wireguard-docs. I don't understand exactly what you are trying to do, but if you are trying to pass traffic anywhere you need to enable packet forwarding at the Kernal level.

By the way, look at https://github.com/pirate/wireguard-docs

Thanks for the reply. I'm not sure which missing lines you're referring to though? According to this documentation, PostUp is used to run a command after the interface is initialised (same for PostDown, which apparently runs a command after the interface is deleted), but I'm not sure what commands exactly I'd need to run PostUp or PostDown for?

Find more example commands for inspecting the interface at https://github.com/pirate/wireguard-docs#inspect.