You want to do a one half of Tailscale’s site to site networking documentation and set a route for 100.64.0.0/10 on your router to go through the device that’s got tailscale installed.
Is there a way to route this traffic through my Pfsence router or other local Tailscale machine?
When you say you want to “route this traffic” are you asking how to force all the tv traffic on a different network through tailscale to your “own cloud vpn service”?
Device A - device on local lan, can’t run tailscale for whatever reason
Device B - device/VM on local lan, can run tailscale (presumably Linux)
Device C - Linux VM in the cloud, running tailscale as an exit node.
You want to let device A use device C as an exit node? I’d like to do something similar, and my device B is not my router, it’s just a linux VM on my LAN. Basically I’d like something where I can just set device A’s default route to device B’s local LAN IP (192.168.x.x) and then it’d automagically be routing all it’s traffic over tailscale and onto the internet via device C.
Assuming what I described is what you want, I was able to do it with a VM on my home lan acting as a tailscale router, and a VM living on a VPS in the cloud. If you look below where I’m tinkering on a wholly separate Linux VM running vanilla debian, you’ll see my curl command with my default route set to my router (192.168.2.1) gives me my local IP in North Carolina. If I set it the default route to the VM on my home lan acting as a tailscale router (192.168.2.171) the same curl command shows me an IP in California. The “magic” was an iptables masquerade rule on that home VM tailscale router. I’ll have to tinker with it some, and I’m not entirely sure what other tweaks it needs, but as a basic POC it’s working. I redacted the 3rd and 4th octet of the public IPs
# ip r
default via 192.168.2.1 dev enp1s0
192.168.2.0/24 dev enp1s0 proto kernel scope link src 192.168.2.170
# curl canhazip.com
71.75.xxx.xxx
# ip route replace default via 192.168.2.171 dev enp1s0
# ip r
default via 192.168.2.171 dev enp1s0
192.168.2.0/24 dev enp1s0 proto kernel scope link src 192.168.2.170
# curl canhazip.com
104.237.xxx.xxx
Let me know what you find. I suspect I could move that MASQUERADE iptables rule around…maybe…it was just a quick ‘lemme try this’ but I wanna thoroughly understand what I did, and also see if there’s a better way. I’m also pondering doing the same setup with wireguard and not using tailscale. That WG setup I’m pondering is mostly so I can build it all from scratch to really understand what I’ve done.
Pity, it didn’t work for me.
On the TV I changed the ip gateway to be the same as the local ip address of the device with Tailscale. On that same local machine I also selected the vpn server as exit node.
This local machine did have a connection with the vpn server as required but my TV didn’t get any connection at all. The TV could NOT get any external connection.