RTRMON RTRMON v2.1.3 -Oct 19, 2024- Monitor your Router's Health (New: AMTM, Network Conn/Bandwidth/Diag + Port Scanner + Speedtest)

[dave14305]

I am seeing sw_mode=3, not 5, for all four (4) of my AiMesh nodes — GT-AXE16000, GT-AX6000, and RT-AX86U (x2). My primary router (GT-AX6000) shows sw_mode=1.

Good to know. I’ve never used AiMesh, so was making assumptions based on the code. I wonder what constitutes an AiMesh node (5) versus an AiMesh AP (3)?

 

[Viktor Jaep]

@Viktor Jaep: That appears to take care of the missing WAN interface errors on AiMesh nodes. I do see some failures within the diagnostic results:

  Network Resolution Test...   [Failed]   | nslookup google.com 127.0.0.1
  Dig Functionality Test...    [Failed]   | dig google.com

Dig might fail if you haven't installed the dig binary from Entware... opkg install bind-dig

But the nslookup failing is kinda weird... but maybe an iMesh node forwards its dns requests to the main router? Also interesting!

 

[visortgw]

Dig might fail if you haven't installed the dig binary from Entware... opkg install bind-dig

But the nslookup failing is kinda weird... but maybe an iMesh node forwards its dns requests to the main router? Also interesting!

Installation of dig fails:

# opkg install dig
Unknown package 'dig'.
Collected errors:
 * opkg_install_cmd: Cannot install package dig.

It certainly makes sense that AiMesh nodes forward DNS requests to the main router.

UPDATE: opkg install bind-dig works, and it resolves that error.

 

[Viktor Jaep]

Installation of dig fails:

# opkg install dig
Unknown package 'dig'.
Collected errors:
 * opkg_install_cmd: Cannot install package dig.

It certainly makes sense that AiMesh nodes forward DNS requests to the main router.

try opkg install bind-dig

 

[Viktor Jaep]

Installation of dig fails:

# opkg install dig
Unknown package 'dig'.
Collected errors:
 * opkg_install_cmd: Cannot install package dig.

It certainly makes sense that AiMesh nodes forward DNS requests to the main router.

UPDATE: opkg install bind-dig works, and it resolves that error.

So that leaves DNS resolution... since nslookup google.com 127.0.0.1 doesn't work, that IP would need to change to the primary router that the iMesh nodes connect to... there's gotta be an NVRAM value for that! LOL

 

[visortgw]

So that leaves DNS resolution... since nslookup google.com 127.0.0.1 doesn't work, that IP would need to change to the primary router that the iMesh nodes connect to... there's gotta be an NVRAM value for that! LOL

I believe that it is NVRAM value lan_gateway that you are looking for (which resolves to IP of primary router)...

 

[visortgw]

So that leaves DNS resolution... since nslookup google.com 127.0.0.1 doesn't work, that IP would need to change to the primary router that the iMesh nodes connect to... there's gotta be an NVRAM value for that! LOL

Or, why specify IP at all? Simply use nslookup google.com?

 

[Viktor Jaep]

Or, why specify IP at all? Simply use nslookup google.com?

Very true!! That sounds like a fix!

 

[Viktor Jaep]

Hey @visortgw ... could you please send me a screenshot off your AXE16000 to make sure that the wifi page looks like it's populating OK? Wanted to make sure that the 2.4GHz, the 2 x 5GHz and the 6GHz visualizations come up right?

 

[visortgw]

try opkg install bind-dig

Should you install dig if it isn't already?

 

[Viktor Jaep]

Should you install dig if it isn't already?

I leave it as optional since a lot of times, it gets installed when other tools are installed. It's just one of those old tools that nobody ever uses anymore... so I don't want to force it on people.

 

[visortgw]

Hey @visortgw ... could you please send me a screenshot off your AXE16000 to make sure that the wifi page looks like it's populating OK? Wanted to make sure that the 2.4GHz, the 2 x 5GHz and the 6GHz visualizations come up right?

View attachment 58990

 

[Viktor Jaep]

THANK YOU!!!

This is why this is so helpful when you don't have a device like this to test against... My OCD thanks you. You ROCK!

 

[Viktor Jaep]

@visortgw ... if you see anything else out of alignment... the wifi page should really be the only one since the AXE16000 is so unique, but just let me know.

I just updated the script, so you can download/overwrite... and this wifi page should look aligned now.

 

[visortgw]

THANK YOU!!!

This is why this is so helpful when you don't have a device like this to test against... My OCD thanks you. You ROCK!

View attachment 58992

@Viktor Jaep: I was wondering how much that would bother you (I noticed the same, but I didn't dare mention it)!

 

[Viktor Jaep]

@Viktor Jaep: I was wondering how much that would bother you (I noticed the same, but I didn't dare mention it)!

It bothers me more than you can imagine... alignment OCD is my downfall.

 

[visortgw]

@visortgw ... if you see anything else out of alignment... the wifi page should really be the only one since the AXE16000 is so unique, but just let me know.

I just updated the script, so you can download/overwrite... and this wifi page should look aligned now.

Fixed! Now, just the nslookup issue on Diagnostics page remains.

 

[Viktor Jaep]

Fixed! Now, just the nslookup issue on Diagnostics page remains.

I'm going to address this first thing in the AM... I have some other items on my list left to finish as well. Plus, I have a couple of beers to down!

 

[visortgw]

I'm going to address this first thing in the AM... I have some other items on my list left to finish as well. Plus, I have a couple of beers to down!

So, I'm a bit ahead of you, having already finished a bottle of wine with my sister.

 

[Viktor Jaep]

Beta 2 is out, addressing these issues below. @visortgw ... would be curious if the nslookup network diag now works on your node(s)!

And if anyone has a RT-BE96U or a GT-BE98_PRO, please let me know if everything is working, especially determining if things look good on the WiFi page since this BE98 Pro is the first router with 2 x 6GHz ranges to display.

What's new? (Including everything from Beta 1)
v2.0.12b2 - (TBA)
- PATCH: After getting some nvram feedback from @visortgw and @dave14305, I've made more modifications on how to determine if a router is truly a router, not an AP/Repeater/iMesh Node.
- PATCH: Through testing with @visortgw, it was determined that the nslookup diag command does not work on iMesh nodes, and made a small modification to it so that it may hopefully pass this test.
- PATCH: Now includes compatibility for the newly announced supported Merlin FW routers: the GT-BE98_PRO and the RT-BE96U. The BE98_PRO is the first router that makes use of 2 x 6GHz ranges.
- PATCH: Logging standards have been updated across the script, and open to suggestions for other log events that might be reported on.

BETA 2 Download link:

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