On a slate 7 pro, turning of routing traffic via a tailscale exit node doesn't turn it off. It looks like it worked in the ui but the exit node is still used. This script actually disables traffic from being routed through the exit node for me
#!/bin/sh
uci -q delete tailscale.settings.exit_node_ip
uci commit tailscale
tailscale set --exit-node=
/etc/init.d/tailscale restart
sleep 2
tailscale status | grep -E 'active|exit node' || echo "no active exit node"
Based on local testing, when tailscale is disabled, the traceroute command shows that traffic is no longer going through tailscale.
It seems the problem cannot be reproduced.
How did you determine that tailscale was not disabled?
Hi,
When tailscale is running and an exit node is used to route traffic, then in the UI I turn off routing traffic via the exit node (but tailscale is still being used), traffic continues to be routed via the exit node (confirmed with tailscale status).
Thank you for your update.
Are you setting the BE10000 itself as the exit node?
Or are you simply enabling a Custom Exit Node on the BE10000 and setting other devices as exit nodes?
If I set BE10000 itself as an exit node, when I disable tailscale in the GUI, executing tailscale status only shows a message indicating that tailscale is not running.
If it's the second scenario, nothing changes.
First I setup tailscale to connect to an exit node that isn’t on the BE10000.
Then I turn off routing traffic via the exit node (but keep tailscale connected)
The UI says the exit node isn’t being used but running tailscale status confirms traffis is still being routed via the exit node (it shouldn’t be)
We've conducted multiple verifications based on this issue, including changing the exit node device, but the problem doesn't seem to be reproducible.
If we disable the custom exit node on the BE10000,
it should normally look like this.
However, the screenshot you provided does seem to have a problem. Can this problem be reproduced reliably in your environment?
If possible, could you share your router with us so we can check it?
Technical Support via GoodCloud - GL.iNet Router Docs 4
If possible, you can send me a private message or send the shared information to our technical support email address (along with the post link).
Thank you.
Hi lucas2
Thank you for taking the time to investigate this issue.
I had updated the tailscale version to 1.98.2 and I see the behaviour as described above.
I reverted back to the default, 1.92.5 and it doesn’t happen.
I then tried the latest version, 1.98.5 and it doesn’t happen.
I hadn’t considered that it would be due to tailscale itself, I apologise for wasting your time.
OK.
Thank you for the update.
So, this issue only recurs when Tailscale is upgraded to version 1.98.2?
Thank you so much for providing the clue.
We will document this issue to help others who encounter similar problems.
1.98.2 has the problem, 1.98.5 doesn’t.
From the changelog I’m guessing it was fixed in 1.98.4.
