Selfhosted

39435 readers

1 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:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago

MODERATORS

[email protected]

Confused - Tailscale allows me to reach the original IP Address of my nas (sh.itjust.works)

submitted 1 year ago by [email protected] to c/[email protected]

5 comments fedilink hide all child comments

Is this supposed to happen? I thought it assigned a special ip and that's the one you use. For me I'm able to access my original local ip address outside my network, and from the provided tailscale ip. luckily when I turn off tailscale I can't access either.

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 2 points 1 year ago* (last edited 1 year ago)

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.