amtm amtm - the Asuswrt-Merlin Terminal Menu

[thelonelycoder]

hello
i wanted to get your advise regarding the reboot scheduler. it is not working for me at all. the router doesnt reboot on specified times. for example, as of today, it shouldve reset 2 days ago
how can i troubleshoot this?


View attachment 22799 View attachment 22800

thanks

The System Log will have error messages hinting for the reason why. Post them.

 

[thelonelycoder]

Opinions and suggestions welcome, dear users.
amtm is ubiquos, hence I consider it an essential app.
Therefore I consider to include less used scripts into amtm, along with a structured menu that groups (third party) scripts for a better user experience.

Independent of @dave14305 which focuses on the addons API at https://www.snbforums.com/threads/suggestions-for-merlin-add-ons.63399 I'm asking for opinions for:
- What existing script(s) is/are missing in amtm?
- What is your gripe with amtm?
- Things you expect to see or implemented in amtm

As always, I'm grateful for your replies.

 

[nzwayne]

Opinions and suggestions welcome, dear users.
amtm is ubiquos, hence I consider it an essential app.
Therefore I consider to include less used scripts into amtm, along with a structured menu that groups (third party) scripts for a better user experience.

Independent of @dave14305 which focuses on the addons API at https://www.snbforums.com/threads/suggestions-for-merlin-add-ons.63399 I'm asking for opinions for:
- What existing script(s) is/are missing in amtm?
- What is your gripe with amtm?
- Things you expect to see or implemented in amtm

As always, I'm grateful for your replies.

Thanks for an awesome tool. I'd like the time/date added to the main panel to complement the message of "All Scripts are up to date" to show when eg. 08:00 18Apr 2020.

 

[dave14305]

Things you expect to see or implemented in amtm

I think a backup scheduler would be a nice addition. Today, users must manually run backups in the GUI. Mine is simple, but I offer it as a conversation starter:

#!/bin/sh

BACKUPDIR=/tmp/mnt/Backup/Router

if [ -d "$BACKUPDIR" ]; then
        if [ -n "$1" ]; then
          FWVER="$1"
        else
          FWVER="$(nvram get buildno)_$(nvram get extendno)"
        fi

        rm -f "$BACKUPDIR"/settings_"$FWVER".cfg.bak 2>/dev/null
        cp -p "$BACKUPDIR"/settings_"$FWVER".cfg "$BACKUPDIR"/settings_"$FWVER".cfg.bak 2>/dev/null
        nvram save "$BACKUPDIR"/settings_"$FWVER".cfg

        rm -f "$BACKUPDIR"/jffs_"$FWVER".tar.bak 2>/dev/null
        cp -p "$BACKUPDIR"/jffs_"$FWVER".tar "$BACKUPDIR"/jffs_"$FWVER".tar.bak 2>/dev/null
        tar -cf "$BACKUPDIR"/jffs_"$FWVER".tar -C /jffs .

        rm -f "$BACKUPDIR"/nvram_"$FWVER".txt.bak 2>/dev/null
        cp -p "$BACKUPDIR"/nvram_"$FWVER".txt "$BACKUPDIR"/nvram_"$FWVER".txt.bak 2>/dev/null
        nvram show 2>/dev/null | sort > "$BACKUPDIR"/nvram_"$FWVER".txt
fi

 

[maghuro]

Opinions and suggestions welcome, dear users.
amtm is ubiquos, hence I consider it an essential app.
Therefore I consider to include less used scripts into amtm, along with a structured menu that groups (third party) scripts for a better user experience.

Independent of @dave14305 which focuses on the addons API at https://www.snbforums.com/threads/suggestions-for-merlin-add-ons.63399 I'm asking for opinions for:
- What existing script(s) is/are missing in amtm?
- What is your gripe with amtm?
- Things you expect to see or implemented in amtm

As always, I'm grateful for your replies.

Well, I have a suggestion. Batch updates on scripts.
A real example - Jack yaz released an update for almost all of his scripts at the same time and amtm said that they have updated. And then, we had to go manually inside each script to update.
So my suggestion is, when looking for updates (u option) on amtm, it asks "Do you want to update the script(s)?" And then amtm calls the update function of each script in need.

Edit: and... Thinking further... Why not a search updates scheduler and send notification by email, for example, like diversion does? And also, like diversion, notification on new Merlin firmware update.

 

[L&LD]

@maghuro while it seems like a timesaver on the surface, I would vote against any type of 'batch update' of scripts. That is right up there with Automatic updates (and usually, automatic anything) which have the possibility of really hosing any stable system, eventually.

 

[QuikSilver]

@maghuro while it seems like a timesaver on the surface, I would vote against any type of 'batch update' of scripts. That is right up there with Automatic updates (and usually, automatic anything) which have the possibility of really hosing any stable system, eventually.

I second @L&LD ....while it may be convenient to have it updated all at once I rather do it myself manually. I like to read the corresponding thread to see what issues may or may not arise before I update the corresponding script.

 

[maghuro]

@maghuro while it seems like a timesaver on the surface, I would vote against any type of 'batch update' of scripts. That is right up there with Automatic updates (and usually, automatic anything) which have the possibility of really hosing any stable system, eventually.

Well, you have a good point, sir. I totally agree and understand!

However the update check scheduler and email notifications for updates and firmware is a good feature, isn't it?

 

[L&LD]

@maghuro, I am one of the 'weird' ones here on this forum. I read every single post, even if it is way above my head. In the beginning, I had tested the amtm/Diversion email notifications and backup option and it worked flawlessly.

Today though, I don't need to read the same things twice.

This isn't a harmful feature and can be a great feature for some, but not one that I would use. That is why I didn't specifically comment on it, until asked.

 

[maghuro]

@maghuro, I am one of the 'weird' ones here on this forum. I read every single post, even if it is way above my head. In the beginning, I had tested the amtm/Diversion email notifications and backup option and it worked flawlessly.

Today though, I don't need to read the same things twice.

This isn't a harmful feature and can be a great feature for some, but not one that I would use. That is why I didn't specifically comment on it, until asked.

And I like you being that way!
Is people like you that the forums need! Always interested and keeping this going!

 

[thelonelycoder]

Well, you have a good point, sir. I totally agree and understand!

However the update check scheduler and email notifications for updates and firmware is a good feature, isn't it?

That's built into Diversion, one of the perks it offers. It checks for firmware updates (FWun), Diversion and amtm updates including amtm third party updates (DivUn).
One just has to enable it.

Edit: Building this rather large email function into amtm and effectively duplicating the functions is pointless IMHO.

 

[maghuro]

That's built into Diversion, one of the perks it offers. It checks for firmware updates (FWun), Diversion and amtm updates including amtm third party updates (DivUn).
One just has to enable it.

Edit: Building this rather large email function into amtm and effectively duplicating the functions is pointless IMHO.

I know sir... The problem is I don't use diversion

 

[L&LD]

I know sir... The problem is I don't use diversion

 

[maghuro]

Yes, shame on me
But as I'm using a DNS based solution (NextDNS), I really don't need diversion right now.
I've used it in the near past, and I know it's a fantastic and marvelous script, but now I'm in the DNS based mood

 

[dave14305]

Yes, shame on me
But as I'm using a DNS based solution (NextDNS), I really don't need diversion right now.
I've used it in the near past, and I know it's a fantastic and marvelous script, but now I'm in the DNS based mood

Even when I tested the NextDNS CLI, I still kept Diversion enabled because it handles dnsmasq logging so well, which is essential for troubleshooting issues with upstream DNS servers or services. But to avoid duplicate blocking, I use dnsmasq.postconf to remove the addn-hosts lines related to Diversion to allow the names to be forwarded upstream for blocking. And I still used Pixelserv as well, adding an alias command to dnsmasq.

#!/bin/sh

CONFIG="$1"
. /usr/sbin/helper.sh

. /opt/share/diversion/file/post-conf.div # Added by Diversion

if [ -f /tmp/nextdns.pid ] && [ -d "/proc/$(sed -n '1p' /tmp/nextdns.pid)" ]; then
        pc_delete "addn-hosts=/opt/share/diversion/list/" "$CONFIG"
        pc_append "alias=0.0.0.0,192.168.1.2" "$CONFIG"
fi

These reasons are why I still use Diversion today, despite occasional wanderings.

 

[maghuro]

Even when I tested the NextDNS CLI, I still kept Diversion enabled because it handles dnsmasq logging so well, which is essential for troubleshooting issues with upstream DNS servers or services. But to avoid duplicate blocking, I use dnsmasq.postconf to remove the addn-hosts lines related to Diversion to allow the names to be forwarded upstream for blocking. And I still used Pixelserv as well, adding an alias command to dnsmasq.

#!/bin/sh

CONFIG="$1"
. /usr/sbin/helper.sh

. /opt/share/diversion/file/post-conf.div # Added by Diversion

if [ -f /tmp/nextdns.pid ] && [ -d "/proc/$(sed -n '1p' /tmp/nextdns.pid)" ]; then
        pc_delete "addn-hosts=/opt/share/diversion/list/" "$CONFIG"
        pc_append "alias=0.0.0.0,192.168.1.2" "$CONFIG"
fi

These reasons are why I still use Diversion today, despite occasional wanderings.

Don't have doubt there's many reasons to use it, but as I'm starting only now to know everything related to this, I don't compreends very well what's dnsmasq nor pixelserv-tls or what they're supposed to do despite of being used for diversion to work.

Edit: I've learned some ifs and elifs and basic things like that, I've created (with great help) my script to put my dnsomatic being updated, I understand right now little things, but understanding those kind of things it's the next step, far from my actual compreension

 

[thelonelycoder]

I know sir... The problem is I don't use diversion

Your problem, you can't have it all

 

[thelonelycoder]

Even when I tested the NextDNS CLI, I still kept Diversion enabled because it handles dnsmasq logging so well, which is essential for troubleshooting issues with upstream DNS servers or services. But to avoid duplicate blocking, I use dnsmasq.postconf to remove the addn-hosts lines related to Diversion to allow the names to be forwarded upstream for blocking. And I still used Pixelserv as well, adding an alias command to dnsmasq.

#!/bin/sh

CONFIG="$1"
. /usr/sbin/helper.sh

. /opt/share/diversion/file/post-conf.div # Added by Diversion

if [ -f /tmp/nextdns.pid ] && [ -d "/proc/$(sed -n '1p' /tmp/nextdns.pid)" ]; then
        pc_delete "addn-hosts=/opt/share/diversion/list/" "$CONFIG"
        pc_append "alias=0.0.0.0,192.168.1.2" "$CONFIG"
fi

These reasons are why I still use Diversion today, despite occasional wanderings.

FYI, post-conf.div already sources the helper.sh file.

 

[maghuro]

Your problem, you can't have it all

Yeah, I know
Well, IMHO that part of code must be on amtm (because amtm is installed in firmware by default) and not inside diversion, because not everyone uses it...

Diversion must be only doing what it was very well designed for (blocking ads) and amtm being a "script manager", should have the option for schedule updates check, not div.

But that's my opinion

 

[thelonelycoder]

Yeah, I know
Well, IMHO that part of code must be on amtm (because amtm is installed in firmware by default) and not inside diversion, because not everyone uses it...

Diversion must be only doing what it was very well designed for (blocking ads) and amtm being a "script manager", should have the option for schedule updates check, not div.

But that's my opinion

I agree, you have a point there.
However, that code is huge and used in Diversion anyway for the stats and backup function. I would have to duplicate things. The update notification mails are a goodie for Diversion, the mail function was implemented for the stats function. Everything else came later.