Beta Asuswrt-Merlin 3004.388.9 Beta is now available

[robinjoo1]

same thing.

different browser/machine

 

[ShlomiD]

different browser/machine

Tried Edge, same thing.
Tried on my cellphone, same thing.

 

[dave14305]

Tried Edge, same thing.
Tried on my cellphone, same thing.

Can you access either of these URLs?

https://www.asusrouter.com/device-map/router_status.asp

https://www.asusrouter.com/device-map/router.asp

 

[ShlomiD]

Can you access either of these URLs?

https://www.asusrouter.com/device-map/router_status.asp

https://www.asusrouter.com/device-map/router.asp

No, "ERR_NAME_NOT_RESOLVED"

 

[dave14305]

No, "ERR_NAME_NOT_RESOLVED"

Replace the name with whatever you call your router.

 

[ShlomiD]

Replace the name with whatever you call your router.

both addresses work, they show the status pages.

 

[dave14305]

both addresses work, they show the status pages.

Then I would suggest nothing is wrong with the firmware itself and you should look into your reverse proxy setup for clues. Unless you can demonstrate the same issue exists without the reverse proxy (i.e. direct from LAN), I’m not sure anyone else can help you with this rather specific access method.

 

[bennor]

I don't have any addons installed.

edit: weird issue, when accessing the web UI via IP address the gui shows up ok, I have only SCMerlin installed.
but when accessing via hostname from my reverse proxy the gui shows up like the screenshot I've uploaded a few messages back and I don't see SCMerlin either. very strange.

That would seem to indicate your problem likely lies with the reverse proxy.
On a side note, SCMerlin IS an addon.

 

[ShlomiD]

Then I would suggest nothing is wrong with the firmware itself and you should look into your reverse proxy setup for clues. Unless you can demonstrate the same issue exists without the reverse proxy (i.e. direct from LAN), I’m not sure anyone else can help you with this rather specific access method.

That would seem to indicate your problem likely lies with the reverse proxy.
On a side note, SCMerlin IS an addon.

Even without the addon the problem is the same.
Downgrading to the previous version mitigates the problem.
So what's changed? Nothing in my reverse proxy setup.

 

[Ripshod]

Even without the addon the problem is the same.
Downgrading to the previous version mitigates the problem.
So what's changed? Nothing in my reverse proxy setup.

The outstanding fact is - you're the one reporting this problem with your model router. I don't recall seeing anyone else with that router reporting this problem, therefore the problem is within your own network environment.
You're the one who created this more exotic setup. No one here knows what you have done, what is broken, or how to fix it.

 

[dave14305]

So what's changed? Nothing in my reverse proxy setup.

The firmware changed, obviously. Asus changed the underlying web UI code in the newer GPL source code. It doesn’t prove it’s broken if no other users report the same problem. I guess you can wait and see if anyone else besides Merlin confirms or denies your report for your specific model. With no browser errors, no browser extensions, and no Merlin 3rd party addons installed, there’s not much to go on except sharing specific details how your proxy is configured and what URL it uses for the router.

 

[ShlomiD]

The firmware changed, obviously. Asus changed the underlying web UI code in the newer GPL source code. It doesn’t prove it’s broken if no other users report the same problem. I guess you can wait and see if anyone else besides Merlin confirms or denies your report for your specific model. With no browser errors, no browser extensions, and no Merlin 3rd party addons installed, there’s not much to go on except sharing specific details how your proxy is configured and what URL it uses for the router.

I guess I'll wait, for the meantime I returned to using the router's IP address.

 

[Old Fart]

Asuswrt-Merlin 3004.388.9 Beta 1 is now available. Note that the BCM4912 devices are being migrated to 3006.102, therefore they will not be included in this or in future 3004.388 release.

The focus of this release is the merge of an updated GPL, updated components, and a few enhancements to VPN clients.

List of models that are not included in thise release, as they will be included in the next 3006.102 release:

 * GT-AX6000
 * ZenWifi Pro XT12
 * GT-AX11000 Pro
 * GT-AXE16000
 * RT-AX86U Pro
 * RT-AX88U Pro

Changelog:

3004.388.9 (xx-xxx-2025)
  - NOTE: BCM4912 models such as the GT-AX6000 have now been
         migrated to the 3006 firmware series.

  - NEW: (re-added) VPN interface selector on the Speedtest page,
         to test a VPN tunnel's throughput.
  - UPDATED: Merged GPL 388_25373.
  - UPDATED: dropbear to 2025.87.
  - UPDATED: OpenVPN to 2.6.13.
  - UPDATED: dnsmasq to 2.91.
  - UPDATED: miniupnpd to 2.3.7 (20250207 snapshot)
  - UPDATED: amtm to 5.2 (decoderman)
  - CHANGED: VPN public IP retrieval now uses HTTP instead of STUN,
             which should be more reliable through a VPN tunnel.
  - CHANGED: Model name will be inserted in the filename of JFFS
             backups.
  - CHANGED: Improved refresh behaviour of the VPN Status page.
  - CHANGED: Set rp_filter mode to "loose" on Wireguard client
             interfaces.
             Fixes gettunnelip.sh and onboard speedtest.
  - CHANGED: Display public IP address for Wireguard clients.
  - CHANGED: Make PCP requests also honor the Secure Mode setting
             (Self-Hosting-Group)
  - CHANGED: Settings/JFFS backup uploads file picker  will filter by
             file extension.
  - CHANGED: Added dhd userspace tool to RT-AX88U and GT-AX11000.
  - CHANGED: WAN IPv6 provided as second argument to the ddns-start
             script.
  - FIXED: CVE-2024-9143 in OpenSSL (Debian backport by RSDNTWK)
  - FIXED: Missing icon for the GT-AX11000 on AiMesh page.

Please keep discussions on this specific release. The thread will be locked once feedback dies down.

Downloads are here.
Changelog is here.

I don't see this beta for the GT-AX11000-PRO. I see 388.9 Beta1 for the GT-AX11000 (non pro) and GT-AXE11000 only
Was this an oversight?

 

[dave14305]

Was this an oversight?

Read the OP more closely, you Old Fart!

 

[Zastoff]

I don't see this beta for the GT-AX11000-PRO. I see 388.9 Beta1 for the GT-AX11000 (non pro) and GT-AXE11000 only
Was this an oversight?

List of models that are not included in this release

 

[Old Fart]

I don't see this beta for the GT-AX11000-PRO. I see 388.9 Beta1 for the GT-AX11000 (non pro) and GT-AXE11000 only
Was this an oversight?

Cancel My bad. Should have read the release more carefully.

 

[MacG32]

I can't log in to any of my Guest Networks, they won't authenticate and half of the pages don't load correctly, see below. I had to revert back to RT-AX86U_3004_388.8_4. I've also tried the beta twice to make sure the flash and everything else was correct.

Seems YazFi isn't working for my Guest Networks anymore. I am unable to log in to any of them. I fixed the pages not loading correctly. I flashed from a different browser.

Edit: I uninstalled YazFi, rebooted, and the guest networks show, but I'm unable to log into them.

 

[bennor]

Seems YazFi isn't working for my Guest Networks anymore.

Try installing the YazFi develop version (aka 4.4.5) which has some updates.

/jffs/scripts/YazFi develop
/jffs/scripts/YazFi forceupdate

 

[MacG32]

Try installing the YazFi develop version (aka 4.4.5) which has some updates.

/jffs/scripts/YazFi develop
/jffs/scripts/YazFi forceupdate

Thank you for your help, but it's still not working for some reason. Even with YazFi uninstalled and a reboot, I'm unable to log into any of my guest networks.

Edit: I reverted back to 3004.388.8_4 and I still can't log in to any of my guest networks with or without YazFi.

Edit: Did a factory reset and my guest networks seem to be working again on 3004.388.8_4.

 

[aex.perez]

Thank you for your help, but it's still not working for some reason. Even with YazFi uninstalled and a reboot, I'm unable to log into any of my guest networks.

Edit: I reverted back to 3004.388.8_4 and I still can't log in to any of my guest networks with or without YazFi.

Edit: Did a factory reset and my guest networks seem to be working again on 3004.388.8_4.

I had to revert as well, for a different reason and as AiMesh is closed source and not under Merlins pervue, really didn't have choice. But like you, reverting didn't fix things.

First time, I had to recover the Router and both nodes, but that was with Alpha 2 but I expect challenges with an Alpha release. The second time, with the Beta, exact same issues but I only applied it to one node, the low risk one. To try it out, first.

But even reverting to 388.8.4 and multiple reboots and other troubleshooting, nothing would connected over WiFi on that node (wired clients on the node never impacted) as soon as one WiFi device connected, everything else got shut out. I had to remove all the bindings and the devices would then connect to the Router and the other Node on 388.8.4. I to had to factory reset the node on the Beta and reapply 388.8.4 before any WiFi clients would connect through it.

But once downgraded, recovered my setup, and a final reboot everything was working as before.