spdMerlin spdMerlin v4.4.14 [2025-Jul-12] - Internet Speedtest and Monitoring Tool for AsusWRT Merlin

[ExtremeFiretop]

Something odd is happening.
I have auto speed tests configured for AUTOBW.
I have them excluded from QoS so QoS won't interfere.
Today, I configured a wireguard vpn client (wgc2). I included it in auto speed tests just for sake of fun.
Every speed test I realize (even with exclude from QoS), the wan interface is affected by QoS values, but the wgc2 don't as expected.
I tried to set my QoS down/up to 10mbps to test and yes, as soon as I start a speed test, it's capped to 10mbps on Wan (which isn't supposed), but not on wgc2.

What speedtest binary are you using? Built in or external? Does it make a difference to your observations?

 

[maghuro]

What speedtest binary are you using? Built in or external? Does it make a difference to your observations?

First thing I tried.
I'm using external, but I tested with both, same results.

 

[Martinski]

Something odd is happening.
I have auto speed tests configured for AUTOBW.
I have them excluded from QoS so QoS won't interfere.
Today, I configured a wireguard vpn client (wgc2). I included it in auto speed tests just for sake of fun.
Every speed test I realize (even with exclude from QoS), the wan interface is affected by QoS values, but the wgc2 don't as expected.
I tried to set my QoS down/up to 10mbps to test and yes, as soon as I start a speed test, it's capped to 10mbps on Wan (which isn't supposed), but not on wgc2.

I'm not very familiar with all configuration parameters used by spdMerlin, especially those regarding QoS (I don't use QoS or spdMerlin in my own home router). But, to gather some clues, I've added code to leave log messages during Speedtests when stopping and restarting QoS (if enabled).

This new code is available only in the latest 'develop' branch, so if you want to run the 'develop' version, you can switch from the installed 'master' branch to the latest 'develop' branch with the following command:

/jffs/scripts/spdmerlin develop

If you were already running the 'develop' branch version, you can force an update to get the very latest changes with the following command:

/jffs/scripts/spdmerlin forceupdate

If you run the latest 'develop' version, please provide the full output generated when running the Speedtest via the CLI menu.

 

[maghuro]

B

I'm not very familiar with all configuration parameters used by spdMerlin, especially those regarding QoS (I don't use QoS or spdMerlin in my own home router). But, to gather some clues, I've added code to leave log messages during Speedtests when stopping and restarting QoS (if enabled).

This new code is available only in the latest 'develop' branch, so if you want to run the 'develop' version, you can switch from the installed 'master' branch to the latest 'develop' branch with the following command:

/jffs/scripts/spdmerlin develop

If you were already running the 'develop' branch version, you can force an update to get the very latest changes with the following command:

/jffs/scripts/spdmerlin forceupdate

If you run the latest 'develop' version, please provide the full output generated when running the Speedtest via the CLI menu.

Besides those improved log messages, was anything changed between stable and develop version?
I'm asking because, after changing to develop and run a few speedtests with QoS set to a very low value (as I did on stable version), the QoS fully stops and the Speedtest runs at max speed

 

[Martinski]

Besides those improved log messages, was anything changed between stable and develop version?
I'm asking because, after changing to develop and run a few speedtests with QoS set to a very low value (as I did on stable version), the QoS fully stops and the Speedtest runs at max speed

Several changes have been accumulating in the 'develop' branch version since the latest production 4.4.12 release was issued on June 22. Among those, the only change that I can think of that may have an effect on the code dealing with QoS would be a 3-second delay that I added after stopping (and later restarting) QoS to allow the operation to be completed before initiating the Speedtest. I suppose it's possible that without the short delay, the Speedtest may have started "too early" while QoS was not yet completely stopped.

 

[maghuro]

Several changes have been accumulating in the 'develop' branch version since the latest production 4.4.12 release was issued on June 22. Among those, the only change that I can think of that may have an effect on the code dealing with QoS would be a 3-second delay that I added after stopping (and later restarting) QoS to allow the operation to be completed before initiating the Speedtest. I suppose it's possible that without the short delay, the Speedtest may have started "too early" while QoS was not yet completely stopped.

It sure must be, because it only happens on Wan speed test (which is the first). The ones following, QoS is fully stopped and don't get capped.

As soon as I change to stable again, same problem happens, so it must be the 3 second delay

 

[Martinski]

It sure must be, because it only happens on Wan speed test (which is the first). The ones following, QoS is fully stopped and don't get capped.

Yes, that makes sense. Since the WAN interface is always the first (unless you explicitly exclude it), it would be the most likely to be affected by QoS when the Speedtest was started "too early" while shutting off QoS.

 

[iTyPsIDg]

Martinski also added a command to reset the interfaces in PR: https://github.com/AMTM-OSR/spdMerlin/pull/35
Please try again by updating to the develop branch with Martinski's instructions, and report back after your reboot

Thanks!

Tested last night. The added delay was enough for one of my OVPN interfaces to come up, but not the second one.

Hopefully, it isn't too difficult for Viktor to add a reset to VPNMON-R3 because I think that is the best option.

 

[iTyPsIDg]

Tested last night. The added delay was enough for one of my OVPN interfaces to come up, but not the second one.

Hopefully, it isn't too difficult for Viktor to add a reset to VPNMON-R3 because I think that is the best option.

Success. I had both a Non-Responsive VPN slot failure last night and a reboot this morning and all interfaces are still included for spdmerlin.

Thank you all.

 

[Martinski]

Release Notes for spdMerlin v4.4.13 production version now available
[2025-July-03]

1) IMPROVED: Added a delay after stopping and then later after restarting QoS (if enabled) to allow the operation to be completed before initiating a Speedtest.

2) IMPROVED: Added log messages when stopping and later restarting QoS (if enabled).

3) IMPROVED: Added a delay to the reboot startup sequence that checks if VPN interfaces are up and ready for spdMerlin. This extra delay during reboot allows more time for all VPN interfaces to be initialized and become ready.

4) NEW: Added new CLI parameters "reset_interfaces force" to trigger an on-demand recheck of all VPN interfaces and reset them in cases where a VPN interface was previously found "disabled" but later becomes "enabled" and is now in a ready/active state.

[Based on a suggestion from @iTyPsIDg]​

The full command is the following:​

/jffs/scripts/spdmerlin reset_interfaces force

5) Miscellaneous code improvements.


The fork from @Jack Yaz's spdMerlin add-on is now hosted on the AMTM-OSR GitHub repo:

GitHub - AMTM-OSR/spdMerlin: spdMerlin is an internet speedtest and monitoring tool for AsusWRT Merlin with charts for daily, weekly and monthly summaries. It tracks download/upload bandwidth as well as latency, jitter and packet loss.

spdMerlin is an internet speedtest and monitoring tool for AsusWRT Merlin with charts for daily, weekly and monthly summaries. It tracks download/upload bandwidth as well as latency, jitter and pac...

github.com

 

[Martinski]

Release Notes for spdMerlin v4.4.14 production version now available
[2025-July-12]

1) FIXED: When choosing to set a preferred server for speed tests, a bug was causing an endless loop when the request to get the list of closest servers was sent and failed. Upon failure, the code was not checking for an empty list (it assumed at least 1 entry), so it went into an infinite loop generating "[: bad number" error messages and creating a large temporary file in the TMPFS partition while trying to parse the *empty* server list. This happened when using the WebUI page only.

2) FIXED: On the WebUI page, the Manual Speedtest using the "Choose a Server" option for "All" interfaces was not working when more than one interface was enabled; instead, it would appear to get "stuck" indefinitely waiting to get back some results.

3) FIXED: A bug was corrupting the configuration file when a user selected a preferred server for an interface, and the server name info happened to contain certain special characters (e.g. ampersand '&'). The result corrupted the entry for the specified interface in the configuration file.

4) IMPROVED: When the request to get a list of closest servers fails, an error notification is shown on the WebUI page, and a log message is sent to the system log.

5) IMPROVED: Added code to allow users to reset the preferred server selection for an interface.

6) Miscellaneous code improvements.

Example screenshot when the request to get the list of closest servers is sent and fails:

The fork from @Jack Yaz's spdMerlin add-on is now hosted on the AMTM-OSR GitHub repo:

GitHub - AMTM-OSR/spdMerlin: spdMerlin is an internet speedtest and monitoring tool for AsusWRT Merlin with charts for daily, weekly and monthly summaries. It tracks download/upload bandwidth as well as latency, jitter and packet loss.

spdMerlin is an internet speedtest and monitoring tool for AsusWRT Merlin with charts for daily, weekly and monthly summaries. It tracks download/upload bandwidth as well as latency, jitter and pac...

github.com

P.S. A special shout-out to my nephew Samuel for finding and reporting all 3 bugs that were fixed in this release. Great job, buddy!!