If you have configured that tailscale node as Subnet Router or Exit Node then yes, that is supposed to happen.
this post was submitted on 12 Jul 2023
1 points (57.1% liked)
Selfhosted
39435 readers
4 users here now
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 1 year ago
MODERATORS
Awesome. Well that's even better than using the 100.xxx addresses
Depending on how you set up your on-LAN tailscale hosts, you may have included --advertise-routes=<your lan CIDR> and then I think you need to --accept-routes on other clients for them to actually set up the local routes that use the wireguard connection, but that would likely explain the behavior you're seeing unless the behavior was updated to make this automatic.
Are you talking about addresses like 192.168.x.x? Do you have subnet routing enabled in Tailscale?
view more: next ›