What's new

RTRMON RTRMON v2.2.3 -Nov 16, 2025- Monitor your Router's Health (New: Wireguard, AMTM, Network Conn/Bandwidth/Diag + Port Scanner + Speedtest) - v2.3.0Beta7

Nice work on coming up with a solution, @jksmurf! I may have already asked, but what happens if you run RTRMON on the nodes? Does it give you this info as well, or does it revert to displaying these clients as LAN clients?
Yet to be tested! Maybe next year … 😆
 
Fixed a flaw in the way RTRMON captures Wi-Fi stats that became apparent after moving to the GT-BE98Pro. This should now display your stats correctly and should be backwards compatible with other router models and firmware versions. This was the last item on my list to fix before a formal release... please give it one last test! Enjoy!

RTRMON v2.3.0b7
What's new?
- PATCH:
Fixed the Wi-Fi stats page, as it was using an older method of collecting interface stats. With the newer routers implementing per-SSID/VLAN accounting at the driver level, the parent interface (ex: wl0) no longer accumulates statistics directly. This new method of capturing this info should be backwards compatiable with other routers and older firmware. TBD! ;)

Download link:
Code:
curl --retry 3 "https://raw.githubusercontent.com/ViktorJp/RTRMON/develop/rtrmon.sh" -o "/jffs/scripts/rtrmon.sh" && chmod 755 "/jffs/scripts/rtrmon.sh"

Significant Screenshots:

Showing that we're getting stats again! Whoo!

1767839135546.png
 
Fixed a flaw in the way RTRMON captures Wi-Fi stats that became apparent after moving to the GT-BE98Pro. This should now display your stats correctly and should be backwards compatible with other router models and firmware versions. This was the last item on my list to fix before a formal release... please give it one last test! Enjoy!

RTRMON v2.3.0b7
What's new?
- PATCH:
Fixed the Wi-Fi stats page, as it was using an older method of collecting interface stats. With the newer routers implementing per-SSID/VLAN accounting at the driver level, the parent interface (ex: wl0) no longer accumulates statistics directly. This new method of capturing this info should be backwards compatiable with other routers and older firmware. TBD! ;)

Download link:
Code:
curl --retry 3 "https://raw.githubusercontent.com/ViktorJp/RTRMON/develop/rtrmon.sh" -o "/jffs/scripts/rtrmon.sh" && chmod 755 "/jffs/scripts/rtrmon.sh"

Significant Screenshots:

Showing that we're getting stats again! Whoo!

View attachment 69818
Works for me on GT-BE98 Pro primary router and GT-AX6000 AiMesh node. Thanks!
 
@Viktor Jaep: I must say that the reworked wifi client page (aka page 7) is FAST compared to the previous version, even on my large, complex network — roughly 10 seconds from start to finish to refresh about 80 clients!
 
@Viktor Jaep: I must say that the reworked wifi client page (aka page 7) is FAST compared to the previous version, even on my large, complex network — roughly 10 seconds from start to finish to refresh about 80 clients!
That's great to hear, @visortgw! I've got some plans to firm it up even more. That'll be for the next release! ;)
 
Works for me on GT-BE98 Pro primary router and GT-AX6000 AiMesh node. Thanks!
Sorry I believe we touched on this briefly above, but can you remind me, to see the client details (RSSI e.g.) for clients on AiMesh nodes, do you need to have Merlin installed on the Nodes and enable this option on the main “Mark Router As iMesh Node/Repeater/Bridge?” (Not sure why it’s iMesh not AiMesh).
 
Sorry I believe we touched on this briefly above, but can you remind me, to see the client details (RSSI e.g.) for clients on AiMesh nodes, do you need to have Merlin installed on the Nodes and enable this option on the main “Mark Router As iMesh Node/Repeater/Bridge?” (Not sure why it’s iMesh not AiMesh).
Correct. I think they may have rebranded from iMesh to AiMesh... Then again, it could be a typo! Lol
 
Last edited:
Correct. I think their may have rebranded from iMesh to AiMesh... Then again, it could be a typo! Lol
Ok thanks. Will have to set up the node tomorrow, need a usb stick or ssd to install entware on it I think, as used by RTRMON.

Is it possible / could I request that you allow folks to exclude certain screens so you don’t have to scroll through a bunch of them? atm I’m just interested in screen 7, per client RSSI stats (and you saw above how I’m doing that at the moment, with scripts).

As there are screens I will never use, could these be excluded using an exclude list eg exclude 2,3,4,5 or an include one 1,6,7? Saves scrolling or cycling through screens that are of lesser interest.
 
Last edited:
Ok thanks. Will have to set up the node tomorrow, need a usb stick or ssd to install entware on it I think, as used by RTRMON.

Is it possible / could I request that you allow folks to exclude certain screens so you don’t have to scroll through a bunch of them? atm I’m just interested in screen 7, per client RSSI stats (and you saw above how I’m doing that at the moment

As there are screens I will never use, could these be excluded using an exclude list eg exclude 2,3,4,5 or an include one 1,6,7? Saves scrolling or cycling through screens that are of lesser interest.
For now, simply type p (aka previous) once screen 1 appears after initialization to rotate back to screen 7.
 
For now, simply type p (aka previous) once screen 1 appears after initialization to rotate back to screen 7.
Alternately just start RTRMON telling it to jump to screen 7.

Code:
agagne@xt8-up:/tmp/home/root# rtrmon -monitor 7
 
Alternately just start RTRMON telling it to jump to screen 7.

Code:
agagne@xt8-up:/tmp/home/root# rtrmon -monitor 7
Thanks for the tip. You learn something new every day!
 
Alternately just start RTRMON telling it to jump to screen 7.

Code:
agagne@xt8-up:/tmp/home/root# rtrmon -monitor 7
Very nice, thank you. It does seem to stay on screen 7 only, which is exactly what I was after. I’m not sure it uses the “screen” function when started like that, will need to check.

It seems to update (the counter) and roll over faster than I’d like it to (faster than my feeble brain can digest the information or copy it), is it possible to briefly freeze (f) the update so I can have enough time to read it / copy it please?
 
Very nice, thank you. It does seem to stay on screen 7 only, which is exactly what I was after. I’m not sure it uses the “screen” function when started like that, will need to check.

It seems to update (the counter) and roll over faster than I’d like it to (faster than my feeble brain can digest the information or copy it), is it possible to briefly freeze (f) the update so I can have enough time to read it / copy it please?
You can change the counter from 10sec to whatever you like under the settings.
 
Very nice, thank you. It does seem to stay on screen 7 only, which is exactly what I was after. I’m not sure it uses the “screen” function when started like that, will need to check.

It seems to update (the counter) and roll over faster than I’d like it to (faster than my feeble brain can digest the information or copy it), is it possible to briefly freeze (f) the update so I can have enough time to read it / copy it please?
Yes you can start RTRMON using screen with the option to jump to a particular screen (Example 7).

Check out RTRMON help.
Code:
agagne@rt-be88u:/tmp/home/root# rtrmon -h

RTRMON v2.3.0b7 Commandline Option Usage:

rtrmon.sh -h | -help
rtrmon.sh -log
rtrmon.sh -config
rtrmon.sh -update
rtrmon.sh -setup
rtrmon.sh -uninstall
rtrmon.sh -screen
rtrmon.sh -monitor
rtrmon.sh -screen/-monitor X
rtrmon.sh -screen (X) -now

 -h | -help (this output)
 -log (display the current log contents)
 -config (configuration utility)
 -update (script update utility)
 -setup (setup/dependencies utility)
 -uninstall (uninstall utility)
 -screen (normal router monitoring using the screen utility)
 -monitor (normal router monitoring operations)
 -screen/-monitor X (X = display screen 1-6 upon execution)
 -screen -now (bypass screen instructions and 5 sec timer)

 Examples:
 rtrmon -screen -now (bypass screen timer directly into monitor mode)
 rtrmon -screen 2 (jump to page 2 upon execution using screen)
 rtrmon -screen 3 -now (bypass timer and jump to page 3 using screen)
 rtrmon -monitor 4 (jump to page 4 in monitoring mode)
 
Yes you can start RTRMON using screen with the option to jump to a particular screen (Example 7).

Check out RTRMON help.
Code:
agagne@rt-be88u:/tmp/home/root# rtrmon -h

RTRMON v2.3.0b7 Commandline Option Usage:

rtrmon.sh -h | -help
rtrmon.sh -log
rtrmon.sh -config
rtrmon.sh -update
rtrmon.sh -setup
rtrmon.sh -uninstall
rtrmon.sh -screen
rtrmon.sh -monitor
rtrmon.sh -screen/-monitor X
rtrmon.sh -screen (X) -now

 -h | -help (this output)
 -log (display the current log contents)
 -config (configuration utility)
 -update (script update utility)
 -setup (setup/dependencies utility)
 -uninstall (uninstall utility)
 -screen (normal router monitoring using the screen utility)
 -monitor (normal router monitoring operations)
 -screen/-monitor X (X = display screen 1-6 upon execution)
 -screen -now (bypass screen instructions and 5 sec timer)

 Examples:
 rtrmon -screen -now (bypass screen timer directly into monitor mode)
 rtrmon -screen 2 (jump to page 2 upon execution using screen)
 rtrmon -screen 3 -now (bypass timer and jump to page 3 using screen)
 rtrmon -monitor 4 (jump to page 4 in monitoring mode)
Sorry bad information. IT apperas to not work with screen for page 7.
Pages less than 7 look to be ok.
@Viktor Jaep
 
Yes you can start RTRMON using screen with the option to jump to a particular screen (Example 7).

Check out RTRMON help.
Code:
agagne@rt-be88u:/tmp/home/root# rtrmon -h

RTRMON v2.3.0b7 Commandline Option Usage:

rtrmon.sh -screen/-monitor X

 -h | -help (this output)
 -log (display the current log contents)
 
 -screen/-monitor X (X = display screen 1-6 upon execution)
IMG_2917.jpeg
IMG_2918.jpeg
IMG_2919.jpeg
IMG_2920.jpeg
IMG_2921.jpeg


Ok noting that I put the command that didn’t work below to demonstrate what I ran, and trying with and without .sh and using just 6 per example in case 7 didn’t work, I’m not sure what I am doing wrong here?
 
View attachment 69841View attachment 69842View attachment 69843View attachment 69844View attachment 69845

Ok noting that I put the command that didn’t work below to demonstrate what I ran, and trying with and without .sh and using just 6 per example in case 7 didn’t work, I’m not sure what I am doing wrong here?
You do not need to use .sh.

Code:
agagne@rt-be88u:/tmp/home/root#  rtrmon -screen 6
or
agagne@rt-be88u:/tmp/home/root#  rtrmon -monitor 6

There should be an alias that gets created for you I believe as part of the install.
Code:
agagne@rt-be88u:/tmp/home/root# alias
rtrmon='sh /jffs/scripts/rtrmon.sh'
 
Last edited:
You do not need to use .sh.

Code:
agagne@rt-be88u:/tmp/home/root#  rtrmon -screen 6
or
agagne@rt-be88u:/tmp/home/root#  rtrmon -monitor 6
Yes, without .sh worked for monitor which I ran before, but as -screen/-monitor X did not work I just gave it a whirl to rule it out, ta.
 
Last edited:

Similar threads

Latest threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Back
Top