RTRMON RTRMON v2.1.6 -Jul 5, 2025- Monitor your Router's Health (New: AMTM, Network Conn/Bandwidth/Diag + Port Scanner + Speedtest)

[Viktor Jaep]

Some minor but important updates to RTRMON heading your way... 2.1.6 released today!

NOTE: Upon running RTRMON, you may be presented with a screen that indicates your setup is incomplete, or that you're missing entware dependencies. The "column" entware tool is now a required component, so please hit the "Force Reinstall Entware Dependencies", and let everything reinstall to ensure all tools are in place to allow RTRMON to do it's thing!

What's new?
v2.1.6 - (July 5, 2025)
- PATCH: Included a much needed "export PATH" statement to ensure the script knows where to look for commonly installed entware tools. Not having this could cause confusion, as the script might use a similar older or newer tool installed in a different location on the router.
- PATCH: Included a check for the "column" entware tool. This tool is necessary for the display of data on page #7 (wireless/wired devices), and originally thought it was included with our FW by default. Apparently not the case, and will now get installed on a new RTRMON install, or will complain its missing and ask you to reinstall through the "Force Reinstall Entware Dependencies" menu item.
- PATCH: General bugfixes and UI cleanup items.

Download link (or update directly within RTRMON or AMTM):

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

Significant Screenshots:
None today!

 

[scootertramp]

This is not a result of RTRMON latest update but, I would like to see if this can be fixed.
iftop errors when running from RTRMON or running iftop from command line.

Error when running RTRMON:

Refresh (C)urrent Network Statistics

[Updating WAN( ) LAN( ) VPN( ) Statistics ... Please stand by...]Bus error
[Updating WAN(X) LAN( ) VPN( ) Statistics ... Please stand by...]Bus error
Refresh (C)urrent Statistics | Stats Age: 0 Minute(s) ago

From the messages file:

2025-07-05T19:30:41.545008-04:00 rt-ax92u kernel[-]: Unhandled fault: alignment fault (0x92000021) at 0x00000000f65000ae
2025-07-05T19:30:41.601287-04:00 rt-ax92u kernel[-]: potentially unexpected fatal signal 7.
2025-07-05T19:30:41.601287-04:00 rt-ax92u kernel[-]: CPU: 0 PID: 30113 Comm: iftop Tainted: P O 4.1.51 #2
2025-07-05T19:30:41.601287-04:00 rt-ax92u kernel[-]: Hardware name: Broadcom-v8A (DT)
2025-07-05T19:30:41.601287-04:00 rt-ax92u kernel[-]: task: ffffffc004de4ac0 ti: ffffffc008dfc000 task.ti: ffffffc008dfc000
2025-07-05T19:30:41.601287-04:00 rt-ax92u kernel[-]: PC is at 0x133e4
2025-07-05T19:30:41.601287-04:00 rt-ax92u kernel[-]: LR is at 0x132dc
2025-07-05T19:30:41.601287-04:00 rt-ax92u kernel[-]: pc : [<00000000000133e4>] lr : [<00000000000132dc>] pstate: 600c0010
2025-07-05T19:30:41.601287-04:00 rt-ax92u kernel[-]: sp : 00000000f64fe8e8
2025-07-05T19:30:41.601287-04:00 rt-ax92u kernel[-]: x12: 0000000000000000
2025-07-05T19:30:41.602670-04:00 rt-ax92u kernel[-]: x11: 0000000000000000 x10: 0000000000013cf0
2025-07-05T19:30:41.602670-04:00 rt-ax92u kernel[-]: x9 : 0000000000000064 x8 : 0000000000000100
2025-07-05T19:30:41.602670-04:00 rt-ax92u kernel[-]: x7 : 0000000000000001 x6 : 0000000000000000
2025-07-05T19:30:41.602670-04:00 rt-ax92u kernel[-]: x5 : 00000000f64fe924 x4 : 00000000f65000a2
2025-07-05T19:30:41.602670-04:00 rt-ax92u kernel[-]: x3 : 000000000000d37c x2 : 00000000000001bb
2025-07-05T19:30:41.602670-04:00 rt-ax92u kernel[-]: x1 : 0000000000000000 x0 : 00000000f64fe924

The above error from the messages file is the same when running iftop from command line.

Kernel: RT-AX92U (aarch64) Kernel-4.1.51
Firmware: 3004.388.9_2-gnuton1
AMTM: 6.1
RTRMON: 2.1.6

I did try running "Force Reinstall Entware Dependencies" but, it did not help.

 

[Viktor Jaep]

This is not a result of RTRMON latest update but, I would like to see if this can be fixed.
iftop errors when running from RTRMON or running iftop from command line.

Error when running RTRMON:

Refresh (C)urrent Network Statistics

[Updating WAN( ) LAN( ) VPN( ) Statistics ... Please stand by...]Bus error
[Updating WAN(X) LAN( ) VPN( ) Statistics ... Please stand by...]Bus error
Refresh (C)urrent Statistics | Stats Age: 0 Minute(s) ago

From the messages file:

2025-07-05T19:30:41.545008-04:00 rt-ax92u kernel[-]: Unhandled fault: alignment fault (0x92000021) at 0x00000000f65000ae
2025-07-05T19:30:41.601287-04:00 rt-ax92u kernel[-]: potentially unexpected fatal signal 7.
2025-07-05T19:30:41.601287-04:00 rt-ax92u kernel[-]: CPU: 0 PID: 30113 Comm: iftop Tainted: P O 4.1.51 #2
2025-07-05T19:30:41.601287-04:00 rt-ax92u kernel[-]: Hardware name: Broadcom-v8A (DT)
2025-07-05T19:30:41.601287-04:00 rt-ax92u kernel[-]: task: ffffffc004de4ac0 ti: ffffffc008dfc000 task.ti: ffffffc008dfc000
2025-07-05T19:30:41.601287-04:00 rt-ax92u kernel[-]: PC is at 0x133e4
2025-07-05T19:30:41.601287-04:00 rt-ax92u kernel[-]: LR is at 0x132dc
2025-07-05T19:30:41.601287-04:00 rt-ax92u kernel[-]: pc : [<00000000000133e4>] lr : [<00000000000132dc>] pstate: 600c0010
2025-07-05T19:30:41.601287-04:00 rt-ax92u kernel[-]: sp : 00000000f64fe8e8
2025-07-05T19:30:41.601287-04:00 rt-ax92u kernel[-]: x12: 0000000000000000
2025-07-05T19:30:41.602670-04:00 rt-ax92u kernel[-]: x11: 0000000000000000 x10: 0000000000013cf0
2025-07-05T19:30:41.602670-04:00 rt-ax92u kernel[-]: x9 : 0000000000000064 x8 : 0000000000000100
2025-07-05T19:30:41.602670-04:00 rt-ax92u kernel[-]: x7 : 0000000000000001 x6 : 0000000000000000
2025-07-05T19:30:41.602670-04:00 rt-ax92u kernel[-]: x5 : 00000000f64fe924 x4 : 00000000f65000a2
2025-07-05T19:30:41.602670-04:00 rt-ax92u kernel[-]: x3 : 000000000000d37c x2 : 00000000000001bb
2025-07-05T19:30:41.602670-04:00 rt-ax92u kernel[-]: x1 : 0000000000000000 x0 : 00000000f64fe924

The above error from the messages file is the same when running iftop from command line.

Kernel: RT-AX92U (aarch64) Kernel-4.1.51
Firmware: 3004.388.9_2-gnuton1
AMTM: 6.1
RTRMON: 2.1.6

I did try running "Force Reinstall Entware Dependencies" but, it did not help.

I'm sorry @scootertramp ... Hate to tell you this... but when you start seeing "<name of binary> Tainted", that's usually bad news. I've not ever been to able to recover from something like this without a full USB wipe (possibly a bad USB) and/or a full router wipe and reset. Something in the OS has gone bad, and the only way out is a full reinstall.

Would welcome any other assistance or opinions from the community if you've had luck recovering from something like this without a full wipe + reinstall?

 

[scootertramp]

I'm sorry @scootertramp ... Hate to tell you this... but when you start seeing "<name of binary> Tainted", that's usually bad news. I've not ever been to able to recover from something like this without a full USB wipe (possibly a bad USB) and/or a full router wipe and reset. Something in the OS has gone bad, and the only way out is a full reinstall.

Would welcome any other assistance or opinions from the community if you've had luck recovering from something like this without a full wipe + reinstall?

Thanks. but I think that's a rabbit hole I would rather avoid. Everything else I am using on this router appears to be working well.
I tried RTRMON on one of my XT8 routers to see how it fairs there as well. I am seeing the following errors when running RTRMON.

cat: can't open '/sys/class/net//statistics/rx_bytes': No such file or directory
cat: can't open '/sys/class/net//statistics/tx_bytes': No such file or directory

On the XT8 iftop seems to be running better, but I get a few odd messages there as well.
When quitting iftop:
XXXXXXX@zenwifi-xt8up:/tmp/home/root# iftop
interface: archer
Unable to get IP address for interface: archer
ioctl(SIOCGIFADDR): Cannot assign requested address
MAC address is: 00:00:00:00:00:00

and in the messages file:
2025-07-06T08:11:54.928670-04:00 zenwifi-xt8up kernel[-]: protocol 0000 is buggy, dev archer
2025-07-06T08:11:55.480667-04:00 zenwifi-xt8up kernel[-]: protocol 0000 is buggy, dev archer

XT8 Info:
ZenWiFi_XT8 (armv7l) Kernel-4.1.52
Firmware: 3004.388.9_2-gnuton1
AMTM: 6.1
RTRMON: 2.1.6

 

[Viktor Jaep]

Thanks. but I think that's a rabbit hole I would rather avoid. Everything else I am using on this router appears to be working well.
I tried RTRMON on one of my XT8 routers to see how it fairs there as well. I am seeing the following errors when running RTRMON.

I'm just saying, from my experience. When this happened to me, it started out with one tool, but then it quickly started multiplying to the point where I was unable to use some commonly-used tools making for a frustrating experience. Whatever is going bad on your router, isn't going to stop until you take some action.

cat: can't open '/sys/class/net//statistics/rx_bytes': No such file or directory
cat: can't open '/sys/class/net//statistics/tx_bytes': No such file or directory

This is pretty rare, but for some reason RTRMON can't determine what your WAN0 interface name is (usually eth0). Luckily, you can override this to the correct value under the settings menu. Try picking the right one from this list, and should make a difference for you.

On the XT8 iftop seems to be running better, but I get a few odd messages there as well.
When quitting iftop:
XXXXXXX@zenwifi-xt8up:/tmp/home/root# iftop
interface: archer
Unable to get IP address for interface: archer
ioctl(SIOCGIFADDR): Cannot assign requested address
MAC address is: 00:00:00:00:00:00

and in the messages file:
2025-07-06T08:11:54.928670-04:00 zenwifi-xt8up kernel[-]: protocol 0000 is buggy, dev archer
2025-07-06T08:11:55.480667-04:00 zenwifi-xt8up kernel[-]: protocol 0000 is buggy, dev archer

This may have something to do with your strange eth0 interface issue. Doesn't seem like iftop likes it either. Seems like it tried to pick one called "archer", but there wasn't an IP address assigned to it, so it wasn't able to gather any data. Once you figure out the correct interface name for WAN0, you can use that in the iftop commandline as well, and force it to use that.

I haven't had many report back from the XT8 side, running on gnuton, but we could very well be dealing with a compatibility issue here.

 

[scootertramp]

I'm just saying, from my experience. When this happened to me, it started out with one tool, but then it quickly started multiplying to the point where I was unable to use some commonly-used tools making for a frustrating experience. Whatever is going bad on your router, isn't going to stop until you take some action.


This is pretty rare, but for some reason RTRMON can't determine what your WAN0 interface name is (usually eth0). Luckily, you can override this to the correct value under the settings menu. Try picking the right one from this list, and should make a difference for you.

View attachment 66529



This may have something to do with your strange eth0 interface issue. Doesn't seem like iftop likes it either. Seems like it tried to pick one called "archer", but there wasn't an IP address assigned to it, so it wasn't able to gather any data. Once you figure out the correct interface name for WAN0, you can use that in the iftop commandline as well, and force it to use that.

I haven't had many report back from the XT8 side, running on gnuton, but we could very well be dealing with a compatibility issue here.

@Viktor Jaep

Assigning an interface works fine for both RTRMON and iftop on the XT8. I used br0 since that is using the routers ip address.

For now I will skip the rabbit hole on the AX92U and take the blue pill. I am not sure how long the AX92U will be a viable router
as it has been on the EOL list for quite some time. Back last November I started to look for a replacement because of EOL and
had not had any firmware updates for about a year. To my surprise ASUS was still pushing them on their site and there was a new firmware
update. Since then there have been like two more firmware updates.

Thanks for your input and I will see where things stand when the blue pill wears off.

 

[Viktor Jaep]

Assigning an interface works fine for both RTRMON and iftop on the XT8. I used br0 since that is using the routers ip address.

Glad that worked for ya.

For now I will skip the rabbit hole on the AX92U and take the blue pill. I am not sure how long the AX92U will be a viable router
as it has been on the EOL list for quite some time. Back last November I started to look for a replacement because of EOL and
had not had any firmware updates for about a year. To my surprise ASUS was still pushing them on their site and there was a new firmware
update. Since then there have been like two more firmware updates.

Thanks for your input and I will see where things stand when the blue pill wears off.

Absolutely... let me know how it goes! Hopefully some upcoming sales will be enticing enough to pull that trigger on a new router in the near future.