TAILMON TAILMON v1.3.0 -Aug 24, 2025- WireGuard-based Tailscale Installer, Configurator and Monitor (Available in AMTM!)

[rung]

Yes, I tried adding all those kinds of those types of commands after those listed. The only fix was to end the autoupdate routine with a tsdown. That way, the main loop detects this and restarts tailscale. I agree it's must be some kind of cache issue with either tailmon or tailscale.


I'm sure a reboot would also work but 1) it's overkill as the change above works for me even though I don't know why and 2) I wouldn't be able to do so remotely if I can't access the router.

Thanks,
Rung

If it helps, here is my config file:

track=0
keepalive=1
timerloop=60
logsize=2000
autostart=1
schedule=1
schedulehrs=3
schedulemin=30
updatetm=1
updatets=1
amtmemailsuccess=1
amtmemailfailure=1
ratelimit=0
tsoperatingmode="Userspace"
persistentsettings=1
exitnode=1
advroutes=1
accroutes=0
precmd=""
args="--tun=userspace-networking --state=/opt/var/tailscaled.state --statedir=/opt/var/lib/tailscale"
preargs="nohup"
routes="192.168.1.0/24"
customcmdline=""

 

[Viktor Jaep]

Yes, I tried adding all those kinds of those types of commands after those listed. The only fix was to end the autoupdate routine with a tsdown. That way, the main loop detects this and restarts tailscale. I agree it's must be some kind of cache issue with either tailmon or tailscale.

That's interesting. I'll have to check that out, and see if it restarts the script itself too in that situation. That might be a more forceful way of getting these services restarted.

 

[Viktor Jaep]

New beta available with some new additions made by @rangermix!

What's new:
v1.3.1b1 - (TBA)
- MINOR: Thanks to a contribution from @rangermix, the capability of forcing the router to use IP Forwarding if it is disabled has been added. His addition will check for the existence of the /proc/sys/net/ipv4/ip_forward (and ipv6) files, and checking they are both set to "1" before enabling this functionality by adding some statements to your init-start file. So this may require a reboot before it will work completely. Apparently this has been a hang-up for several folks now, and this seems to be a working fix. For others (like me), this setting was already enabled, and this code would not interfere with that. Another interesting note is that @rangermix believes this behavior stems from routers being configured in a "repeater mode", and may have these settings turned off by default.

Download link:

curl --retry 3 "https://raw.githubusercontent.com/ViktorJp/TAILMON/develop/tailmon.sh" -o "/jffs/scripts/tailmon.sh" && chmod 755 "/jffs/scripts/tailmon.sh"

 

[rung]

I'm happy to see I have ipv4/ip_forward existing and set to one (and don't seem to have any issues with Tailscale). By the way, do you know the symptoms if this is an issue for someone?

Note: I don't see a ipv6/ip_forward entry. Is it because I don't have ipv6 functionality enabled? Does the code check for that?

 

[Viktor Jaep]

I'm happy to see I have ipv4/ip_forward existing and set to one (and don't seem to have any issues with Tailscale). By the way, do you know the symptoms if this is an issue for someone?

I think @rangermix would need to fill you in on some more of the symptoms, but after some frustration trying to troubleshoot this issue, he found that this fix solved it for him as well:

https://www.snbforums.com/threads/t...d-monitor-available-in-amtm.92874/post-972216

Note: I don't see a ipv6/ip_forward entry. Is it because I don't have ipv6 functionality enabled? Does the code check for that?

Good call... it's actually located under:
/proc/sys/net/ipv6/conf/all/forwarding

 

[rung]

Updated to beta. Checked out a couple of functions. All still working great as usual!

 

[rung]

Good call... it's actually located under:
/proc/sys/net/ipv6/conf/all/forwarding

That I do have and it's 1. Thanks for clarifying!

 

[jksmurf]

That I do have and it's 1. Thanks for clarifying!

Per my check at the time it was raised, mine are both 1 for IPv4 and IPv6.

Good on you @Viktor Jaep for gnawing away at this since October! Not suggesting you’re slow, just dogged…

 

[Viktor Jaep]

Per my check at the time it was raised, mine are both 1 for IPv4 and IPv6.

Good on you @Viktor Jaep for gnawing away at this since October! Not suggesting you’re slow, just dogged…

Truthfully, I wasn't really considering implementing it, but it seems there's more than just 1 person now that has come across this. Huge thanks to @rangermix for taking on the task of getting something formally implemented within TAILMON.

 

[GWater]

Hi All - I really appreciate Tailmon and have been running Tailscale on my router for a while. I've had to compile my own Tailscale due to CG-NAT IP range conflicts as tailscale takes over the whole 100.64.0.0/10 range

Better interop with other users of 100.64.0.0/10 · Issue #1381 · tailscale/tailscale

Tailscale grabs 100.64.0.0/10 for its overlay network. Currently, this translates to things not working right if the underlay network also uses that range: On linux, we install anti-spoofing rules ...

github.com

I wanted to downgrade recently so I used Tailmon to go back to version 1.84.0 (successfully) but when I wanted to install my custom tailscale 1.90.9 ipk, Entware still thought I was on 1.92.3. I use the command:

Opkg install tailscale_1.90.9.ipk

Error:
Not downgrading package tailscale on root

To get around this I fully removed tailscale and then installed again. My long winded question is, does anyone know where Entware might be storing the higher version number after using Tailmon to downgrade? It looks like remnants remain during a downgrade