amtm amtm v6.7.1 [2026-Apr-18] - the Asuswrt-Merlin Terminal Menu

[thelonelycoder]

Welcome, this is amtm 6.7.1, the Asuswrt-Merlin Terminal Menu

amtm is a front end that manages popular scripts for wireless routers running Asuswrt-Merlin firmware.
amtm is hosted on the Diversion website: https://diversion.ch/amtm.html

What's new in amtm

• Fixes endless loop prompting to update amtmupdate compatible scripts. Thanks to @maghuro for reporting.
• Adds script version numbers to amtmUpdate.log. Thanks to @scootertramp for the suggestion.

 

[visortgw]

@thelonelycoder: Can you please consider performing autoupdate when MD5 hash change is detected, but there is no version change for 3rd-party scripts (e.g., Skynet and RTRMON today)? Currently, updates must be initiated manually.

 

[thelonelycoder]

@thelonelycoder: Can you please consider performing autoupdate when MD5 hash change is detected, but there is no version change for 3rd-party scripts (e.g., Skynet and RTRMON today)? Currently, updates must be initiated manually.

MD5 hash changes can have multiple reasons, I am reluctant to allow auto-updates for these in amtm.

• I used to push updates for both amtm and Diversion with minor changes and NO version change. This happened for various and non-nefarious reasons.
  It got so bad that users complained that my update strategy is flawed - and they were right. So I changed it, see this post. I since follow strictly the most used versioning system, with the major.minor.patch numbering system for both amtm and Diversion.
• An MD5 hash change can also mean a compromised script file on your router or a hacked server file. This is not unheard of and the hash change might be an indicator for that. Another reason why I no longer push updates without a version change.
• And then there's the laziness of script writers - that used to include me! - to push an update and not inform users via a post or something. There may be more reasons, I am just to lazy to type more ...

Anyway, you may try to convince me otherwise.

 

[Mutzli]

@thelonelycoder: Can you please consider performing autoupdate when MD5 hash change is detected, but there is no version change for 3rd-party scripts (e.g., Skynet and RTRMON today)? Currently, updates must be initiated manually.

Skynet had a small update today:

fix IOT rule checks for proper param order by dave14305 · Pull Request #194 · Adamm00/IPSet_ASUS

Creates false integrity violations when iotports is populated. Actual output from 3006.102.7_2 iptables: -A FORWARD -i br+ -o eth0 -p tcp -m set --match-set Skynet-IOT src -m tcp -m multiport --dpo...

github.com

 

[visortgw]

MD5 hash changes can have multiple reasons, I am reluctant to allow auto-updates for these in amtm.

• I used to push updates for both amtm and Diversion with minor changes and NO version change. This happened for various and non-nefarious reasons.
  It got so bad that users complained that my update strategy is flawed - and they were right. So I changed it, see this post. I since follow strictly the most used versioning system, with the major.minor.patch numbering system for both amtm and Diversion.
• An MD5 hash change can also mean a compromised script file on your router or a hacked server file. This is not unheard of and the hash change might be an indicator for that. Another reason why I no longer push updates without a version change.
• And then there's the laziness of script writers - that used to include me! - to push an update and not inform users via a post or something. There may be more reasons, I am just to lazy to type more ...

Anyway, you may try to convince me otherwise.

Today's changes for both RTRMON and Skynet were both the third reason — yes, we need to discourage deployment of patches without version number change. Possibly a prompt to override when user knows it's a legit change?