Release Asuswrt-Merlin 3004.388.9 is now available

[Mikeyy]

3004.388.9_2 is now available, fixing a couple of issues:

  - UPDATED: miniupnpd to 2.3.8.
  - FIXED: CVE-2025-2492 in AiCloud (backport from upstream)
  - FIXED: Networkmap system status frame failing to load when
           accessing the router with some particular hostnames.
  - FIXED: Networkmap client list wordwrapping long hostnames.
  - FIXED: webui issue when DDNS set to Custom.
  - FIXED: Compatibility issues with IoT devices and WPA2/WPA3
           networks (Asus)

Thank you! Custom DDNS is working now.

 

[hkp]

Solved by separating br like this:

(1) interface=br0
(2) dhcp-host=5c:c3:cc:39:aa:cc,ignore ##_#_xyz1 Wifi #

(3) interface=br1
(4) dhcp-host=5c:c3:cc:39:aa:cc,xyz1,10.10.10.203,604800 ##_#_xyz1 Wifi #

I installed version: 3004.388.9 on RT-AX86U a couple of weeks ago and found a strange problem with custom hostname settings in /jffs/configs/dnsmasq.conf.add. The error log kept on saying that there was a duplicate IP address at line x. I removed all the assignments but one, even then it was complaining of the same error.

Apr 14 15:53:36 RT-AX86U custom_config: Appending content of /jffs/configs/dnsmasq.conf.add.
Apr 14 15:53:36 RT-AX86U custom_script: Running /jffs/scripts/dnsmasq.postconf (args: /etc/dnsmasq.conf)
Apr 14 15:53:36 RT-AX86U dnsmasq[31536]: duplicate dhcp-host IP address 10.0.0.3 at line 157 of /etc/dnsmasq.conf
Apr 14 15:53:36 RT-AX86U dnsmasq[31536]: FAILED to start up

Looks like the new version 3004.388.9 has a different way to set the hostname based on the MAC. I found the setting by manually setting it under LAN->DHCP Server and then checked the /etc/dnsmasq.conf.

Before upgrade:
dhcp-host=XX:XX:XX:XX:XX:XX,hostname,10.0.0.3,Motorola-1

After upgrade:
dhcp-host=XX:XX:XX:XX:XX:XX,set:XX:XX:XX:XX:XX:XX,Motorola-1,10.0.0.3

I changed all the entries in /jffs/configs/dnsmasq.conf.add. Now it works fine.

Last night I saw that the minor version: 3004.388.9_2 is available now, went ahead and installed it. All the settings are working fine with the minor version as well without any changes.

 

[Djurre Swets Pieters]

Hi, the latest firmware on my RT-AX58AU mesh network (RT-AX58U_3004_388.9_2) has the same issue at the previous one. All connections to my Google equipment are lost.
So I flashed back to RT-AX58U_3004_388.8_4 where I have no issues.

 

[Mikeyy]

Hi, the latest firmware on my RT-AX58AU mesh network (RT-AX58U_3004_388.9_2) has the same issue at the previous one. All connections to my Google equipment are lost.
So I flashed back to RT-AX58U_3004_388.8_4 where I have no issues.

That means exactly what?

 

[ramthrou]

I'm currently stuck on 388.7 after experiencing lots of Aimesh node-instability with the 388.8 branch on my AX86S Aimesh based network with AC86 and AC68U nodes (wired and wireless).

Can anybody with a working 388.7 Aimesh setup who also experienced instabilities with 388.8 please report their experiences with 388.9?

 

[aex.perez]

I'm currently stuck on 388.7 after experiencing lots of Aimesh node-instability with the 388.8 branch on my AX86S Aimesh based network with AC86 and AC68U nodes (wired and wireless).

Can anybody with a working 388.7 Aimesh setup who also experienced instabilities with 388.8 please report their experiences with 388.9?

Works great, but mixing AC and AX devices, different generations, on a mesh network and asking them to operate, is inviting inviting instability.
I've been there, and swapped my old AC5300's for AX86u's to pair with the AX88u. To improve stabiliy, configure optins with the oldest device in mind.

 

[ramthrou]

Works great, but mixing AC and AX devices, different generations, on a mesh network and asking them to operate, is inviting inviting instability.
I've been there, and swapped my old AC5300's for AX86u's to pair with the AX88u. To improve stabiliy, configure optins with the oldest device in mind.

Just to be clear: you experienced stability with 388.7, instability with 388.8, and now stability again with 388.9 in your Aimesh network? Or did you experience stability with all of them or start on 388.9?

I'm not going to upgrade my whole fleet of perfectly functioning in terms of specs AC86 and AC68 routers and throw money at/dig myself deeper in the Asus-hole when they can't even get mature models like this to work.

I do run the official asuswrt on all the nodes btw., as should you and anybody (higher likeliness of Aimesh instability with Merlin).

 

[aex.perez]

Just to be clear: you experienced stability with 388.7, instability with 388.8, and now stability again with 388.9 in your Aimesh network? Or did you experience stability with all of them or start on 388.9?

I'm not going to upgrade my whole fleet of perfectly functioning in terms of specs AC86 and AC68 routers and throw money at/dig myself deeper in the Asus-hole when they can't even get mature models like this to work.

I do run the official asuswrt on all the nodes btw., as should you and anybody (higher likeliness of Aimesh instability with Merlin).

Well as mine it likely much more stable, I'll stay as is. No need to replace, just configure to the feature set of the oldest device, or more relevant don't use AX86u newer functionality and expect your AC86, or AC68 not to complain and introduce instability.

Configure to the lowest common denominator.

 

[ramthrou]

Just to be clear: you experienced stability with 388.7, instability with 388.8, and now stability again with 388.9 in your Aimesh network? Or did you experience stability with all of them or start on 388.9?

Well as mine it likely much more stable, I'll stay as is.

I'm sorry, was that a no or a yes? I asked a very specific question for a specific reason. If you had no issues with 388.8, your answer does not apply to the use-case I'm seeking feedback on at all – I need to know if there has been a change in stability from 388.8 to 388.9, not if there are people experiencing issues with neither.

I asked because I need to know if anything has changed for people with 388.8 issues. I remember there were others who experienced stability issues related to 388.8 as well.

No need to replace, just configure to the feature set of the oldest device, or more relevant don't use AX86u newer functionality and expect your AC86, or AC68 not to complain and introduce instability.

Configure to the lowest common denominator.

There are no new functionalities for Aimesh nodes with 388 over 386 as far as I know. With 3006 there is Guest Network Pro with VLAN if you want to become a beta-tester, but 388, I think there are none.

 

[FTC]

Hi, I just saw in 388.9_2 (router is rt-ax88u) that the graph 'Threat Activities' under the different 'AiProtection' tabs is corrupted (shows only data points for the first day of the secuence). Anyone else seeing this ? is this a known bug ?.
I already attempted to erase the AiProtection database,and restart AiProtection but same thing happens with an empty one, which makes me belive this is more of a presentation issue.
Note that to force / test some AiProtection errors you can navigate to wicar. org and choose to test some threats.

 

[ExtremeFiretop]

I'm sorry, was that a no or a yes? I asked a very specific question for a specific reason. If you had no issues with 388.8, your answer does not apply to the use-case I'm seeking feedback on at all – I need to know if there has been a change in stability from 388.8 to 388.9, not if there are people experiencing issues with neither.

I asked because I need to know if anything has changed for people with 388.8 issues. I remember there were others who experienced stability issues related to 388.8 as well.



There are no new functionalities for Aimesh nodes with 388 over 386 as far as I know. With 3006 there is Guest Network Pro with VLAN if you want to become a beta-tester, but 388, I think there are none.

So to clarify, your 5 firmware versions behind and still having the same issue?
It's either a very specific issue that has not yet been properly reported/identified, or a configure issue of some kind.

Can you link us to your identified reports of issues in 388.8 that your talking about?
What is the issue exactly that your trying to bring up?

You asked a very specific question that is very unlikely to get a very specific answer without more details. "Instability" means what exactly?

For the sake of argument, even if I was a user that thought I might be in a similar boat to you with random crashing 388.8... I'd go..
"what does instability mean? Does he mean crashing like me or something else?"

It could be hard kernel crashing? WiFi disconnects with endpoint devices or between the nodes and the primary? Unable to actually flash the firmware?
Any specific errors your dealing with on the newer firmware in the system logs? Kinda unreasonable to expect anyone to go back 4-5 firmware versions to dig up this info other than yourself being impacted.

The chances of someone being in the same boat as you and reporting back are low considering most people are not 5 versions behind, I would focus on how to troubleshoot the existing firmware issues (if you even still have them).
Maybe the best move for you is make a backup of everything on 388.7, and then test a single node or router on 388.9 first, and troubleshoot a single node instead of upgrading your "whole fleet" of 3 routers. My 2 cents.

 

[Unetwork]

@FTC Hello, I've noticed the same display problem on the AiProtection graphic (AX88U)
It did not exist on the previous version 388.8 :

Secondly, when you display the list of clients on the home page, the IP addresses are not centered in the case, they're on the left, there's a big space.
It's a small bug, but if it could be fixed, that would be great.

Thanks again to @RMerlin for his work.

 

[ramthrou]

So to clarify, your 5 firmware versions behind and still having the same issue?
It's either a very specific issue that has not yet been properly reported/identified, or a configure issue of some kind.

I'm two versions behind the newly released one, which means i skipped one version and am now asking about the new one. Not as dramatic as you make it sound, really. We're not counting the small incremental updates inbetween which doesn't upgrade the GPL, where the problem most likely resides.

Can you link us to your identified reports of issues in 388.8 that your talking about?
What is the issue exactly that your trying to bring up?

You asked a very specific question that is very unlikely to get a very specific answer without more details. "Instability" means what exactly?

For the sake of argument, even if I was a user that thought I might be in a similar boat to you with random crashing 388.8... I'd go..
"what does instability mean? Does he mean crashing like me or something else?"

It could be hard kernel crashing? WiFi disconnects with endpoint devices or between the nodes and the primary? Unable to actually flash the firmware?
Any specific errors your dealing with on the newer firmware in the system logs?

Clients disconnecting and reconnecting ("micro-disconnections"). A very common problems with Asus and Aimesh setup which is resolved by reverting to the previous FW and waiting for a new one to fix that (and probably break something else, but hopefully not too significant), or wasting your life trying to chase down a million squirrels representing different settings on both the router and clients, to no avail because it turns out to be Asus abscent QC.

Kinda unreasonable to expect anyone to go back 4-5 firmware versions to dig up this info other than yourself being impacted.

The chances of someone being in the same boat as you and reporting back are low considering most people are not 5 versions behind, I would focus on how to troubleshoot the existing firmware issues (if you even still have them).
Maybe the best move for you is make a backup of everything on 388.7, and then test a single node or router on 388.9 first, and troubleshoot a single node instead of upgrading your "whole fleet" of 3 routers. My 2 cents.

The chances of somebody having to skip a version because of issues is fairly high in the Asus neck of the woods.

As i mentioned, I remember reading others having issues with 388.8, which is why I specifically asked people who were still on 388.7 who had tried the new 388.9.

 

[ExtremeFiretop]

I'm two versions behind the newly released one, which means i skipped one version and am now asking about the new one. Not as dramatic as you make it sound, really. We're not counting the small incremental updates inbetween which doesn't upgrade the GPL, where the problem most likely resides.

"Most likely" being the key word above, if you don't know, it's assuming.
Without proper testing we do NOT actually know, and we don't run on assumptions which is why your mostly seeing crickets with your report.

Just because you don't count the minor versions doesn't mean they don't exist, so actually yes it's 5 versions to everyone else following the threads and updating on a consistent bases.
If we were to only count GPL updates as actual updates; we wouldn't get anywhere fast since GPL updates fully rely on ASUS, and many changes are done between the GPL updates from @RMerlin just as an example.

Just because a GPL change is "likely" the culprit means very little until backed with evidence of logs of a specific version where it starts.
This is why I am asking for such evidence and troubleshooting around the issue, so we can properly note the issue your experiencing.

Clients disconnecting and reconnecting ("micro-disconnections"). A very common problems with Asus and Aimesh setup which is resolved by reverting to the previous FW and waiting for a new one to fix that (and probably break something else, but hopefully not too significant), or wasting your life trying to chase down a million squirrels representing different settings on both the router and clients, to no avail because it turns out to be Asus abscent QC.

Whether or not ASUS missed it in QC; does not help us or them narrow it down further.

If the problem really exists in the code base, you should be able to replicate it, and we should be able to narrow it down.
Do you have system logs showing the issues? Until we receive logs or any further troubleshooting or evidence; your going to be clearly spinning your tires in the mud.

The chances of somebody having to skip a version because of issues is fairly high in the Asus neck of the woods.

As i mentioned, I remember reading others having issues with 388.8, which is why I specifically asked people who were still on 388.7 who had tried the new 388.9.

And have you found those posts again to share? Again for the sake of argument, even if I believe you, where should I start? How would I replicate?
Most people here clearly don't have this issue; and your telling us it exists without logs or screenshot of the problem and configuration.

You might think your chances are high of getting a useful response with someone serving you the answer on a silver platter, but based on the hours going by.... Not so sure.
You should really focus on properly troubleshooting and reporting the issues in current versions where they exist (maybe with a single node first) and report back.

Thanks!

 

[FTC]

@FTC Hello, I've noticed the same display problem on the AiProtection graphic (AX88U)
It did not exist on the previous version 388.8 :

View attachment 65501

Secondly, when you display the list of clients on the home page, the IP addresses are not centered in the case, they're on the left, there's a big space.
It's a small bug, but if it could be fixed, that would be great.
Thanks again to @RMerlin for his work.

View attachment 65502

Thanks for the info. Time to wait for a new release/fix then... although as you mention, this two are quite minor things.

 

[JIPG]

Thanks for the info. Time to wait for a new release/fix then... although as you mention, this two are quite minor things.

Same problem here with the AiProtection graphics.It was not there in FW 388.8.
Regarding the location of the ip adress, there is a big space to acomodate an ipv6 address additionally to the ipv4 one.

 

[Mutzli]

Same problem here with the AiProtection graphics.It was not there in FW 388.8.
Regarding the location of the ip adress, there is a big space to acomodate an ipv6 address additionally to the ipv4 one.

I assume that the AiProtection graphics issue was introduced with the last GPL merger and since everything Trend Micro is closed source it's not something that can be fixed by Merlin.

 

[JIPG]

I assume that the AiProtection graphics issue was introduced with the last GPL merger and since everything Trend Micro is closed source it's not something that can be fixed by Merlin.

Unfortunately ...

 

[dave14305]

I've noticed the same display problem on the AiProtection graphic (AX88U)
It did not exist on the previous version 388.8 :

In the browser, enter the url as:

http://192.168.50.1/getNonIPSChart.asp?type=mals

And post the result here. Adjust the URL to match your setup (http/https, router IP or asusrouter.com, special port if https, etc).
Mine looks like:

data = '[["0", "0", "0", "0", "0", "0", "0"]]';

 

[JIPG]

In the browser, enter the url as:

http://192.168.50.1/getNonIPSChart.asp?type=mals

And post the result here. Adjust the URL to match your setup (http/https, router IP or asusrouter.com, special port if https, etc).
Mine looks like:

data = '[["0", "0", "0", "0", "0", "0", "0"]]';

This is my result: data = '[["0", "0", "0", "0", "0", "0", "0"]]'