this post was submitted on 06 Jun 2025
37 points (95.1% liked)

Selfhosted

46688 readers
395 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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. 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.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

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

Questions? DM the mods!

founded 2 years ago
MODERATORS
 

I encountered something I don't quite understand, and I was hoping someone could enlighten me.

I set up Tailscale on my router with subnets, so I could remotely access my home network. This worked great. Then, at home, I was happily browsing the internet on my main PC, and decided to dial into another machine on my network. It couldn't access it at all. Disconnecting Tailscale on my main PC restored lconnectivity.

I don't understand what is happening here- the only thing I can think of is that my internet traffic was being routed through Tailscale, but I don't have an exit node.

TL,DR: home PC sees Internet but not LAN when connected to Tailscale, why and how fix?

you are viewing a single comment's thread
view the rest of the comments
[–] gazter@aussie.zone 1 points 2 days ago (1 children)

I set up subnet advertisements by doing tailscale set --advertise-routes=192.168.1.0/24. I did not touch ACL.

The home PC is Windows, the context menu for the tray app give the option to 'use tailscale subnets' which is enabled- I assume this is the equivalent of accepting advertised routes.

From the home PC, tailscale ping 192.168.1.2 returns a pong, from the tailscale IP. tracert fails.

[–] rtxn@lemmy.world 1 points 1 day ago

That's unfortunate, I have no idea how Tailscale does routing on Windows. Try running the client without accepting any subnet advertisements.

I've also found this: https://tailscale.com/kb/1023/troubleshooting#lan-traffic-prioritization-with-overlapping-subnet-routes The solution might be to advertise a larger subnet (e.g. 192.168.1.0/23) to make the route advertisements on the tailnet less specific than on the LAN. Advertising a larger subnet won't cause any additional issues because it's in a private IP range.