amtm amtm 4.5.2 - the Asuswrt-Merlin Terminal Menu, May 02, 2024

[DeDragonSlayer]

On a different note, I noticed that amtm displays Access Point (AP) operation mode for my AiMesh and Media Bridge devices.
I dug a bit and found this thread, which seemed to suggest there's more than one nvram variable at play.
Then I checked the nvram values for my devices and I got:

Media Bridge (RT-AC68U, RT-N66U):
sw_mode=3
wlc_psta=1

AiMesh node (RT-AC86U):
sw_mode=3
wlc_psta=2

Main router (RT-AX88U):
sw_mode=1
wlc_psta=0

So i modified locally amtm code with the following snippet:

 OM='Operation Mode:'
                case "$(nvram get sw_mode)" in
                        1) echo " $OM Wireless router";;
                        2) echo " $OM Repeater";;
                        3) case "$(nvram get wlc_psta)" in
                                1) echo " $OM Media Bridge";;
                                2) echo " $OM AiMesh Node";;
                                *) echo " $OM Access Point (AP)";;
                                esac;;
                        4) echo " $OM Media Bridge";;
                        5) echo " $OM AiMesh Node";;
                        *) echo " $OM $(nvram get sw_mode), as-yet-unknown";;
                esac

and it seems to work, at least in my limited scenario. I have no idea if values 4 and 5 for sw_mode are still being used, so I just left them in there.
Hoping this post is useful, but obviously in the low-priority minor improvement suggestion category.

 

[thelonelycoder]

On a different note, I noticed that amtm displays Access Point (AP) operation mode for my AiMesh and Media Bridge devices.
I dug a bit and found this thread, which seemed to suggest there's more than one nvram variable at play.
Then I checked the nvram values for my devices and I got:

Media Bridge (RT-AC68U, RT-N66U):
sw_mode=3
wlc_psta=1

AiMesh node (RT-AC86U):
sw_mode=3
wlc_psta=2

Main router (RT-AX88U):
sw_mode=1
wlc_psta=0

So i modified locally amtm code with the following snippet:

 OM='Operation Mode:'
                case "$(nvram get sw_mode)" in
                        1) echo " $OM Wireless router";;
                        2) echo " $OM Repeater";;
                        3) case "$(nvram get wlc_psta)" in
                                1) echo " $OM Media Bridge";;
                                2) echo " $OM AiMesh Node";;
                                *) echo " $OM Access Point (AP)";;
                                esac;;
                        4) echo " $OM Media Bridge";;
                        5) echo " $OM AiMesh Node";;
                        *) echo " $OM $(nvram get sw_mode), as-yet-unknown";;
                esac

and it seems to work, at least in my limited scenario. I have no idea if values 4 and 5 for sw_mode are still being used, so I just left them in there.
Hoping this post is useful, but obviously in the low-priority minor improvement suggestion category.

Thanks, I‘ll check that on my routers and implement.

 

[thelonelycoder]

amtm 4.5.1 is now available

What's new in this patch release

• Corrected uiDivStats version number detection.
• Corrected Disk check options to actual number, thanks @jksmurf for reporting.
• Better detection of device operation mode in header, thanks to @DeDragonSlayer for reporting. Note that it is nearly impossible to know the exact mode because of the way it's determined.
• Because of the above, the NVRAM values for sw_mode and wlc_psta are shown in the a about screen.

 

[vibroverbus]

Seems to work good. I had some weird stuff w/ 4.5 happen like the uiDivStats didn't work then I did a amtm reset and then it seemed to work but then it didn't again and had some weird stuff w disk check too but upgrade seemed to work fine and all looks proper now in both regards (uiDivStats and disk check).

 

[Jaime Alvarez]

- amtm can now keep a history of entered shell commands with sh. This is the same feature that Diversion always provided by default but has now been moved to amtm. The move from Diversion to amtm is seamless if Diversion is updated before amtm, no user interaction is necessary.

I just had to reinstall everything on my venerable AC68U after my AX86U died. I wondered why it wasn't keeping my shell history, until I read this.

I just executed the sh command. I'll report back later.

Thank you @thelonelycoder !

 

[thelonelycoder]

I just had to reinstall everything on my venerable AC68U after my AX86U died. I wondered why it wasn't keeping my shell history, until I read this.

I just executed the sh command. I'll report back later.

Thank you @thelonelycoder !

On new installs the shell history is not enabled by default as it was in Diversion.

 

[thelonelycoder]

amtm 4.5.2 is now available

What's new in this patch release

• Accurate script version check comparison method, this slipped by in 4.5.1. Thanks to @vlord for reporting.
• File check and wording changes concerning updates.

 

[visortgw]

amtm 4.5.2 is now available

What's new in this patch release

• Accurate script version check comparison method, this slipped by in 4.5.1. Thanks to @vlord for reporting.
• File check and wording changes concerning updates.

Updated from Amsterdam.