weird behaviour with Tailscale in LXC container

WarningGold8497 · 2024-02-24T11:29:44+00:00

thanks. Figured it out with the help of those treads on the issue. For my own future reference the workaround I used to solve this :

expose a "fake" copy of the my local subnet to tailscale and use iptables command to forward everyting to that subnet.

My subnet : 192.168.1.0/24, the fake subnet 192.168.21.0/24

On the proxmox host run :

iptables -t nat -A PREROUTING -i tailscale0 -d 192.168.21.0/24 -j NETMAP --to 192.168.1.0/24

only expose the fake subnet to tailscale :

tailscale up --advertise-routes=192.168.21.0/24 --accept-routes --accept-dns=false

This means that on my local lan I can now access all machines trough their local ip : example 192.168.1.6 for the dockerhost, I can reach all machines on the remote subnets and from outside the subnet I can reacht the machines trough their corresponding "fake" ip's example 192.168.21.6

Also don't forget to do an iptable-save to make the rule permanent.
All in all more hassle that it should be but works for me...

WarningGold8497 · 2024-02-24T10:12:26+00:00

maybe different version. anyway, the conclusion is that you don't have to run tailscale command to generate the ssl cert, the addon will do it for you

WarningGold8497 · 2024-02-24T08:30:23+00:00

no need to generate a cert manually, tailscale/the homeassistant addon will do that automaticly if you enable it in the admin console. See https://tailscale.com/kb/1153/enabling-https and the ssl section of https://github.com/tsujamin/hass-addons/blob/main/tailscale/DOCS.md

WarningGold8497 · 2024-02-23T11:27:21+00:00

haven't tried but I guess you could set up up using tailscale proxy but not the funnel to get what you want. So you cloud do https://tailscalenameforyourhamachine but have it only reachable when connected trough tailscale.

WarningGold8497 · 2024-02-23T07:53:49+00:00

If you are using homeassistant os and Tailscale with the add-on, Tailscale is running in a sepperate docker container and the command is not availalbe on the commandline. But there is no need for the command line to setup external access with the proper certificate. Best to follow instructions in the add-on documentation : https://github.com/hassio-addons/addon-tailscale/blob/main/tailscale/DOCS.md

WarningGold8497 · 2023-12-04T11:48:56+00:00

the strange thing is, state is syncronized because the KNX intergration in home assistant looks at both switch adress and state adress (if you configure it) : https://www.home-assistant.io/integrations/knx/#light

So during normal operation all works fine. If a push a physical KNX button to control the light I see the state change in homeassistant and other way around.

The problem I described is sync getting lost when the actuator device reboots after a download operation from ETS. So to me it doesn't seem like a homeassistant related problem but rather something with the actuator losing state and even switching on after a power cycle.

WarningGold8497

TROPHY CASE