You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi there,
I'm trying to get my QNAP NAS to use a machine of my tailscale net as an exit-node.
I'm running 1.72.0 on multiple systems - a windows 11 laptop, android 14 and QNAP NAS, and I've setup all three as exit nodes, allowing them in the route settings of the Machines dashboard - see first screen' blue pills.
The issue is that the QNAP tailscale web UI select does not list any exit-node - only the None + Run as exit node options, see second screen. The windows and android tailscale UIs, on the other hand, do list one another as exit node - see also screen, the tailscale windows UI lists the android exit-node.
I've tried toggling on and off exit-node for qnap, but never managed to see the other machines listed. Is this standard behavior or a bug? Thanks for the feedback!
Screen 1, Machines dashboard
Screen 2, exit-nodes listed on qnap and windows
The text was updated successfully, but these errors were encountered:
Hi there,
I'm trying to get my QNAP NAS to use a machine of my tailscale net as an exit-node.
I'm running 1.72.0 on multiple systems - a windows 11 laptop, android 14 and QNAP NAS, and I've setup all three as exit nodes, allowing them in the
route settings
of theMachines
dashboard - see first screen' blue pills.The issue is that the QNAP tailscale web UI select does not list any exit-node - only the
None + Run as exit node
options, see second screen. The windows and android tailscale UIs, on the other hand, do list one another as exit node - see also screen, the tailscale windows UI lists the android exit-node.I've tried toggling on and off exit-node for qnap, but never managed to see the other machines listed. Is this standard behavior or a bug? Thanks for the feedback!
Screen 1, Machines dashboard
Screen 2, exit-nodes listed on qnap and windows
The text was updated successfully, but these errors were encountered: