What's new
  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

Release Asuswrt-Merlin 3004.388.10 is now available

RMerlin

Asuswrt-Merlin dev
Staff member
Asuswrt-Merlin 3004.388.10 is now available for legacy devices still on the 388 code branch. The focus of this release is the merge of new GPL, the new Connections tracking page, and the reorganization of the Tools pages.

Code:
3004.388.10 (4-Oct-2025)
  - NOTE: For developers, please note that the new default branch
          is now called "main" - it's what was previously the
          3006.102 branch.
          The "master" branch has been renamed "master-old", and
          is no longer actively used.  Due to how the 3006.102
          branch diverged, it was easier to do it this way than
          to fold back 3006.102 on top of master.
          3004.388 remains where 3004.388 models live.

  - NOTE: Due to numerous webui changes, it's recommended to
          force refresh the page after first login, or clear
          your browser cache.

  - NOTE: Asus has made some security related changes.  Password
          requirements are stricter, and UPNP is no longer
          enabled by default.  New password rules were
          slightly loosened for Asuswrt-Merlin, repeating
          characters are still allowed.

  - NEW: Completely redesigned System Log -> Connections page.
           - You can now filter the list
           - You can set the page to auto-refresh itself
           - Public IP addresses can be looked up on
             WhatismyIPaddress.com
           - Local hostnames will be resolved and shown
           - Routed IPv6 connections will be shown

  - NEW: Added Control-D servers to DNS-over-TLS
         presets (dave14305)
  - UPDATED: Merged GPL 388_25523.
  - UPDATED: dropbear to 2025.88.
  - CHANGED: Setting DNS Director to "Router" will now always
             redirect to the router's own IP.  Previously it
             would redirect to the first DNS server configured
             on the DHCP page (which defaults to the router
             itself).
             If you need DNS Director to redirect to an IP
             configured in your DHCP settings, use a Custom DNS
             entry in DNS Director.  This makes it more consistant
             with what the name implies, and was also necessary
             for improved Guest Network support.
  - CHANGED: Replaced netstat-nat by a fork called netstat-nat-ng.
             This fork fixes a number of issues with IPv6 and
             field size.
  - CHANGED: Optimized performance when refreshing the Sysinfo
             page on a network with thousands of tracked
             connections.
  - CHANGED: Modified the Quick Internet Setup wizard so not
             to attempt downloading firmware updates from Asus
             (which would fail anyway).
  - CHANGED: Tools category renamed System Info.
  - CHANGED: Tools -> Other Settings were moved to new tabs
             (Administration -> Tweaks, and
             Traffic Analyzer -> Settings).
  - CHANGED: Moved "Redirect to asusrouter.com" to the new
             Tweaks tab, and moved "Enable JFFS Custom Scripts"
             to the Basic Config section on the System page.
  - CHANGED: Backported Wireless Log hostname retrieval code
             from 3006 (based on IP instead of MAC)
  - FIXED: DNSDirector "Router" mode would not always work properly
           with IPv6 (now uses REDIRECT instead of DNAT, which was
           backported from iptables 1.4.19).
  - FIXED: Additionnal fix for the status frame missing from
           Network Map under certain hostnames.
  - FIXED: CVE-2025-9230 in OpenSSL (backport by RSDNTWK).


Please keep discussions on this specific release. This thread will be locked once feedback has died down.

Downloads are here.
Changelog is here.
 
Reserved post.
 
Dirty upgraded my RT-AX86U from 3004_388.9_2 ("dirty" because I only disabled Skynet and stopped AdGuard Home before doing the upgrade), update went fine and router rebooted well.
Cleared my browser cache before connecting to Admin Web page, look nice and look like smoother than before.
I read that some optimization and tweaks have been done and can't tell if it is linked, but:
  • Before doing the upgrade, I was around 100 MB free RAM
  • After the upgrade, I am now at 200 MB free RAM (same addons, no change)
Thank you very much for your work
 
Guest Network client addresses do not show up in Adguard Home after updating requests are coming from the routers ip 192.168.1.1 DNS Director Global redirection set to Router.
Edit: set to user defined instead of router and add adguard home ip fixes this issue now getting the same behavior as 3004.388.6
 
Last edited:
Guest Network client addresses do not show up in Adguard Home after updating requests are coming from the routers ip 192.168.1.1 DNS Director Global redirection set to Router.
Likely expected behavior. See the Change Log that RMerlin posted in the first post if you haven't already:
- CHANGED: Setting DNS Director to "Router" will now always redirect to the router's own IP. Previously it would redirect to the first DNS server configured on the DHCP page (which defaults to the router itself). If you need DNS Director to redirect to an IP configured in your DHCP settings, use a Custom DNS entry in DNS Director. This makes it more consistant with what the name implies, and was also necessary for improved Guest Network support.
 
Likely expected behavior. See the Change Log that RMerlin posted in the first post if you haven't already:
Yeah read the change log but didn't understand how the change affected my setup and there was no way to set dns address for guest network now everything is clear. Had to set dns director to user defined.
 
Just upgraded from beta2 via MerlinAU. No issues to report.
 
Yeah read the change log but didn't understand how the change affected my setup and there was no way to set dns address for guest network now everything is clear. Had to set dns director to user defined.
If you are not using AiMesh, you can use YazFi which allows you to set the DNS server(s) for WiFi Guest Network clients. YazFi example GUI attached.
 

Attachments

  • YazFi.png
    YazFi.png
    107.1 KB · Views: 10
Thank you for the amazing work! As I see legacy here, does that mean that my AX88U should be upgraded? I see the difference in version for BE88U (probably the one I would upgrade to) .
 
Not sure what happened here but I just updated an RT-AX3000 and an RT-AX58U (both nodes) and neither came back online. I had no problem through the alphas and beta. Odd, that hasn’t happened in a while. Had to reset both.
 
Thank you for the amazing work! As I see legacy here, does that mean that my AX88U should be upgraded? I see the difference in version for BE88U (probably the one I would upgrade to) .
No need to upgrade at this time, legacy simply means that development will be less active on these models. Asus is unlikely to add any new features for instance.

I will still backport things that I implement in 3006 and which still make sense in 3004, such as the new Connections page in this release. Same with the new Traffic Monitoring pages once I am done developing them.
 

Latest threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!

Staff online

Back
Top