amtm amtm 3.1.9 - the Asuswrt-Merlin Terminal Menu

[thelonelycoder]

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

amtm is a front end that manages popular scripts for wireless routers running Asuswrt-Merlin firmware. Starting with Asuswrt-Merlin 384.15, amtm is included in the firmware.

What's new in amtm 3.1.9
NEW: Adds support for Vnstat by @dev_null - Vnstat on Merlin - UI, CLI and email - data use monitoring - with full install and menu.
See https://www.snbforums.com/threads/b...-monitoring-with-full-install-and-menu.70727/
NEW: Adds support for YazDHCP by @Jack Yaz - YazDHCP - feature expansion of DHCP assignments (increasing limit on the number of DHCP reservations)
See https://www.snbforums.com/threads/y...mit-on-the-number-of-dhcp-reservations.69247/
CHANGED: pixelserv-tls helper script to use CA for https WebUI (ps) now supports newly added routers to the Asuswrt-Merlin realm.
CHANGED: Firmware update check when running u now supports newly added Asuswrt-Merlin routers.
CHANGED: Entware installer gives option to use an existing but non-active Entware installation when found on a attached USB device.

How to update amtm
In the amtm menu, enter u to update to this latest version.
The firmware built-in and the regular amtm version receive updates at the same time.

amtm start command

amtm

On firmware older than 384.15, you may have to enter the full path to amtm.
Note that the command below does not work for the firmware built in amtm.

/jffs/scripts/amtm

Install command for Asuswrt-Merlin firmware older than 384.15
Copy and paste the complete command below into your favorite SSH terminal, then press Enter.

curl -Os https://diversion.ch/amtm/amtm && sh amtm

Routers with Asuswrt-Merlin firmware 384.15 and newer require no installation, amtm is included in the firmware. The firmware built in amtm adds FW next to the version.

amtm is hosted on the Diversion website: https://diversion.ch/amtm.html

amtm License
amtm is free to use under the GNU General Public License, version 3 (GPL-3.0).

 

[ColDen]

Welcome, this is amtm v3.1.9, the Asuswrt-Merlin Terminal Menu

amtm is a front end that manages popular scripts for wireless routers running Asuswrt-Merlin firmware. Starting with Asuswrt-Merlin 384.15, amtm is included in the firmware.

How to update amtm
In the amtm menu, enter u to update to this latest version.
The firmware built-in and the regular amtm version receive updates at the same time.

Install command for Asuswrt-Merlin firmware older than 384.15
Copy and paste the complete command below into your favorite SSH terminal, then press Enter.

curl -Os https://diversion.ch/amtm/amtm && sh amtm

Routers with Asuswrt-Merlin firmware 384.15 and newer require no installation, amtm is included in the firmware. The firmware built in amtm adds FW next to the version.

amtm start command

amtm

On firmware older than 384.15, you may have to enter the full path to amtm.
Note that the command below does not work for the firmware built in amtm.

/jffs/scripts/amtm

amtm is hosted on the Diversion website: https://diversion.ch/amtm.html

amtm License
amtm is free to use under the GNU General Public License, version 3 (GPL-3.0).

What's new in amtm 3.1.9
NEW: Adds support for Vnstat by @dev_null - Vnstat on Merlin - UI, CLI and email - data use monitoring - with full install and menu.
See https://www.snbforums.com/threads/b...-monitoring-with-full-install-and-menu.70727/
NEW: Adds support for YazDHCP by @Jack Yaz - YazDHCP - feature expansion of DHCP assignments (increasing limit on the number of DHCP reservations)
See https://www.snbforums.com/threads/y...mit-on-the-number-of-dhcp-reservations.69247/
CHANGED: pixelserv-tls helper script to use CA for https WebUI (ps) now supports newly added routers to the Asuswrt-Merlin realm.
CHANGED: Firmware update check when running u now supports newly added Asuswrt-Merlin routers.
CHANGED: Entware installer gives option to use an existing but non-active Entware installation when found on a attached USB device.

Thanks @thelonelycoder for another uneventful update

 

[Tom Ames]

Thanks for your work! I would be scriptless without amtm and its add-ons.

 

[Ro berto]

Thank you decoderman
Stay safe and have a nice Sunday.

 

[randomuser931583]

May have found a bug:
Swapped out a USB drive as part of trying to fix an ongoing issue and was unable to install entware using "ep". Stopped executing when the device check occurred after selecting the location to install to. Occurred on 2 separate USB drives. I was able to install entware just fine through the diversion installer, however.

Thanks for making such useful utilities, it's appreciated.

 

[thelonelycoder]

May have found a bug:
Swapped out a USB drive as part of trying to fix an ongoing issue and was unable to install entware using "ep". Stopped executing when the device check occurred after selecting the location to install to. Occurred on 2 separate USB drives. I was able to install entware just fine through the diversion installer, however.

Thanks for making such useful utilities, it's appreciated.

Let me check that real quick.

 

[randomuser931583]

Let me check that real quick.

If it helps further, the printed output of the device check gave "1" followed by "OK" before exiting the task with no other messages printed.

 

[thelonelycoder]

If it helps further, the printed output of the device check gave "1" followed by "OK" before exiting the task with no other messages printed.

Yeah, I'm reverting that change to the previous version. This is unfinished code with test code mixed in.
My bad, it's been a while since I coded that part and thought I had finished it.

 

[Stevens243]

Updated, no issues. Nice to see. Was beginning to wonder if this was an abandoned project. Nice to see it's not.

 

[Clark Griswald]

Abandoned!?!

I hear from @thelonelycoder on the Forums more than I hear my own kids.

Stay Safe Everyone

 

[JoGi]

just updated amtm (3.1.9), I notice that the new option "vn Vnstate" has no reference on the webpage under addons > help & support?

 

[elorimer]

I updated amtm to 3.1.9. I did the update of vn-stat, no problem.
I then from amtm to YazDHCP updated YazDHCP from 1.01 to 1.02. The terminal printed the message that YazDHCP had been successfully updated and then hung. After a minute I exited with CTRL-C.

I then went back to amtm and did a uf of YazDHCP which went back to the main YazDHCP menu after a second.

 

[rgnldo]

Very good. Congratulations.

 

[thelonelycoder]

Abandoned!?!

I hear from @thelonelycoder on the Forums more than I hear my own kids.

Stay Safe Everyone

More work, less talk. Is that your family motto?

 

[thelonelycoder]

just updated amtm (3.1.9), I notice that the new option "vn Vnstate" has no reference on the webpage under addons > help & support?

That page is by @Jack Yaz , it will be supplemented as soon as he does find time.

 

[sentinelvdx]

Hi @thelonelycoder I'm getting this error

I did a format jffs, installed entware, swap and skynet... now I connected to it to continue installing addons and I'm getting this

Any idea why?

(It's a loop so I can't check dcl)

 

[Xentrk]

Hi @thelonelycoder I'm getting this error

I did a format jffs, installed entware, swap and skynet... now I connected to it to continue installing addons and I'm getting this

Any idea why?

(It's a loop so I can't check dcl)

Check to see if there are any messages in the System Log that may help shed some light on the issue.

 

[sentinelvdx]

Check to see if there are any messages in the System Log that may help shed some light on the issue.

I have done a factory reset, reinstalled everything, and configured all from scratch to avoid any issue carry over.

I'm running AMTM 3.1.9 on RT-AC88U with 386.2 Beta1
USB drive is running fine, I tested it several times

Yesterday after uninstalling conmon, I decided to go back to AMTM and noticed this every time I open it.

Spoiler: SSH

grep: error while loading shared libraries: libgcc_s.uo.1: cannot open shared ob                                       ject file: No such file or directory
grep: error while loading shared libraries: libgcc_s.uo.1: cannot open shared ob                                       ject file: No such file or directory
1  open     Diversion                      v
grep: error while loading shared libraries: libgcc_s.uo.1: cannot open shared ob                                       ject file: No such file or directory
grepgrep: : error while loading shared librarieserror while loading shared libra                                       ries: : libgcc_s.uo.1libgcc_s.uo.1: : cannot open shared object filecannot open                                        shared object file: : No such file or directoryNo such file or directory

2  open     Skynet

grep: error while loading shared libraries: libgcc_s.uo.1: cannot open shared ob                                       ject file: No such file or directory
grep: error while loading shared libraries: libgcc_s.uo.1: cannot open shared ob                                       ject file: No such file or directory
ep manage   Entware packages

grep: error while loading shared libraries: libgcc_s.uo.1: cannot open shared ob                                       ject file: No such file or directory
grep: error while loading shared libraries: libgcc_s.uo.1: cannot open shared ob                                       ject file: No such file or directory
grep: error while loading shared libraries: libgcc_s.uo.1: cannot open shared ob                                       ject file: No such file or directory
grep: error while loading shared libraries: libgcc_s.uo.1: cannot open shared ob                                       ject file: No such file or directory
grep: error while loading shared libraries: libgcc_s.uo.1: cannot open shared ob                                       ject file: No such file or directory
dc manage   Disk check script
grep: error while loading shared libraries: libgcc_s.uo.1: cannot open shared ob                                       ject file: No such file or directory

And syslog is showing:

Spoiler: Syslog

Mar 17 11:50:45 pixelserv-tls[9826]: generate_cert: failed to open file for write: /opt/var/cache/pixelserv/_.pipe.aria.microsoft.com
Mar 17 11:50:45 kernel: EXT4-fs error (device sda1): add_dirent_to_buf:1280: inode #524707: block 2105441: comm pixelserv-tls: bad entry in directory: directory entry across blocks - offset=40(40), inode=524573, rec_len=4112, name_len=6
Mar 17 11:50:50 pixelserv-tls[9826]: generate_cert: failed to open file for write: /opt/var/cache/pixelserv/_.pipe.aria.microsoft.com
Mar 17 11:50:50 kernel: EXT4-fs error (device sda1): add_dirent_to_buf:1280: inode #524707: block 2105441: comm pixelserv-tls: bad entry in directory: directory entry across blocks - offset=40(40), inode=524573, rec_len=4112, name_len=6
Mar 17 11:51:08 pixelserv-tls[9826]: generate_cert: failed to open file for write: /opt/var/cache/pixelserv/_.segment.io
Mar 17 11:51:08 kernel: EXT4-fs error (device sda1): add_dirent_to_buf:1280: inode #524707: block 2105441: comm pixelserv-tls: bad entry in directory: directory entry across blocks - offset=40(40), inode=524573, rec_len=4112, name_len=6
Mar 17 11:51:15 pixelserv-tls[9826]: generate_cert: failed to open file for write: /opt/var/cache/pixelserv/_.segment.io
Mar 17 11:51:15 kernel: EXT4-fs error (device sda1): add_dirent_to_buf:1280: inode #524707: block 2105441: comm pixelserv-tls: bad entry in directory: directory entry across blocks - offset=40(40), inode=524573, rec_len=4112, name_len=6
Mar 17 11:51:16 pixelserv-tls[9826]: generate_cert: failed to open file for write: /opt/var/cache/pixelserv/_.segment.io
Mar 17 11:51:16 kernel: EXT4-fs error (device sda1): add_dirent_to_buf:1280: inode #524707: block 2105441: comm pixelserv-tls: bad entry in directory: directory entry across blocks - offset=40(40), inode=524573, rec_len=4112, name_len=6
Mar 17 11:51:17 pixelserv-tls[9826]: generate_cert: failed to open file for write: /opt/var/cache/pixelserv/_.segment.io
Mar 17 11:51:17 kernel: EXT4-fs error (device sda1): add_dirent_to_buf:1280: inode #524707: block 2105441: comm pixelserv-tls: bad entry in directory: directory entry across blocks - offset=40(40), inode=524573, rec_len=4112, name_len=6
Mar 17 11:51:20 pixelserv-tls[9826]: generate_cert: failed to open file for write: /opt/var/cache/pixelserv/_.segment.io
Mar 17 11:51:20 kernel: EXT4-fs error (device sda1): add_dirent_to_buf:1280: inode #524707: block 2105441: comm pixelserv-tls: bad entry in directory: directory entry across blocks - offset=40(40), inode=524573, rec_len=4112, name_len=6
Mar 17 11:51:24 pixelserv-tls[9826]: generate_cert: failed to open file for write: /opt/var/cache/pixelserv/_.segment.io
Mar 17 11:51:24 kernel: EXT4-fs error (device sda1): add_dirent_to_buf:1280: inode #524707: block 2105441: comm pixelserv-tls: bad entry in directory: directory entry across blocks - offset=40(40), inode=524573, rec_len=4112, name_len=6
Mar 17 11:51:25 pixelserv-tls[9826]: generate_cert: failed to open file for write: /opt/var/cache/pixelserv/_.segment.io
Mar 17 11:51:25 kernel: EXT4-fs error (device sda1): add_dirent_to_buf:1280: inode #524707: block 2105441: comm pixelserv-tls: bad entry in directory: directory entry across blocks - offset=40(40), inode=524573, rec_len=4112, name_len=6
Mar 17 11:51:28 pixelserv-tls[9826]: generate_cert: failed to open file for write: /opt/var/cache/pixelserv/_.segment.io
Mar 17 11:51:28 kernel: EXT4-fs error (device sda1): add_dirent_to_buf:1280: inode #524707: block 2105441: comm pixelserv-tls: bad entry in directory: directory entry across blocks - offset=40(40), inode=524573, rec_len=4112, name_len=6
Mar 17 11:51:31 pixelserv-tls[9826]: generate_cert: failed to open file for write: /opt/var/cache/pixelserv/_.segment.io
Mar 17 11:51:31 kernel: EXT4-fs error (device sda1): add_dirent_to_buf:1280: inode #524707: block 2105441: comm pixelserv-tls: bad entry in directory: directory entry across blocks - offset=40(40), inode=524573, rec_len=4112, name_len=6
Mar 17 11:51:35 pixelserv-tls[9826]: generate_cert: failed to open file for write: /opt/var/cache/pixelserv/_.mixpanel.com
Mar 17 11:51:35 kernel: EXT4-fs error (device sda1): add_dirent_to_buf:1280: inode #524707: block 2105441: comm pixelserv-tls: bad entry in directory: directory entry across blocks - offset=40(40), inode=524573, rec_len=4112, name_len=6
Mar 17 11:51:38 pixelserv-tls[9826]: generate_cert: failed to open file for write: /opt/var/cache/pixelserv/_.mixpanel.com
Mar 17 11:51:38 kernel: EXT4-fs error (device sda1): add_dirent_to_buf:1280: inode #524707: block 2105441: comm pixelserv-tls: bad entry in directory: directory entry across blocks - offset=40(40), inode=524573, rec_len=4112, name_len=6
Mar 17 11:51:41 pixelserv-tls[9826]: generate_cert: failed to open file for write: /opt/var/cache/pixelserv/_.mixpanel.com
Mar 17 11:51:41 kernel: EXT4-fs error (device sda1): add_dirent_to_buf:1280: inode #524707: block 2105441: comm pixelserv-tls: bad entry in directory: directory entry across blocks - offset=40(40), inode=524573, rec_len=4112, name_len=6
Mar 17 11:51:42 pixelserv-tls[9826]: generate_cert: failed to open file for write: /opt/var/cache/pixelserv/_.mixpanel.com
Mar 17 11:51:42 kernel: EXT4-fs error (device sda1): add_dirent_to_buf:1280: inode #524707: block 2105441: comm pixelserv-tls: bad entry in directory: directory entry across blocks - offset=40(40), inode=524573, rec_len=4112, name_len=6
Mar 17 11:51:44 pixelserv-tls[9826]: generate_cert: failed to open file for write: /opt/var/cache/pixelserv/_.mixpanel.com
Mar 17 11:51:44 kernel: EXT4-fs error (device sda1): add_dirent_to_buf:1280: inode #524707: block 2105441: comm pixelserv-tls: bad entry in directory: directory entry across blocks - offset=40(40), inode=524573, rec_len=4112, name_len=6
Mar 17 11:51:45 pixelserv-tls[9826]: generate_cert: failed to open file for write: /opt/var/cache/pixelserv/_.mixpanel.com
Mar 17 11:51:45 kernel: EXT4-fs error (device sda1): add_dirent_to_buf:1280: inode #524707: block 2105441: comm pixelserv-tls: bad entry in directory: directory entry across blocks - offset=40(40), inode=524573, rec_len=4112, name_len=6
Mar 17 11:51:48 pixelserv-tls[9826]: generate_cert: failed to open file for write: /opt/var/cache/pixelserv/_.segment.io
Mar 17 11:51:48 kernel: EXT4-fs error (device sda1): add_dirent_to_buf:1280: inode #524707: block 2105441: comm pixelserv-tls: bad entry in directory: directory entry across blocks - offset=40(40), inode=524573, rec_len=4112, name_len=6
Mar 17 11:53:12 kernel: EXT4-fs error (device sda1): add_dirent_to_buf:1280: inode #524707: block 2105441: comm pixelserv-tls: bad entry in directory: directory entry across blocks - offset=40(40), inode=524573, rec_len=4112, name_len=6

 

[PeterR]

I have done a factory reset, reinstalled everything, and configured all from scratch to avoid any issue carry over.

I'm running AMTM 3.1.9 on RT-AC88U with 386.2 Beta1
USB drive is running fine, I tested it several times

Yesterday after uninstalling conmon, I decided to go back to AMTM and noticed this every time I open it.

The USB flash drive is corrupted, you should run a disk check, e.g.

umount /dev/sda1
/usr/sbin/e2fsck /dev/sda1

or use the amtm disk check script

 

[sentinelvdx]

The USB flash drive is corrupted, you should run a disk check, e.g.

umount /dev/sda1
/usr/sbin/e2fsck /dev/sda1

or use the amtm disk check script

I'll give a try to your commands as it's impossible to access amtm... it does a loop showing what I've shared.

I'm getting this, and I double checked it was removed:

ASUSWRT-Merlin RT-AC88U 386.2_beta1 Wed Mar 10 16:44:43 UTC 2021
sentinelvdx@RT-AC88U:/tmp/home/root# /usr/sbin/e2fsck /dev/sda1
e2fsck 1.45.6 (20-Mar-2020)
/dev/sda1 is in use.
e2fsck: Cannot continue, aborting.