On the GL-MT1300 (I know not officially supported) it uses the MIPS package. However I had to tweak your script to install the mipsle as mips errors when trying to start (EOL errors).
Asking around, I just updated my AXT 1800 to the latest version Tailscale using the script provided above, was working fine before with the last version of tailscale, now the custom exit node does not work at all. Also, tried to re-bind device and I get an error stating "operation timed out" and just hangs there trying to do something. I try binding thru SSH and with the link it provides me and seems to "bind device" but again the "custom Exit node" seems not to be working on my end. I've have no trouble with connecting to my all my sites if I use any other devices. Just wondering if anyone had any issues after this latest update with their routers?
Custom exit node is only supported if you modify the startup scripts since the option isn't provided by default in the GL firmware. You need to add the corresponding argument to the startup script then.
Need to vi into /usr/bin/gl_tailscale and add --advertise-exit-node to the following line which is right at the end of the file. Then just reboot or presumably restart tailscale and it will show up as an exit node.
/usr/sbin/tailscale up --reset --accept-routes $param --timeout 3s --accept-dns=false > /dev/null
If I misunderstood this and you meant using another exit node I only got that working by using the mullvad addon. Never tested another exit node so not sure if it will properly detect those but I was able to use the mullvad addon in testing and select the router then it showed up with a list of IPs to use as an exit node for the router.
Yes not using the router as a exit node but using it to connect to other exit nodes within my tailscale network.
Like I mentioned, it was working fine until the latest update to Tailscale that I ran into this problem
Looks like the other poster had the same problem that I am having too, I tried the command the poster listed for the MT3000 and it didn't seem to work for me on my end...
If this is the cause of my problems, how would I revert back to TailScale v1.64.0 since it was the last version that worked for me?