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 ASUS RT-AX86U Pro Firmware version 3.0.0.6.102_34349 (2025/03/17)

bennor

Part of the Furniture
ASUS RT-AX86U Pro Firmware version 3.0.0.6.102_34349
https://www.asus.com/networking-iot...6u-pro/helpdesk_bios/?model2Name=RT-AX86U-Pro

Version 3.0.0.6.102_34349
58.18 MB
2025/03/17
SHA-256 :D4F725FFB67997CFB443D641A174C67EB6223A66215D6FFDBD92FECF5C77849F
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.

Download: https://dlcdnets.asus.com/pub/ASUS/...AX86U_PRO_300610234349.zip?model=RT-AX86U Pro
 
Four months to go from 34336 to 34349 feels like a big nothingburger to me. Maybe it fixes my node WLAN leaking the WPS protocol, but I doubt it contains the SDN change from Guest Network Pro to Network.

OE
 
Last edited:
feels like a big nothingburger to me

I believe Asus updated all the routers across the board even the ones on EoL list mostly because of:

1) security patch
2) changes in AiMesh

Network configuration is eventually coming after 37xxx update. At least this is when it happened on BE-class devices.
 
Upgrade early this morning via the Android Asus app. Best news is there was no harm done! Did not notice any new features or changes to the GUI.
 
Weird they didn't update the GT-AX6000
 
Both my router and node auto updated over night. So far so good.
 
Well, there are some issues...
As usual I did some "testing" of the WIFI settings. Normally, I run 20 MHz Auto Channel on 2.4 GHz and 80 MHz auto channel no DFS on 5 GHz with Ethernet backhaul to 1 Gb ports. I switched both bands back to the Asus WIFI defaults and rebooted the mesh system. WIFI clients would not connect to the node although the node seemed to be broadcasting. I switched to 2.5 Gb Ethernet backhaul which worked for a couple of minutes then switched to 5 Ghz WIFI backhaul and the 2.4 Ghz clients would connect to the node sometimes. Disabled DFS with no change. Made several other changes to the WIFI with unsat results. Switching the 5 GHz back to 80 MHz works. Settings I am on now that are working: 2.4 GHz @ 20 MHz channel 6, 5GHz @20-40-80-160 MHz channel 36.
I do not feel I need to revert to the prior firmware as the mesh system is working and there are no complaints from the family. Besides, Asus would bug me that there is an upgrade. As this is complicated I do not exactly know what to report to Asus.
 
Well, there are some issues...
As usual I did some "testing" of the WIFI settings. Normally, I run 20 MHz Auto Channel on 2.4 GHz and 80 MHz auto channel no DFS on 5 GHz with Ethernet backhaul to 1 Gb ports. I switched both bands back to the Asus WIFI defaults and rebooted the mesh system. WIFI clients would not connect to the node although the node seemed to be broadcasting. I switched to 2.5 Gb Ethernet backhaul which worked for a couple of minutes then switched to 5 Ghz WIFI backhaul and the 2.4 Ghz clients would connect to the node sometimes. Disabled DFS with no change. Made several other changes to the WIFI with unsat results. Switching the 5 GHz back to 80 MHz works. Settings I am on now that are working: 2.4 GHz @ 20 MHz channel 6, 5GHz @20-40-80-160 MHz channel 36.
I do not feel I need to revert to the prior firmware as the mesh system is working and there are no complaints from the family. Besides, Asus would bug me that there is an upgrade. As this is complicated I do not exactly know what to report to Asus.

I'm surprised your first (and easiest) move wasn't to remove/reset the node and re-add it, as I reported yesterday. My next move (and before reporting anything to ASUS) would have been to re-commission the network from scratch, but that was not necessary.

OE
 
I'm surprised your first (and easiest) move wasn't to remove/reset the node and re-add it, as I reported yesterday. My next move (and before reporting anything to ASUS) would have been to re-commission the network from scratch, but that was not necessary.

OE
Oh, I forgot to mentioned I did that several times. Power cycled several times, too. Even did a Hard Factory Reset of the node. Made no difference
 
Oh, I forgot to mentioned I did that several times. Power cycled several times, too. Even did a Hard Factory Reset of the node. Made no difference

One more possibility... it seems your AX86U node has not yet received the current round of firmware update... I would upload that when it is released and re-add that node.

OE
 
One more possibility... it seems your AX86U node has not yet received the current round of firmware update... I would upload that when it is released and re-add that node.

OE
Am waiting with baited breath for the AX86U update...
 
Not sure what is happening to RT-AX86U, but it was once the most recommended and quite popular around, then become the most affected by the recent malware and now has the longest delays with firmware upgrades. It was a good router... 🤷‍♂️
 
Not sure what is happening to RT-AX86U, but it was once the most recommended and quite popular around, then become the most affected by the recent malware and now has the longest delays with firmware upgrades. It was a good router... 🤷‍♂️
Yeah it's weird
 
Not sure what is happening to RT-AX86U, but it was once the most recommended and quite popular around, then become the most affected by the recent malware and now has the longest delays with firmware upgrades. It was a good router... 🤷‍♂️
I've had mine for 5 years, it's been rock solid. I also don't understand why Asus leaves the AX86U for last, it was\is such a popular model.
 
I also don't understand why Asus leaves the AX86U for last

Most likely because this model was sort of primary target of malware, some routers got damaged, Asus managed to come up with firmware reverting the damages, it took extra time and now some of the routers are not exactly in the same state as they left the factory. No wonder if the next firmware update for this model is also "special edition" taking into account the chain of events.
 

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