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

[Viktor Jaep]

As hinted at before w/ @swejuggalo, I have totally revamped the whole update and autoupdate process. Once you subscribe to a particular track, TAILMON will only recommend updates for that track. Enjoy!

What's new!?
v1.3.0b1 - (TBA)
- MINOR: Revamped the entire check updates/autoupdates process. Going into the "Check for Updates" section in the main setup / configuration menu, you now have the option to subscribe to either the BETA or STABLE (default) track. Once you are enrolled in either of these 2 tracks, TAILMON will only recommend updates and autoupdates for this specific track.
- PATCH: Fixed some minor UI changes

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"

Significant Screenshots:

Showing the option to see / pick between the Stable and Beta tracks in the Update Utility:

 

[Viktor Jaep]

Hello,
I have a problem accessing the UI of my GT-AX6000 router. The router is running the latest Merlin firmware and all add-ons are up to date. I use Tailscale to access the UI of my RT-AC68U router, where I can easily connect by entering the Tail IP address in the browser, but I have trouble accessing the GT-AX6000. I have 192.168.1.0/24 allowed. I read that the firewall might be causing the issue, so I entered:

iptables -I INPUT -i tailscale0 -p tcp --dport 65432 -j ACCEPT


So far, no success. On my home network, I log in to the UI via 192.168.1.1:65432

If I create a VPN server on the router, I can connect via OpenVPN and access the UI without any problems. I have a public IP address.

Do you have any suggestions on what I could try?

Are you running under Kernel or Userspace mode? I have always found to have more issues under Kernel mode, like getting to the UI of my router. I think I was able to find a workaround by actually going out of my way and using the tailscale serve command... like so:

tailscale serve --http=<port> <target> [off]

But again, I have no issues getting to the UI under Userspace mode, and get to it both from remote with a "192.168.50.1" or the Tailscale IP.

 

[swejuggalo]

As hinted at before w/ @swejuggalo, I have totally revamped the whole update and autoupdate process. Once you subscribe to a particular track, TAILMON will only recommend updates for that track. Enjoy!

What's new!?
v1.3.0b1 - (TBA)
- MINOR: Revamped the entire check updates/autoupdates process. Going into the "Check for Updates" section in the main setup / configuration menu, you now have the option to subscribe to either the BETA or STABLE (default) track. Once you are enrolled in either of these 2 tracks, TAILMON will only recommend updates and autoupdates for this specific track.
- PATCH: Fixed some minor UI changes

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"

Significant Screenshots:

Showing the option to see / pick between the Stable and Beta tracks in the Update Utility:

View attachment 67401

Awesome! Already installed on my main router.
What would happen in the scenario of beta ending? Back to stable and automatically going back to beta when available?

 

[Viktor Jaep]

Awesome! Already installed on my main router.
What would happen in the scenario of beta ending? Back to stable and automatically going back to beta when available?

Great question... So when the beta ends, the beta track will contain the stable version so it can replicate to the main branch on github. But TAILMON will remain on that beta track, so when a new beta gets added to the develop branch, it will then automatically update to that latest beta.

 

[swejuggalo]

Great question... So when the beta ends, the beta track will contain the stable version so it can replicate to the main branch on github. But TAILMON will remain on that beta track, so when a new beta gets added to the develop branch, it will then automatically update to that latest beta.

Great! So when a possible patch comes on stable path it would not be a problem to stay on beta path since it's a build number check rather than build date? Think that is the only problem I can think on. If stable would get newer, but still lower version than beta.

 

[Viktor Jaep]

Great! So when a possible patch comes on stable path it would not be a problem to stay on beta path since it's a build number check rather than build date? Think that is the only problem I can think on. If stable would get newer, but still lower version than beta.

Even if a patch comes out, it would hit develop/beta first, so you're safe.

 

[swejuggalo]

Even if a patch comes out, it would hit develop/beta first, so you're safe.

Seems like you covered the possible scenarios then
Lets see if a glitch pops up.

 

[jksmurf]

I have always found to have more issues under Kernel mode

FWIW, I’ve never had any issues with Custom mode, which basically uses the Kernel mode.

 

[Viktor Jaep]

FWIW, I’ve never had any issues with Custom mode, which basically uses the Kernel mode.

Yeah, I really don't understand why I have to jump through hoops with Kernel mode on my end. Just glad Userspace mode works for my purposes.