I take my shitposts very seriously.
How did you set up subnet advertisements on the router, and which subnets? Did you touch the ACL in the tailnet’s admin console?
On the home PC, did you accept advertised routes with the Tailscale client?
What happens when you ping a host on the LAN using tailscale ping ADDR? What happens when you try to tracert or tracepath to it?
Perhaps there was an easier lighter-weight way of doing this?
sshuttle does exactly that. It’s basically a VPN that uses SSH tunnelling. If you have a host in the same network as the target machine, and you can SSH into it, sshuttle can route all TCP traffic between you and the target (or a subnet) through the host without having to bind local ports manually.
sshuttle -r ssh_server <hosts/subnets...>
deleted by creator
Minio is about to get Redis’d.
I use self-hosted services in the following categories as much as possible…
That question could really use a “not applicable” option. I don’t operate any home automation solutions, so any answer from me would be invalid, and neutral answers because the item is not relevant will appear the same as neutral answers because I use both self-hosted and externally hosted solutions (e.g. Mullvad for privacy and Tailscale to get around CGNAT).
You're officially an asshole.
This is a joke, see git-blame-someone-else
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.