Document how to announce additional routes on the local network from the HA addon about hass-addons HOT 2 CLOSED

Hey there, sorry you've had such a frustrating time getting it all set up. I've been thinking increasingly often that making userspace_networking the default going forward might be the way to go, would that have alleviated some of your issues?

Also interesting re: ping, I'll get that added to the container when I have a moment this evening hopefully.

from hass-addons.

Hi again,

I'm pushing the setup to some limits there, I'm trying to combine different things like using the addon as a subnet router (that works now), using it also as an exit node (that works too), and combining that with AdGuard (or PiHole) (and then it does not fully work due to some Tailscale tweaking that I can't figure out yet).

I tend to think that none of these capabilities would even work without the userspace_networking activated.

When I installed AdGuard, below are the different networks it can discover. It clearly does not see much of the network beyond the inner virtual network between the HA containers. So I believe that your addon will work "OK" when users will use it only for accessing their HA instance from remote, but any usage where you want to use the addon for accessing any resource outside of the HA host will probably require the userspace_networking flag activated. Well, it's just my personal observation anyway.

I still have lots of questions about advanced setup and the docs from Tailscale only rarely consider the client running in a container. And Tailscale forum is not helping much either.

The question of the "disable DNS" flag is also an important one when you want to use a DNS proxy as mentioned here: https://tailscale.com/kb/1114/pi-hole/ but again it does not take in consideration the container aspect.

At this moment I am advertising local routes, exit node, and userspace_networking and disable_dns are on and everything seem to work except the DNS proxy is bypassed by Tailscale when I use the addon as exit node (DNS is forced to 100.100.100.100 when a tailscale client changes the exit node). And I have small issues between Tailscale and AdGuard addons for which I just opened another issue here.

That's where I'm up to.

from hass-addons.