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

[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.

 

[Nesalex]

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.

Sorry, but I can’t give a precise answer to your question. I installed Tailscale through the AMTM menu and used the recommended settings. I found the solution with AI:

Solution (works on my ASUS GT-AX6000 with Tailscale):​

1. Forward the router UI port from 192.168.1.1:65432 to 127.0.0.1:65432 using socat:
   
   socat TCP-LISTEN:65432,fork TCP:192.168.1.1:65432
   
   
   
2. Expose it via Tailscale Serve:
   
   tailscale serve --bg --http 80 http://127.0.0.1:65432

 

[rung]

Not sure why, but every once in a while after a tailscale upgrade, I will lose router access. Everything says it is running fine (tailmon and tailscale web page). I have found the following restores access:

1) ssh into router another way (e.g. local lan or backup Wireguard server)
2) Jump back into Tailmon: "tailmon -screen"
3) Exit Tailmon: "e"
4) kill tailscale process: "ps | grep tailscaled", "kill xxxx"
5) Restart Tailmon: "tailmon -screen"

Tailmon will restart tailscale and router access from the tailscale network is restored.

Maybe this technique will help others who are having trouble with their setup?

Rung

 

[Viktor Jaep]

Not sure why, but every once in a while after a tailscale upgrade, I will lose router access. Everything says it is running fine (tailmon and tailscale web page). I have found the following restores access:

1) ssh into router another way (e.g. local lan or backup Wireguard server)
2) Jump back into Tailmon: "tailmon -screen"
3) Exit Tailmon: "e"
4) kill tailscale process: "ps | grep tailscaled", "kill xxxx"
5) Restart Tailmon: "tailmon -screen"

Tailmon will restart tailscale and router access from the tailscale network is restored.

Maybe this technique will help others who are having trouble with their setup?

Rung

Does the "(R)estart" function not do the trick for you? Then again, I'm not seeing this issue either.

 

[rung]

Does the "(R)estart" function not do the trick for you? Then again, I'm not seeing this issue either.

It does not. I'm wondering if there is some caching going on? Killing everything and starting up again clears all the past?

 

[Viktor Jaep]

TAILMON v1.3.0 Beta 2 is out! This is a test of the new auto update method, for those on the beta track... let me know how it works out! You should be able to update via the update menu, or via autoupdate.

v1.3.0b2 - (TBA)
- PATCH: Fixed some of the logging messaging as it was still recommending an upgrade to a stable release even if you were enrolled in the beta track.

Download link (or let it autoupdate if you're enrolled in the Beta track!)

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

 

[Viktor Jaep]

It does not. I'm wondering if there is some caching going on? Killing everything and starting up again clears all the past?

Are you running under kernel or userspace mode? Sorry, have to ask.

 

[Stephen Harrington]

Hey @Viktor Jaep, very minor cosmetic issue but getting some weird screen formatting error in AMTM now since 1.3.0b1, or maybe it was an AMTM update?
The tailmon "tm" line has gone all screwy and is displaced WAY out to the right as far as it can go, which as usual really triggers my OCD
Not sure if this is a "you" fix or a @thelonelycoder fix? See screen shots:

Normal AMTM startup:

After doing a "u" Update:

Other than that, all good with the betas, thank you again for all your hard work!

 

[Viktor Jaep]

Hey @Viktor Jaep, very minor cosmetic issue but getting some weird screen formatting error in AMTM now since 1.3.0b1, or maybe it was an AMTM update?
The tailmon "tm" line has gone all screwy and is displaced WAY out to the right as far as it can go, which as usual really triggers my OCD
Not sure if this is a "you" fix or a @thelonelycoder fix? See screen shots:

Normal AMTM startup:

View attachment 67467

After doing a "u" Update:

View attachment 67468


Other than that, all good with the betas, thank you again for all your hard work!

Oh snap... I did some documentation and it looks like it's picking that stuff up within AMTM... here's the comparison between v1.2.0 and v1.3.0b2. I could remove the notes next to the version, and that would fix it. Will do on the next round. You can edit yourself, or you may need to suffer through a few days of OCD.

 

[Viktor Jaep]

Hey @Viktor Jaep, very minor cosmetic issue but getting some weird screen formatting error in AMTM now since 1.3.0b1, or maybe it was an AMTM update?
The tailmon "tm" line has gone all screwy and is displaced WAY out to the right as far as it can go, which as usual really triggers my OCD
Not sure if this is a "you" fix or a @thelonelycoder fix? See screen shots:

Actually... please go ahead and just redownload this latest version. My OCD can't wait either. I've omitted the documentation next to that variable. Should fix it.

 

[Stephen Harrington]

Actually... please go ahead and just redownload this latest version. My OCD can't wait either.

Phew! All good now, thanks @Viktor Jaep !!