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?
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.
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.
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.
Thanks for the PR!
I already merged it and rebuilt the most up to date TS version.
Fix is implemented now
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.
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?
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.