Beta Asuswrt-Merlin 386.7 Beta is now available

[Mutzli]

This is great news. anyone else can confirm pixelserv-tls/diversion problems with RT-AX88 are gone with this beta ?

I think most problems from pixelserv -tls come from a large blocking list. Everything over 1million can bog down the router. I have about 350-400k blocked domains and never had any performance issues.

 

[Howard_inGA]

Sigh. It would help if I was actually studying current code rather than accidentally reviewing 386.5 alpha 2 code. For some reason my gt-ax11000 build folder wasn't synced up.

The aurargb_enable value is actually set by me in 386.7, it's something I changed a few weeks ago. I just need to remove that code that I added, and that nvram will stay put... That should solve the option found on the System page. It won't affect the hardware button, which seems fine by me - someone using that button might really want to fully disable or re-enable all lights.

EDIT: So, the revised behaviour that I just tested on my GT-AXE11000, regarding the System option to disable LEDs:

- If AuraRGB is enabled, then enabling/disabling LEDs will also control AuraRGB
- If AuraRGB is disabled, then enabling/disabling LEDs will not touch AuraRGB, leaving it off in both modes

This is actually the original behaviour before the 386.6 changes, and seems the most intuitive to me.

Brother, we all been there! It is soothing to know that even the best are still human...;-)

 

[RMerlin]

@RMerlin do you see a way to prevent memaccess to put its sh command later in the $PATH. See https://github.com/RMerl/asuswrt-merlin.ng/blob/master/release/src/router/memaccess/memaccess.c

This is clearly what's happening for @jsbeddow here: https://www.snbforums.com/threads/asuswrt-merlin-386-7-beta-is-now-available.79282/post-769255

Looks like I have to use absoulute paths like /bin/sh.

Not safely, no. A few years ago I removed this series of applets, thinking they were only for debugging. Then I wasted almost a week trying to track down a USB issue with the RT-AX56U, to e ventually discover that Asus does use some of these applets internally to write into registers, and it wasn't properly initializing the RT-AX56U because of the missing applet. So, I had to readd them.

So far I can see Asus uses the sw applet, I can't see any sh applet use, but that does not mean there aren't any. Could very well be within a closed source component.

The real question here is rather: why is /bin not ahead of /usr/sbin in that user's search path? Or is it his Entware's /opt/bin/sh symlink that's pointing at the wrong place (in which case this would be a bug with the Entware installer)?

BTW I couldn't reproduce the issue on my own RT-AC86U. Tried with Entware installed, without Entware installed - the correct sh instance was always at the start of my search path. To further troubleshoot you need to see that user's PATH content, as well as to where /opt/bin/sh points to.

 

[thelonelycoder]

BTW I couldn't reproduce the issue on my own RT-AC86U. Tried with Entware installed, without Entware installed - the correct sh instance was always at the start of my search path. To further troubleshoot you need to see that user's PATH content, as well as to where /opt/bin/sh points to.

Neither can I and all looks nice and tidy here:

RT-AC86U, 386.7 beta1, with Entware installed:

tlc@RT-AC86U-AD60:/tmp/home/root# echo $PATH
/opt/bin:/opt/sbin:/bin:/usr/bin:/sbin:/usr/sbin:/home/tlc:/mmc/sbin:/mmc/bin:/mmc/usr/sbin:/mmc/usr/bin:/opt/sbin:/opt/bin:/opt/usr/sbin:/opt/usr/bin

tlc@RT-AC86U-AD60:/tmp/home/root# which -a sh
/opt/bin/sh
/bin/sh
/usr/sbin/sh
/opt/bin/sh

tlc@RT-AC86U-AD60:/tmp/home/root# /opt/bin/sh --help
BusyBox v1.25.1 (2022-06-10 20:14:03 EDT) multi-call binary.
Usage: sh [-/+OPTIONS] [-/+o OPT]... [-c 'SCRIPT' [ARG0 [ARGS]] / FILE [ARGS]]
Unix shell interpreter

tlc@RT-AC86U-AD60:/tmp/home/root# /bin/sh --help
BusyBox v1.25.1 (2022-06-10 20:14:03 EDT) multi-call binary.
Usage: sh [-/+OPTIONS] [-/+o OPT]... [-c 'SCRIPT' [ARG0 [ARGS]] / FILE [ARGS]]
Unix shell interpreter

RT-AC86U, 386.7 beta1, no Entware or other scripts:

tlc@RT-AC86U-AD60:/tmp/home/root# echo $PATH
/bin:/usr/bin:/sbin:/usr/sbin:/home/tlc:/mmc/sbin:/mmc/bin:/mmc/usr/sbin:/mmc/usr/bin:/opt/sbin:/opt/bin:/opt/usr/sbin:/opt/usr/bin

tlc@RT-AC86U-AD60:/tmp/home/root# which -a sh
/bin/sh
/usr/sbin/sh

 

[RMerlin]

June 17th: Beta 2 has now been uploaded. Make sure you read the following note!
Changes since beta 1:

89778ae369 Updated documentation
5e7fd8632e rc: fix re-enabling wifi LEDs on the RT-AX86S
8fe761e94a HND5.02L07p2: replace dhd with build without debug enabled for RT-AX86U and GT-AXE11000
3605922c04 webui: change notification message shown if trying to enable AuraRGB while LEDs are disabled
0a54a8cf57 rc: don't re-enable AuraRGB when toggling LED stealth mode if it was previously disabled; remove dead code from setup_leds()
626bf4f117 HND5.02L07p2: fix mtd partition layout
45f552f233 httpd: fix wireless client log issue with guests (issue introduced with 67be92ce6b)
e8e525fd13 Bump version to beta 2

 

[Howard_inGA]

June 17th: Beta 2 has now been uploaded. Make sure you read the following note!
Changes since beta 1:

89778ae369 Updated documentation
5e7fd8632e rc: fix re-enabling wifi LEDs on the RT-AX86S
8fe761e94a HND5.02L07p2: replace dhd with build without debug enabled for RT-AX86U and GT-AXE11000
3605922c04 webui: change notification message shown if trying to enable AuraRGB while LEDs are disabled
0a54a8cf57 rc: don't re-enable AuraRGB when toggling LED stealth mode if it was previously disabled; remove dead code from setup_leds()
626bf4f117 HND5.02L07p2: fix mtd partition layout
45f552f233 httpd: fix wireless client log issue with guests (issue introduced with 67be92ce6b)
e8e525fd13 Bump version to beta 2

Eric, the new beta is showing on the home page for the 5300; but it can't be found on the download folder on the primary or alternate sites...

 

[RMerlin]

Eric, the new beta is showing on the home page for the 5300; but it can't be found on the download folder on the primary or alternate sites...

That's odd, it does show in my deploy log:

Deploying RT-AC5300 to Onedrive...
Deploying RT-AC5300 to Sourceforge...
RT-AC5300_386.7_beta1.zip                                                                                                                            100%   34MB   4.9MB/s   00:06

Give it a while, may be a sync delay on either of these.

EDIT: Oh, I forgot that this model had to be compiled from a separate branch, so the generated build is still the beta 1. I'll need to merge the beta 2 code on top of it and rebuild it. I'll upload it later tonight.

 

[GoNz0]

Beta2 nuked JFFS but I'd got a backup this time, so it's restored. Boot times twice as long during the flash and restore routines. DDNS is still bust on the home page.

 

[FLA_NL]

June 17th: Beta 2 has now been uploaded. Make sure you read the following note!
.......

Dirty update from 386.7_beta1 to 386.7_beta2 on a RT-AX86U following the note. Everything seems ok. Thanks!
cat /proc/mtd:
dev: size erasesize name
mtd0: 05f00000 00020000 "rootfs"
mtd1: 05f00000 00020000 "rootfs_update"
mtd2: 00800000 00020000 "data"
mtd3: 00100000 00020000 "nvram"
mtd4: 05f00000 00020000 "image_update"
mtd5: 05f00000 00020000 "image"
mtd6: 10000000 00020000 "dummy1"
mtd7: 10000000 00020000 "dummy2"
mtd8: 00100000 00020000 "misc3"
mtd9: 02f00000 00020000 "misc2"
mtd10: 00800000 00020000 "misc1"
mtd11: 05619000 0001f000 "rootfs_ubifs"
mtd12: 0001f000 0001f000 "METADATA"
mtd13: 0001f000 0001f000 "METADATACOPY"
mtd14: 0035591a 0001f000 "filestruct_full.bin"
mtd15: 006c8000 0001f000 "data"

 

[Tom Ames]

Dirty flash over 386.7 beta 1. Reformatted jffs.

Everything looking good so far @ ten minutes past the reboots.
Thanks!

 

[RMerlin]

Beta2 nuked JFFS but I'd got a backup this time, so it's restored. Boot times twice as long during the flash and restore routines. DDNS is still bust on the home page.

Something's abnormal with your setup if your RT-AC68U lost its JFFS content.

As for DDNS, from what I remember other people wrote to you earlier in the thread that the Go link was normal when using DNS-o-Matic.

 

[Clark Griswald]

Dirty flash of beta2 on both Main/AP "flashed" significantly faster, than "flash" to beta1.
I also forgot to unmount my USB prior to Flash, with no anomalies observed in my environment.
First time observing AX6000 FW Flash.
During flash I noticed a glowing red hue from the back of the 6000 while flash conducted. I only have the status led lights active, and all lights stayed as originally set after flash (No RGB). Never watching the router before, I never noticed the "red light".

 

[RMerlin]

I frequently see people reporting whether they flashed with a USB disk plugged or not... Just to clarify, flashing with a USB disk plugged is not a problem. It's just that if you actively use SMB sharing with that disk and your router's RAM is used for caching, then sometimes flashing may fail due to not having enough free RAM.

I suspect this might be less of an issue as Asus are now flushing buffers on some models when you log into the webui.

 

[G.host]

386.5_2 to 386.7_beta2 - update smooth!

 

[bluepoint]

June 17th: Beta 2 has now been uploaded. Make sure you read the following note!
Changes since beta 1:

89778ae369 Updated documentation
5e7fd8632e rc: fix re-enabling wifi LEDs on the RT-AX86S
8fe761e94a HND5.02L07p2: replace dhd with build without debug enabled for RT-AX86U and GT-AXE11000
3605922c04 webui: change notification message shown if trying to enable AuraRGB while LEDs are disabled
0a54a8cf57 rc: don't re-enable AuraRGB when toggling LED stealth mode if it was previously disabled; remove dead code from setup_leds()
626bf4f117 HND5.02L07p2: fix mtd partition layout
45f552f233 httpd: fix wireless client log issue with guests (issue introduced with 67be92ce6b)
e8e525fd13 Bump version to beta 2

Confirmed guess same LAN IP's are now fixed in Beta2. Thanks @RMerlin

 

[Deleted member 22229]

Dirty flash B2 over B1 AX58U. No Issues works great. Thanks Eric.

 

[AntonK]

Smooth update from 386.5_2 to 386.7_beta2. Everything is running normally without a hitch.

Thanks RMerlin!

 

[Akore]

386.7 beta1 to beta 2 on AC68U with Samba on and two HD drives attached. I always dirty flash with them connected and have never had an issue.

 

[QuikSilver]

Update to beta2 went smooth....FYI, Even though I was coming from 385_2 I still went ahead and followed the steps to upgrade firmware, wipe jffs partition. I had no problem coming from the latest stable release but figured why not just to make sure.

 

[emwgee]

GT-AX11000 smooth update from 386.7 beta1 to 386.7 beta2, so far so good.

AuraRGB LED on top now stays off after reboot if it was disabled previously.

Reboot tab won't reboot the router when pressed, but this is not new to 386.7 beta. It had happened to me for a long time, I lost track of which version it started.
I can only use the Android ASUS router app to reboot the router if I don't want to use the power switch.