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.9 is now available

Hi,
I had a issue after update today from RT-AX88U_3004_388.8_4 to this 388.9.
I have from years ago a custom /jffs/configs/dnsmasq.conf.add looking like this:
Code:
...
(1) interface=br0,br1
(2) dhcp-host=br0,5c:c3:cc:39:aa:cc,ignore ##_#_xyz1 Wifi #
(3) dhcp-host=br1,5c:c3:cc:39:aa:cc,xyz1,10.10.10.203,604800 ##_#_xyz1 Wifi #
...

After update, dnsmasq have this error:
Apr 27 01:29:19 A88X dnsmasq[13461]: DHCP host has multiple names at line 3 of /etc/dnsmasq.conf

At line (3) I have: "(3) dhcp-host=br1,5c:c3:cc:39:aa:cc,xyz1,10.10.10.203,604800 ##_#_xyz1 Wifi #"
I have br0 and br1 and I want to have xyz1 to be ignored on br0. It used to work until 388.9 with dnsmasq to 2.91.
If you have any suggestion, please share.
Thank you very much!

Later edit: after rollback to 388.8_4 the error disappeared without any other changes.
Solved by separating br like this:

Code:
(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 #
 
Hello!

Is there is a possibility for RT-AX56U to be updated from 3004.388.8_4 to 3004.388.9 or 3004.388.9_2?
I know that it is EOL, but it was still updated by ASUS on 2025/03/17.
 
Hello!

Is there is a possibility for RT-AX56U to be updated from 3004.388.8_4 to 3004.388.9 or 3004.388.9_2?
I know that it is EOL, but it was still updated by ASUS on 2025/03/17.
No. The RT-AX56 has been EOL for about two years, it already received a year of extra updates.

Also, Asus has never upgraded it to the 388 firmware series, unlike me.
 
Very well, if this new route is normal, I'll leave it as it is.
I'd rather ask the question here, because you never know if it could be a bug or something.
It seems to be related to WPS UPnP for SSDP. Is WPS enabled? Is UPnP enabled?
 
AX86U:
What is there to know about setting up the Guest Networks in this new Firmware regarding slot #1 vs 2 & 3?
I thought I saw a mention somewhere that said it's changed but that may have been for 3006.
I've always used 2 & 3 for isolation, so is that still the same or can you use slot 1? Something about the way subnets are being handled?

My upgrade went poorly and I had to rebuild from scratch. The cores were bouncing all over the place and pages were loading slow and erratically. Even the router reset was an issue, it would say complete with the wheel spinning and hang there.
I'm getting hammered with "China" which is in my Skynet country block list.
 
AX86U:
What is there to know about setting up the Guest Networks in this new Firmware regarding slot #1 vs 2 & 3?
I thought I saw a mention somewhere that said it's changed but that may have been for 3006.
I've always used 2 & 3 for isolation, so is that still the same or can you use slot 1? Something about the way subnets are being handled?

My upgrade went poorly and I had to rebuild from scratch. The cores were bouncing all over the place and pages were loading slow and erratically. Even the router reset was an issue, it would say complete with the wheel spinning and hang there.
I'm getting hammered with "China" which is in my Skynet country block list.
Nothing has changed with respect to guest networks in this release compared to the previous releases. The 3006 firmware is completely different.
 
Nothing has changed with respect to guest networks in this release compared to the previous releases. The 3006 firmware is completely different.
Thank you! Didn't want to reload that configuration just yet. Trying to do the bare minimum and avoid another reset.
 
Thank you! Didn't want to reload that configuration just yet. Trying to do the bare minimum and avoid another reset.
Just for point of reference this update went just fine on my AX86U including guest network 2 devices (no reserved addresses). Regular LAN has a few reserved, both ethernet and wifi and that worked just fine too.
 
Dirty upgrade from 3004.388.9 (hard reset 4/28) => so far, so good. Thank you Merlin.
 
It seems to be related to WPS UPnP for SSDP. Is WPS enabled? Is UPnP enabled?
Hello, I checked and UPnP is disabled. It's all the same for WPS in the 2.4 Ghz and 5 Ghz networks.
Note : the router has been completely reset and there are no addons or anything, everything is original.

I can see from your Github post that there's a link between the new route 239.x.x.x and the UPnP WPS option (this route should therefore not be present with options disabled).
This must be a bug and not a ghosts problem...

Maybe @RMerlin should take a look.

1745995197293.png
 
Last edited:
Maybe that was the bug in earlier versions. 239.0.0.0/8 is meant for private/internal use.

Sorry just catching up after a long day yesterday, but in my example/setup I have WPS disabled, but I do have UPnP enabled. I could try to disable it but considering what @Unetwork said I doubt it would make a difference.

Either way as @dave14305 linked, my understanding is that this route is supposed to be there, which is why i just never dived much deeper into it myself.

A multicast route should not harm anything so while it is a "difference" I noticed in Alpha I would generally aim towards it being a good one.

if I truly believed it was breaking something I would of poked and prodded at it a bit more. My 2 cents is this leave it be unless you actually notice it causing issues or breaking something.
 
Maybe that was the bug in earlier versions. 239.0.0.0/8 is meant for private/internal use.
It could be.
We'd need confirmation.

@ExtremeFiretop
Indeed, so far, there doesn't seem to be any problem with the router working properly, but I'm still curious and would like confirmation that this route is compliant or not.
 
One thing's for sure, this route was not present in previous versions of 388.8.
There are posts going back five years which show this route. Even on firmware 386.1. I've yet to see an obvious corelation for it appearing or not.

 
There are posts going back five years which show this route. Even on firmware 386.1. I've yet to see an obvious corelation for it appearing or not.

Thanks for this information, but I never use AiMesh.
So the route shouldn't appear ? strange.
 
Thanks for this information, but I never use AiMesh.
So the route shouldn't appear ? strange.
That post was just one example. Most of the others I found were discussing VPN problems. But that's not to say it's VPN related, just that those sort of posts are more like to contain people's routing tables. In any case I don't think it's a problem as such.
 
Very well, I understand.
For the record, even if it's not the cause, I don't use the VPN part...
We'll see if Rmerlin can take a look and find out the reason for this mysterious route.
 

Similar 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!
Back
Top