Open lucius346346 opened 10 hours ago
Did you try it with the IP addresses? That should work.
DNS requires additional steps to work. I think I will add that to the docs.
Update: See #376
If I ping IP address it just hangs indefinitely (100% packet loss). Same thing happens when I use Home Assistant Tailscale IP itself.
Please check the add-on's config with the YAML view, do you really have that userspace_networking: false
line? The HA add-on UI is broken, you click-clik-save-restart, but in reality you don't have this config line at the end. Though if you have, and you have the tailscale0 interface on your host, it should work, I've tested it a few minutes ago with a vanilla HA VM + TS add-on config, and ping worked with IP.
OK, scratch that. IP does work, the addon just crashed. Thank you for the help!
OK, scratch that. IP does work, the addon just crashed. Thank you for the help!
Crashed?!?!?! Please, please send me the logs (if you don't want to post it here publicly, you can find my email in my github profile). I currently work on healthcheck, and really interested in anything that breaks TS or TS add-on.
Description: I cannot connect to other Tailscale nodes from my Home Assistant OS instance running in a virtual machine.
Steps to Reproduce:
Expected Behavior:
Actual Behavior: When I ping other Tailscale nodes, I receive a "bad address" error.
What I Tried: Disabled the "Userspace networking mode" option.
Environment: Home Assistant OS running in a virtual machine. Tailscale add-on installed.