Fixing Linux Tailscale Exit Node Routing Rob Allen I run a tailscale network so that remote computers can access local services. i also have a linux box at home on that network that advertises itself as an exit node and recently noticed that it wasn’t working. If you want to access devices on the local subnet of another node (the exit node's lan), you need to set up that node as a subnet router and advertise the relevant routes.
Routing Tailscale Exit Node Traffic Via Non Default Gateway In Pfsense Route all non tailscale traffic through an exit node. use suggested exit nodes to automatically use the best exit node based on client information, such as location and latency. To stop a device from using an exit node, go to the exit node section and select none. you can turn off routing through an exit node by selecting none from the exit node drop down. route traffic through a specific device in your tailnet, and configure devices to use an exit node. Exit node doesn't route all traffic. i have setup tailscaile on a number of machines, including a linux vm in my home lab. i advertised that vm as an exit node, and i can use it as such. all "regular" traffic goes trough it, web, ping, ssh, whatever. Meanwhile, a subnet router enables you to access resources on a remote network through your tailscale connection. this tutorial will guide you through configuring both features on an ubuntu server.
Routing Tailscale Exit Node Traffic Via Non Default Gateway In Pfsense Exit node doesn't route all traffic. i have setup tailscaile on a number of machines, including a linux vm in my home lab. i advertised that vm as an exit node, and i can use it as such. all "regular" traffic goes trough it, web, ping, ssh, whatever. Meanwhile, a subnet router enables you to access resources on a remote network through your tailscale connection. this tutorial will guide you through configuring both features on an ubuntu server. For some reason, bodhi pve4 is not showing as offering an exit node when viewed either from linux or windows though it is doing so on the tailscale machines dashboard. I have setup and got working as per instructions. i can reach the local lan and remote sub nets, and access resources. confirming forwarding and nat are working. the exit nodes work fine with all tail scale clients. this works fine when using wire guard gateways. Problem tailscale 1 provides zero config mesh vpn built on top of wiregaurd. it provides an option to use an exit node for routing all traffic through it. but it can't route only specific domains through the exit node. solution setup a socks proxy using ssh command line tool. I set up tailscale years ago but only used it for “reach my own devices” use cases. this week i finally set up a proper home exit node: a tiny dedicated lxc on my proxmox box (1 vcpu, 512 mb ram, basically just tailscale). to verify it worked, i pinged my home servers and they worked.
Comments are closed.