Script: Update Tailscale on (nearly) all devices

In that case, your device isn't supported by the tiny version right now. Please use the official Tailscale binary or use --no-tiny

Sorry for the late response.

Running it with “--no-tiny” seems to have installed it but now it needs “tailscaled”? What’s the best way to install that? Is it through the openwrt interface or running another command?

Why do you think it needs "tailscaled"? Where do you read this message?

When I try to use tailscale up, login or other commands, I keep getting “failed to connect to local tailscaled; it doesn't appear to be running”

I was using Tailscale and did run the script to auto-update Tailscale in my Slate 7 as well as set as “persistent”. However, since I no longer use Tailscale, I disabled it through the GL router page.

I now have a quick question, since I no longer use Tailscale (I really never used it much anyway) do I need to “uninstall” your script, or will it not cause any issues leaving it be. If I should need to remove the script, what are the steps and command(s) to do so.

Thanks

You can simply run my script with the --restore flag to remove all adjustments. Not really necessary, but I would recommend it when you don't use Tailscale anymore.

1 Like

Is it a device that never had Tailscale before? In that case, you need to write your own wrapper to run the service. In the tiny binaries tailscale and tailscaled are the same - they will act differently based on the name it gets called with.

Sorry, I’m not that savvy, typing tailscale update in the terminal shows

root@GL-AR750S:~# tailscale update
already running stable version 1.96.4; no update needed

but in openwrt it shows that tailscale and tailscaled are both installed as version 1.32.3-1 for both. I don’t really understand

Sorry, I can't really help here. Something is odd, but I'm not sure what's wrong.

This issue occurs on firmware with fw4 and Tailscale after commit util/linuxfw,wgengine/router: add connmark rules for rp_filter workar… · tailscale/tailscale@26ef46b · GitHub

Could you please check?. @admon

2 Likes

Thanks for the PR! :gl_emoji_woah:
I already merged it and rebuilt the most up to date TS version.

Fix is implemented now :gl_emoji_nice:
People just need to rerun my script to get the fixed version. No need for a restore or anything else since my script uses the internal workflow number as the TS release version.

3 Likes

Quick question, (sorry if this has already been asked and answered) but for most people, wouldn’t ssh-ing into the router and just running ‘tailscale update‘ solve this issue?

Yup. Was asked here:

and answered below it

And yes, you can still ssh in and run

tailscale set –auto-update

1 Like

Thank you, Admon. Some users say the previous change still doesn't fully fix the issue on their side. I've submitted a follow-up PR to adjust the Tailscale nftables connmark behaviour—the current rule was too intrusive for coexisting with other mark bits (vpn policy 0x8000). The endianness patch remains necessary and helpful; this follow-up only tightens the connmark restore rule on top of it.

Merged and rebuilt. Tailscale should contain this fix now.