TAILMON TAILMON v1.3.1 [2026-Mar-01] - WireGuard-based Tailscale Installer, Configurator and Monitor (Available in AMTM!)

[XIII]

You can try using a shorter more high quality cable. That, or finding a powered enclosure.

I'm not sure my Verbatim enclosure uses a standard cable?

A powered enclosure might indeed be a good thing if I keep experiencing problems with this one.

 

[Viktor Jaep]

This has certainly had enough time to cook, and getting this out the door... huge kudos to @rangermix for his contributions!

What's new!?
v1.3.1 - (March 1, 2026)
- 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.
- PATCH: Changed the date/time to include the offset alongside the timezone. This is to give more visibility for those who aren't assigned a standard timezone name, and in some cases would fall back to using "GMT". Thanks to @Tarek Yag for reporting this, and for @EmeraldDeer providing a deep dive into the date command options.

Download link (or update directly within TAILMON/AMTM):

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

Significant Screenshots:
None today!

 

[XIII]

Unfortunately I did not install knock.sh yet...

Wouldn't have helped! I had to physically disconnect and reconnect the SSD for it to be recognized again... (looks like the cable was not properly connected to the enclosure)

Good thing (and on-topic...) is that TAILMON indeed now only mailed my every hour instead of every minute!

 

[Viktor Jaep]

Wouldn't have helped! I had to physically disconnect and reconnect the SSD for it to be recognized again... (looks like the cable was not properly connected to the enclosure)

Hopefully that's the fix!

Good thing (and on-topic...) is that TAILMON indeed now only mailed my every hour instead of every minute!

Glad you were able to find some rate limiting relief!

 

[rung]

Wouldn't have helped! I had to physically disconnect and reconnect the SSD for it to be recognized again... (looks like the cable was not properly connected to the enclosure)

Good thing (and on-topic...) is that TAILMON indeed now only mailed my every hour instead of every minute!

Does that explain why ssh didn't work? Would a reboot regain that access?

 

[XIII]

Does that explain why ssh didn't work? Would a reboot regain that access?

After a reboot I regained access via SSH, but the SSD was not recognized until I re-attached it / the cable.

I still don't understand why I can't SSH into the router when the SSD goes "down". The web interface did not work either, but WiFi/internet was still working... (for other devices on the LAN)

 

[jksmurf]

Does that explain why ssh didn't work? Would a reboot regain that access?

That’s a great question; a reboot fixed my remote unit once or twice. So if knock could bypass ssd and force a reboot then it’s worth its weight in gold

 

[rung]

Did the massive entware update remotely. Would not work over Tailscale, but worked over the backup Wireguard server. No issues. Tailmon detected the configuration mismatch after the update and fixed itself. Updated screen appears to be working for Tailmon and Knock. Will keep an eye on them.

 

[jksmurf]

Did the massive entware update remotely. Would not work over Tailscale, but worked over the backup Wireguard server. No issues. Tailmon detected the configuration mismatch after the update and fixed itself. Updated screen appears to be working for Tailmon and Knock. Will keep an eye on them.

Funny . Yep... that's what happened to me too, only on the update though; thank goodness for the WG backup.

 

[alan6854321]

@rung @jksmurf - does Tailmon start automatically for you when you reboot the router?

 

[jksmurf]

@rung @jksmurf - does Tailmon start automatically for you when you reboot the router?

I'm not sure how many folks would reboot to check for you but anyway... yes.
p.s. I do not use sceen.
p.s. You may like to post your issue... with error messages ... steps taken to reproduce (the error, not you ...)

 

[alan6854321]

I'm not sure how many folks would reboot to check for you but anyway... yes.
p.s. I do not use sceen.

View attachment 71137View attachment 71138View attachment 71139

No, that's not what I mean. I'm talking about the Tailmon process, not tailscale itself.
It doesn't start automatically for me, and a couple of other people.
We've been posting about it in the Entware thread...

Entware - Okay to install entware update?

I am having an issue syslog-ng on my mesh nodes only. Twice now I have found syslog-ng not running and had to start it on all three mesh nodes. This is what I am seeing in the messages file. Digging myself a bigger hole. 1) Tried rebooting node. ( syslog-ng stops after a period) 2) Attempted...

www.snbforums.com

 

[jksmurf]

No, that's not what I mean. I'm talking about the Tailmon process, not tailscale itself.

Well then, I think you will need to be slightly less unambiguous with your queries. I have many qualities, but telepathy is not one of them .

It doesn't start automatically for me, and a couple of other people.
We've been posting about it in the Entware thread...

OK... mostly seems to be related to screen (hence my comment above).

Entware - Okay to install entware update?

I am having an issue syslog-ng on my mesh nodes only. Twice now I have found syslog-ng not running and had to start it on all three mesh nodes. This is what I am seeing in the messages file. Digging myself a bigger hole. 1) Tried rebooting node. ( syslog-ng stops after a period) 2) Attempted...

www.snbforums.com

All I can say is what I did.

IIRC, I updated entware, then saw the TS binary had dropped to the version in the new entware pkg, then I went into Tailmon and updated the TS binary from there and then all was OK after that.

I did this on two separate networks.

 

[alan6854321]

Hi there,

I run a script overnight (Not BACKUPMON - sorry!) which uses tar -zcf to compress/backup my full USB SSD to my NAS.
Since the "Big Entware update", it gives the following warning...
tar: ./entware/tmp/screens/S-AsusAdmin/8838.tailmon: socket ignored

Anything to worry about? - I'm not even sure id this is a 'Tailmon' issue.
Anything to do with the "LD_LIBRARY_PATH" stuff going on?

 

[Viktor Jaep]

Hi there,

I run a script overnight (Not BACKUPMON - sorry!) which uses tar -zcf to compress/backup my full USB SSD to my NAS.
Since the "Big Entware update", it gives the following warning...
tar: ./entware/tmp/screens/S-AsusAdmin/8838.tailmon: socket ignored

Anything to worry about? - I'm not even sure id this is a 'Tailmon' issue.
Anything to do with the "LD_LIBRARY_PATH" stuff going on?

Should be a benign warning. The socket is a transitory file that only gets established when tailmon starts under screen. You can safely ignore.