Beta Asuswrt-Merlin 3004.388.9 Beta is now available

[dave14305]

Hopefully this is helpful. I am not familiar with Developer Tools.

Click the “Errors” and “Warnings” options to the right. Those are being hidden right now.

 

[RMerlin]

I spoke too soon. Diversion GUI does not render correctly, FF Nightly (x64), Linux

What version? Diversion 5.4.3 contains webui fixes, so make sure you are up-to-date.

 

[jrichard326]

Click the “Errors” and “Warnings” options to the right. Those are being hidden right now.

 

[jrichard326]

What version? Diversion 5.4.3 contains webui fixes, so make sure you are up-to-date.

 

[jrichard326]

Firefox , no extensions

 

[Wishmaster1965]

Dirty Update to my mesh router but on the firmware page it shows Current Version : 3004.388.4_beta3

 

[Unisoft]

What version? Diversion 5.4.3 contains webui fixes, so make sure you are up-to-date.

Answering on mobile, yes, on that version.

 

[Unisoft]

I spoke too soon. Diversion GUI does not render correctly, FF Nightly (x64), LinuxView attachment 64750

That is exactly the same as what I see.

 

[NikL]

Router AX86U.

 

[RMerlin]

Dirty Update to my mesh router but on the firmware page it shows Current Version : 3004.388.4_beta3

Either you downloaded and flashed a 2+ years old firmare, or you didn't flash it properly.

 

[aex.perez]

Didn't see anything in the change log about AiMesh.

Nothing changed since this AM when I applied the beta to one node. Still clients won't connect to the node runing the beta. Removed all the bindings and restarted. A client can move form the 388.8_4 node or router to another but not to the 388.9 beta node. Even downgrading to 388.9 beta node to 388.8_4 rebooting, and BACKUPMON recovery and no WiFi clients connect to it. Binding a WiFi client from the other node about 20ft away, to the node that was on the Beta which is inches away and now on 3888.8_4 and still will not accept a WiFi client. Same thing happpened with the Alpha 2 release.

So going down the WPS reset mode, then re-adding the node, then recover it from backup to get back to my normal.

As soon as I get stable, may try factory resetting the Router and Nodes, and getting them back on the Beta and then manually configuring everything to soo if the problem persists.

 

[aex.perez]

Didn't see anything in the change log about AiMesh.

Nothing changed since this AM when I applied the beta to one node. Still clients won't connect to the node runing the beta. Removed all the bindings and restarted. A client can move form the 388.8_4 node or router to another but not to the 388.9 beta node. Even downgrading to 388.9 beta node to 388.8_4 rebooting, and BACKUPMON recovery and no WiFi clients connect to it. Binding a WiFi client from the other node about 20ft away, to the node that was on the Beta which is inches away and now on 3888.8_4 and still will not accept a WiFi client. Same thing happpened with the Alpha 2 release.

So going down the WPS reset mode, then re-adding the node, then recover it from backup to get back to my normal.

As soon as I get stable, may try factory resetting the Router and Nodes, and getting them back on the Beta and then manually configuring everything to soo if the problem persists.

Ah!
After downgrading and rebooting, nothing. So on a whim, from the AiMesh GUI on the router, removed the node, and was able to re-add in. Then as soon as it was added, I bound a device to it and BAM it connected! So now on to recovery

 

[aex.perez]

After the downgrade of the node, and the recovery/reboot. All the clients can connect to it, bind to it again. As if nothing happened.

Something in this release is messing up AiMesh and prevents clients from connecting to a node, wreaking havoc if you have bound clients. Once back on 388.8-4, I still had to recover from the previous days backup to get the clients to connect to the beta node, that I put back on released code. Just a reboot to released code didn't work, had to do a BACKUPMON recovery as well.

I did take a snapshot of NVRAM but I doubt I'll see any differences between beta and released firmware.

When I have some time, or when/if there is a beta2, I'll try from a blank slate if a dirty upgrade gives me the same issues to try and narrow this down.

Thanks @RMerlin
Did learn under AiMesh on 388 Merlin firmware, wired nodes, AiMesh does work as intended from the Router GUI. Removing, Adding, was effortless and fully functional.
Even though I had some issues, betenn Alpha2 and this Beta, this was a great refresher if/when I run into a wall again

 

[Unisoft]

Another thing, sourceforge (the main downloads area) was blocked by browser because no valid certificate, and there were entries under AIProtection for sourceforge as "Disease Vector".
This was on 02 April 2025. It looks like the site is fine today.

I downloaded from Merlin's OneDrive mirror instead....

 

[Martinski]

Firefox , no extensions

View attachment 64757

I've made a few changes to the Diversion ASP file to address the errors reported on the browser console. If you would like to test this modified ASP file on your router, you can download and set it up from my GitHub repo using the following commands:

curl -LSs --retry 4 --retry-delay 5 --retry-connrefused \
 https://raw.githubusercontent.com/Martinski4GitHub/CustomMiscUtils/develop/Misc/GetDiversionWebPage.sh \
 -o "$HOME/GetDiversionWebPage.sh" && chmod 755 "$HOME/GetDiversionWebPage.sh" && $HOME/GetDiversionWebPage.sh

Once completed, check the Diversion WebUI page again. If you want to be sure that it's working, you can reboot the router after the modified WebUI page is downloaded and set up.

HTH

 

[jrichard326]

I've made a few changes to the Diversion ASP file to address the errors reported on the browser console. If you would like to test this modified ASP file on your router, you can download and set it up from my GitHub repo using the following commands:

curl -LSs --retry 4 --retry-delay 5 --retry-connrefused \
 https://raw.githubusercontent.com/Martinski4GitHub/CustomMiscUtils/develop/Misc/GetDiversionWebPage.sh \
 -o "$HOME/GetDiversionWebPage.sh" && chmod 755 "$HOME/GetDiversionWebPage.sh" && $HOME/GetDiversionWebPage.sh

Once completed, check the Diversion WebUI page again. If you want to be sure that it's working, you can reboot the router after the modified WebUI page is downloaded and set up.

HTH

Thank You. Your modification has fixed the issue here.

 

[laracroftonline]

No issues encountered so far which is good. Alpha 1 had so many broken pages but on this beta i haven’t seen those.

 

[RMerlin]

Another thing, sourceforge (the main downloads area) was blocked by browser because no valid certificate, and there were entries under AIProtection for sourceforge as "Disease Vector".
This was on 02 April 2025. It looks like the site is fine today.

I downloaded from Merlin's OneDrive mirror instead....

TrendMicro WRS was blocking Sourceforge downloads recently (not just Asuswrt-Merlin but other downloads as well). The certificate error is because your router's AiProtection is trying to redirect you to the Block page - you can see the certificate belongs to TrendMicro.

 

[Tex Texan]

Yeah, GUI issue here too...

 

[Unisoft]

On three

Yeah, GUI issue here too...

View attachment 64768

On three RT-AX86U routers, this page is OK and displays fine for me (it was just Diversions add-in tab that didn't display properly for me)