search

hassio-addons / addon-tailscale

Tailscale - Home Assistant Community Add-ons
MIT License
211 stars 75 forks source link

Subnet Routes not working with Headscale #384

Closed mFabio98 closed 3 months ago

mFabio98 commented 4 months ago

Problem/Motivation

Subnet Routes not working with Headscale.

Expected behavior

After specifying the subnet route in a '192.168.1.0/24' fashion, and accepting the subnet advertising server-side, the tailscale client should expose the subnet.

Actual behavior

Instead of exposing to the tailnet the whole specified subnet, the addon manages to expose just the IP address of the home assistant machine.

Steps to reproduce

It's quite involved. VPS running headscale, headscale-admin. Attached the log line I think is most relevant.

Proposed changes

I'm not even remotely qualified to fill-in this field.

image

lmagyar commented 4 months ago

Does this mean, that you can't access anything on the 192.168.1.0/24 subnet from your phone?

Note: The add-on basically sets the parameters of the TS cli, so if TS has any problem with Headscale, it seems to be a TS/HS issue.

mFabio98 commented 4 months ago

I can access only the IP address of the machine running home assistant (IP 192.168.1.10, for example). Any other IP in the subnet is not accessible, including the gateway (192.168.1.1)

I've tried a few solutions and managed to resolve the issue by switching to a different addon (now i notice published by you @lmagyar): https://github.com/lmagyar/homeassistant-addon-tailscale. With that it works as expected.

lmagyar commented 4 months ago

OK, good to know, then it really seems to be a TS issue: this "official" add-on is on TS v1.66.4, my add-on is on TS v1.68.1 - nearly all other stuff in these two add-ons are equivalent. A new release of this official add-on will fix this issue.

Note: In the past I've experimented with new features, some improvements, there were big differences, but nearly eg. got merged into this official add-on.

mFabio98 commented 4 months ago

OK great, I can try again this 'official' addon once it gets updated to confirm whether the issue was solved or not. Many thanks for your support.

github-actions[bot] commented 3 months ago

There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues. Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!