Did you got some version info back?
Nope, this does not work.
So I have to tell you, unfortunately, I can't help here. I don't know which architecture the CPU needs.
I think it´s this one
https://downloads.openwrt.org/releases/23.05.4/packages/mips_24kc/packages/
I am using the latest GL FW 4.6.3-op24 and it comes with Tailscale version 1.66.4.1, is there a simple way to upgrade to 1.7.0? LuCI software shows package version 1.58.2-r1 as an Upgrade, there is something weird with the packages and their versions, or should I just stay with 1.66.4.1? Thanks
Why not just using the script?
Is it really necessary (from a security perspective) to upgrade from 1.66.4.1 to 1.7.0?
Yes, it is. Updates are always necessary - that's why they exist.
1 Like
I wonder if this is because they use entware packages for embedded devices (do they use them on GLiNet routers)?
Just an observation, as until very recently Tailscale under entware was exactly that, Tailscale v1.58.2-1. but they recently upgraded the enwtare package to v1.68.2-3.
See here for details.
See also the wiki for the ASUS Routers running Tailscale via entware on Asus-Merlin.
I still upgrade anwyay, using admon's great script.
admon - thank you. working well on X3000.
how do I advertise routes on the x3000 after install. what syntax to use the --advertise-routes and --advertise-exit-node.
Thank you.
Can't help with that, I don't use Tailscale - sorry.
I'm very happy to report that this appears to have worked on GL-MV1000 'Brume 1' running 4.3.8 beta 1.
1 Like
Script doesn't work on the X750 Spitz. After the upgrade runs I get "Illegal Instruction" when I run the tailscale/tailscaled binaries.
1 Like
Please run both commands and post the result:
grep 'machine' /proc/cpuinfo | awk -F ': ' '{print $2}'
uname -a
root@GL-X750:~# uname -a
Linux GL-X750 5.10.176 #0 Sun Apr 9 12:27:46 2023 mips GNU/Linux
root@GL-X750:~# grep 'machine' /proc/cpuinfo | awk -F ': ' '{print $2}'
GL.iNet GL-X750
Thanks a lot for the Tailscale update script! I have used it to keep the tailscale version up to date on my GL-AXT1800 Slate AX router.
Unfortunately I still have a few issues listed below using Tailscale on my router. Some of the issues may be general GL.iNet Tailscale integration issues and some may be related to the changes performed by the update script.
- Initially I could not get the router to use an exit node that is configured on my tailnet. This was finally resolved with adding
--accept-routes=truesetting to the exit node's tailscale daemon. This was revealed to me when I executedtailnet upon the exit node while the GL.iNet router was connected to the tailnet. - If I activate custom exit node in the GL.iNet router Web UI it works and routes internet traffic through the exit node. If I deactivate and re-activate the custom exit node the traffic routing does not go through the exit node until I reboot the router, despite the exit node being activated in the Web UI.
- My tailnet has devices that offer subnets and a split DNS service using pi-hole in the advertised subnet. The subnets are visible at the GL.iNet router, but the split DNS is not. I assume that I need to manually configure the router to use the pi-hole for DNS when using tailscale?
Software versions
- Router firmware version: 4.6.2
- Tailscale version on the router: 1.72.1, installed with glinet-tailscale-updater
- Latest available tailscale version on other tailnet devices.
Can you tell me which file you edited for that and which command you replaced?
Can you tell me which file you edited for that and which command you replaced?
I am not sure what you are referring to. If to my first point
- Initially I could not get the router to use an exit node that is configured on my tailnet. This was finally resolved with adding
--accept-routes=truesetting to the exit node's tailscale daemon. This was revealed to me when I executedtailnet upon the exit node while the GL.iNet router was connected to the tailnet.
I did not have to edit or replace anything, but just execute tailscale set --accept-routes on the Linux host where I run tailscale in my network. To clarify I am not referring to using the GL.iNet router as an exit node, but routing internet traffic from GL.iNet LAN through an exit node on my tailnet.
If you are referring to the GL.iNet router, I have not edited any files on it. Just updated tailscale using the update script.
Hey there!
Trying to run this on MT-3000, the script tells me:
[2024-09-12 10:43:34] [→] Detecting latest tiny tailscale version
[2024-09-12 10:43:36] [✓] You already have the latest version.
But my tailscale dashboard says this version is 1.66.4-1 (OpenWrt) so quite old.
running tailscale update does run and complete, and running tailscale --vesion gives me 1.72.1 ...
However I'm aware there's also tailscaled on the system, and it report Warning: client version "1.72.1-tc02a15244-g5c00d019b" != tailscaled server version "1.66.4-1 (OpenWrt)"
I wonder why there are both on the system..
What can I do to update it?
Should I try to use the non tiny version ?
uname -a
Linux GL-MT3000 5.4.211 #0 SMP Wed Sep 4 02:59:17 2024 aarch64 GNU/Linux
/proc/cpuinfo :
processor : 0
model name : ARMv8 Processor rev 4 (v8l)
BogoMIPS : 26.00
Features : fp asimd evtstrm aes pmull sha1 sha2 crc32 cpuid
CPU implementer : 0x41
CPU architecture: 8
CPU variant : 0x0
CPU part : 0xd03
CPU revision : 4
processor : 1
model name : ARMv8 Processor rev 4 (v8l)
BogoMIPS : 26.00
Features : fp asimd evtstrm aes pmull sha1 sha2 crc32 cpuid
CPU implementer : 0x41
CPU architecture: 8
CPU variant : 0x0
CPU part : 0xd03
CPU revision : 4
I just tested it on my MT3000 without any issues.
So I am not sure what is different on your device. Restoring the old version (and updating the firmware to get the newest old version) might be necessary to run my script.
You might try to use the non-tiny version - but I am not sure if it will help.