Release ASUS RT-AX58U Firmware version 3.0.0.4.388_25155 (2025/03/17)

[fruitcornbread]

Version 3.0.0.4.388_25155
95.05 MB
2025/03/17

1. Fixed the UI issue in Chrome.
2. Fixed client binding issues in Mesh scenarios.
3. Enhanced input parameter handling techniques to improve data processing stability and system security.
4. Enhance system access control mechanisms.

ZIP SHA-256 : E4706FDDF6116F9E17E92C7D8CB2AEBDAA4D229BA332013AE8A99B865CFB2839
FW SHA-256 : 1221f3dadd5e2bfb1c6e4d59a4029d1727ae9c4a38fc71c5f4029e1f4a407881

Download: https://dlcdnets.asus.com/pub/ASUS/wireless/RT-AX58U/FW_RT_AX58U_300438825155.zip?model=RT-AX58U

 

[jksmurf]

Version 3.0.0.4.388_25155
95.05 MB
2025/03/17

1. Fixed the UI issue in Chrome.
2. Fixed client binding issues in Mesh scenarios.
3. Enhanced input parameter handling techniques to improve data processing stability and system security.
4. Enhance system access control mechanisms.

ZIP SHA-256 : E4706FDDF6116F9E17E92C7D8CB2AEBDAA4D229BA332013AE8A99B865CFB2839
FW SHA-256 : 1221f3dadd5e2bfb1c6e4d59a4029d1727ae9c4a38fc71c5f4029e1f4a407881

Download: https://dlcdnets.asus.com/pub/ASUS/wireless/RT-AX58U/FW_RT_AX58U_300438825155.zip?model=RT-AX58U

Wonder how the GPL compares to what was in RMerlin's Jan 25 Alpha.

 

[visortgw]

Wonder how the GPL compares to what was in RMerlin's Jan 25 Alpha.

Merlin 3004_388.9_alpha1-g64ce422528 (25 January 2025) was built with GPL v25373 — purely by number, Merlin's newer.

 

[RMerlin]

Merlin 3004_388.9_alpha1-g64ce422528 (25 January 2025) was built with GPL v25373 — purely by number, Merlin's newer.

Numbers don`t mean much, they are not sequential. Frequently, Asus will take a specific release, apply a patch on it, and bump the number up for that specific model.

 

[Yakkosmurf]

I have one of these as an AI Mesh node. I performed the update through the app on my iPad. After the install and reboot, my two wireless clients that are bound to this node can’t connect. No, other wireless clients will connect to it either. Everything has been rebooted several times. My router can see the node through the wired backhaul, and reports no errors. Going to try and roll back the firmware and then delete and re-add the node to the mesh if needed.

 

[Yakkosmurf]

Got a few minutes to troubleshoot sooner in the day than I expected. I rolled back to the 25139 firmware by uploading the file from my computer. After the node came back up, the wireless clients immediately started connecting to it as usual.

 

[Tech9]

Try removing and re-adding the node instead. There are changes in AiMesh and I suspect mass firmware upgrade is related.

 

[Yakkosmurf]

When I've got some time, I'll update again and try removing and adding the node.

 

[jksmurf]

I couldn’t get the FW to load via the WebGui (it’s a wireless backhaul mesh node). I might reset the thing, upgrade it wired to a notebook, then reset it again as a node.

TBH I’m not expecting wonders or indeed any noticeable differences at all when you just use it as a node, but I’ve often had problems getting AIMesh to recognize this node wirelessly, always had to use the WAN port with a cable, so for that alone I thought why not give it a whirl.

 

[jksmurf]

Lol this thread is being taken over by smurfs …

 

[Yakkosmurf]

Further troubleshooting is providing some clarity on the issue.

I uploaded 25155 from the web GUI on my computer, and the problem occurred again with my wireless cameras not connecting. Next, I removed the Node from the AI Mesh, then re-added. My cameras would still not connect, so no change.

However, I brought a couple of other clients outside to where they'd only be able to see the node. The issue seems to be that clients that want a 5Ghz connection will not connect to the Node. Only those that are 2.4 Ghz only, or like my Android, that will connect to either. Anything I was able to connect would only do so at 2.4 Ghz.

I used the web GUI again to return to 25139, and everything is back to working as usual. My cameras and my phone instantly connected on 5 Ghz. So, the issue seems to be the 5Ghz band on the AX58U when it's being used a node...at least with my setup.

Hopefully this gives others insight if they experience the same or similar problems.

 

[Tech9]

Your brother smurf has basically the same router in signature and recently reported AiMesh working including GN Pro propagation to it.

 

[jksmurf]

Further troubleshooting is providing some clarity on the issue.

I uploaded 25155 from the web GUI on my computer, and the problem occurred again with my wireless cameras not connecting. Next, I removed the Node from the AI Mesh, then re-added. My cameras would still not connect, so no change.

However, I brought a couple of other clients outside to where they'd only be able to see the node. The issue seems to be that clients that want a 5Ghz connection will not connect to the Node. Only those that are 2.4 Ghz only, or like my Android, that will connect to either. Anything I was able to connect would only do so at 2.4 Ghz.

I used the web GUI again to return to 25139, and everything is back to working as usual. My cameras and my phone instantly connected on 5 Ghz. So, the issue seems to be the 5Ghz band on the AX58U when it's being used a node...at least with my setup.

Hopefully this gives others insight if they experience the same or similar problems.

Hmmmm, interesting observations. You didn’t mention your main router or what FW it was running, nor whether you use Guest Network or Guest Network Pro.

Being curious about the issue, I had a wee look at your various past posts and it seems you have (or have had) a RT-AX58U (Node), RT-AX3000 (Node), RT-AX98X (Node), GT-BE98 Pro (Main), ASUS RT-BE96U (node), two RT-AX55 and an RP-AX56, quite the collection, not sure if your using them all at once ;-). No Merlin.

The reason I had a look (sorry, not spying) was to see if you were using Guest Network Pro (GNP), the recent version of which seems to limit non-3006 based FW nodes to just ONE Wi-Fi Interface per band per device.

What I believe (my limited experience) this means is that if you have set up a VLAN Network in GNP with SSIDX, that NodeZ can only serve SSIDX with 2.4Ghz and 5Ghz and will not accept any other Networks. If you set up SSIDY and you elected to propagate only the 5Ghz band to that NodeZ, then NodeZ will still have the 2.4Ghz band free for SSIDX; but not the 5Ghz band. So where I was going with this was wondering if that’s what you’re experiencing, although I cannot account for the behaviour on the older FW, this is just a wild guess really.

 

[jksmurf]

Your brother smurf has basically the same router in signature and recently reported AiMesh working including GN Pro propagation to it.

Yes … but see my original post, GNP VLAN limitations mean I had to choose to either put both 2.4 and 5 on one SSID or put the 2.4 on one and the 5 on the other.

Guest VLAN is selected as 2.4/5; IoT as 2.4 only.

So the node serves IoT with 2.4 only and Guest with 5 only.

See the message on the screencap regarding the limit. It’s a poor way to represent what (I believe) is actually happening as the cross suggests that there is no connection, whereas it just means the band limit has been reached.

 

[OzarkEdge]

For another point of reference, I have the main WLANs and these custom Guest and IoT VLANs configured for both nodes, and all do broadcast as configured:

I've not reached any interface limit, but I suspect the limit is close.

OE

 

[jksmurf]

I couldn’t get the FW to load via the WebGui (it’s a wireless backhaul mesh node).

Right... well it's always been the case with Merlin FW at least that the RT-AX58U FW also always worked for the RT-AX3000. I have one of each, so it was a sort of two birds one stone happy FW download ... but I digress. It seems for this particular ASUS FW the RT-AX58U does not flash on the RT-AX3000. I tried wirelessly and wired...

So I checked the website and:

• The current RT-AX58U FW is Version 3.0.0.4.388_25155 95.05 MB 2025/03/17 whilst;
• The current RT-AX3000 FW is Version 3.0.0.4.388_25139 95.1 MB 2024/11/07

So I shall just stay on Merlin's 3004.388.9_Alpha1 for now. It works.

 

[jksmurf]

For another point of reference, I have the main WLANs and these custom Guest and IoT VLANs configured for both nodes, and all do broadcast as configured:

View attachment 64425

I've not reached any interface limit, but I suspect the limit is close.

OE

Thank you! But as visortgw noted in a separate thread, with Nodes on 3006, (given your sig) the limit is ... not yet known (maybe 5 Wifi Interfaces, same as VLANs?), whereas with nodes on 3004 ... meh, please don't make me go out and buy 3006-capable nodes ...

 

[visortgw]

Right... well it's always been the case with Merlin FW at least that the RT-AX58U FW also always worked for the RT-AX3000. I have one of each, so it was a sort of two birds one stone happy FW download ... but I digress. It seems for this particular ASUS FW the RT-AX58U does not flash on the RT-AX3000. I tried wirelessly and wired...

So I checked the website and:

• The current RT-AX58U FW is Version 3.0.0.4.388_25155 95.05 MB 2025/03/17 whilst;
• The current RT-AX3000 FW is Version 3.0.0.4.388_25139 95.1 MB 2024/11/07

So I shall just stay on Merlin's 3004.388.9_Alpha1 for now. It works.

https://www.asus.com/us/networking-.../rt-ax3000/helpdesk_bios?model2Name=RT-AX3000

Download Link

 

[Tech9]

whereas with nodes on 3004 ... meh, please don't make me go out and buy 3006-capable nodes ...

Not yet... only after you find the job you are looking for.

 

[jksmurf]

Not yet... only after you find the job you are looking for.

View attachment 64443

lol, Thank you