You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Tailscale addon not routing traffic from LAN to Tailscale
Expected behavior
Since my tailscale on HASS is acting as a subnetrouter, it's routing traffic from Tailscale to my LAN, the other way around should also be possible.
Actual behavior
traceroute 100.84.130.100
traceroute to 100.84.130.100 (100.84.130.100), 64 hops max, 40 byte packets
1 192.168.178.1 (192.168.178.1) 5.353 ms 2.572 ms 2.309 ms
2 192.168.178.3 (192.168.178.3) 4.191 ms 2.893 ms 3.061 ms
3 * * *
I created a static route on my firewall for destination: 100.0.0.0/10 to 192.168.178.3 (my HASS IP)
When I ping 100.84.130.100 (IP from another client in my Tailscale) from HASS I get a instant connection. When I ping / traceroute that same IP from any other device without Tailscale installed it hangs at 192.168.178.3. (see above for the traceroute)
Proposed changes
N/A
The text was updated successfully, but these errors were encountered:
Do you really need snat_subnet_routes: false? This requires much more config everywhere. To access other TS devices, or other subnet devices behind other TS devices, from your LAN, you don't need this. With snat_subnet_routes: true it just works.
If you really want full blown site-to-site networking (ie. using snat_subnet_routes: false), please follow steps from step 3 on Site-to-site networking? - Yeah DOCS.md says steps 2-3, TS changed the docs, DOCS.md will be updated.
Problem/Motivation
Expected behavior
Actual behavior
Steps to reproduce
I configured my hass-tailscale-addon as follows:
I created a static route on my firewall for destination:
100.0.0.0/10
to192.168.178.3
(my HASS IP)When I ping
100.84.130.100
(IP from another client in my Tailscale) from HASS I get a instant connection. When I ping / traceroute that same IP from any other device without Tailscale installed it hangs at192.168.178.3
. (see above for the traceroute)Proposed changes
The text was updated successfully, but these errors were encountered: