Release ASUS ROG Rapture GT-AXE16000 Firmware version 3.0.0.4.388_24374 (2024/09/27)

[visortgw]

Is there a difference between the official GT-AXE16000 version 3.0.0.4.388_24374 and the Merlin GT-AXE16000_3004_388.8_2?

Merlin's release is based upon GPL 24353. Look at the changelog for the summary of what changed in Asus' latest version.

 

[RMerlin]

Is there a difference between the official GT-AXE16000 version 3.0.0.4.388_24374 and the Merlin GT-AXE16000_3004_388.8_2?

Yes. One is stock Asuswrt, and the other is Asuswrt-Merlin with thousands of code changes over the stock one.

Bottom line, you cannot compare them.

 

[drabisan]

Anybody else having GT-AXE16000 as a node and have tested this firmware ?

Both router and node I have are AXE16000. No problems whatsoever.

 

[tgd]

Every time I try to upgrade the node I lose wifi on the node ... Router is fine with last version ... node is kept 2 versions backwards ... both last 2 versions with the same problem on the node ... Any suggestions ?

 

[i5Js]

Hello all,

I have an GT-AXE16000 as main router using the 3.0.0.4.388_24374 and an GT-AXE1000 as mesh node using 3.0.0.4.388_23849. The backhaul mode is ethernet

I see all my devices can only connect to the GT-AXE11000 to 802.11n and 216Mbps. I have removed it from the mesh network, and setup it as a stand alone, and it works as expected, 802.11AX and up to 1300 MBps.

I have cleaned the settings, WPS reset method too, but nothing works, after adding it back to my mesh network, it happens again.

is there known issues about this router and mesh networks?

Thanks in advanced,


EDIT: It seems I have fixed it disabling the Enable Smart Connect option. Now the devices are "free" to connect to any band.

 

[tgd]

Hello again,
Something is definitely wrong in this version in aimesh ( exactly the same problem as last version ) ... I have managed to find a solution in order to have wifi on the 2nd GT-AXE16000 (node) ... I enabled ethernet backhaul mode and everything seems to be working well ... 2 versions ago you could leave it in auto and everything was working well ...
This is not a working model if you have another node connected through wifi.
Another problem I have found in this version is that on the 2,4 band you can not check and save ''Auto select channel including channel 12, 13''.
After applying the changes it reappears unchecked.
So I think I will keep the router on this version and revert back again the node to 23012 waiting for the next version.

 

[drabisan]

It may be the 2 routers are seeing eachother at over 1G on wireless?
I've seen that long time ago, when I had the node moved from AC to AX. That was the reason I didn't used auto - it was switching to a wireless backhaul and I didn't want to share 5GHz radio between clients and backhaul link.

Auto does provide redundancy in case ethernet link goes down. But if you want all radios to be available, forcing ethernet only backhaul may be the single good idea.

However, you should reach out to Asus with this question. With a bit of luck you may find a tech willing to provide a decent explanation.

I'm not arguing here the question you're asking is not valid. It's actually a great question! It should be a simple logic with decent documentation. But it isn't!
You'd be surprised how weird it becomes when the only option is to have wireless backhaul. I configured 5GHz#2 radio as a dedicated backhaul. But often I found my 2 16000 using 6GHz radio as a backhaul. As much as I would love a more predictible behavior for me the only important aspect is stability. And it's super solid and I can easily get super high speeds between devices connected to router and node.

 

[i5Js]

I've found another ridiculous behaviour.I started to have the same issue with the 2.4GHz band and GT-AXE11000; my change was set a fixed ip to the node. When I revert it, it started to work fine. I tried several time, and always had the issue, when the node has a fixed ip.

 

[nthezone]

Version 3.0.0.4.388_24374
55.4 MB
2024/09/27

1. Optimized memory management mechanisms, improving system efficiency and stability.
2. Strengthened input validation and data processing workflows, further protecting your information security.
3. Improved web rendering engine, enhancing browsing experience and security.
4. Enhanced security of system command processing to guard against potential malicious operations.
5. Perfected JavaScript-related security mechanisms, offering a more secure web interaction environment.

Please unzip the firmware file, and then verify the checksum.
SHA256: 8722f036d092ee2dd98c9eef4f961a3bdd20e4248d9bace6d2161bea0bf004de

Download: https://dlcdnets.asus.com/pub/ASUS/wireless/ROG Rapture GT-AXE16000/FW_GT_AXE16000_300438824374.zip?model=ROG Rapture GT-AXE16000

VPN Bug
axe16000 new firmware broke VPN Director on ASUS ROG Rapture GT-AXE16000 Firmware version 3.0.0.4.388_24374
i can no longer get vpn tunnel to work it blocks all traffic , had to downgrade back to 3004.388.7_0_rog
VPN Director Tunnel works like normal now

 

[visortgw]

VPN Bug
axe16000 new firmware broke VPN Director on ASUS ROG Rapture GT-AXE16000 Firmware version 3.0.0.4.388_24374
i can no longer get vpn tunnel to work it blocks all traffic , had to downgrade back to 3004.388.7_0_rog
VPN Director Tunnel works like normal now

You installed Asus stock firmware (non-Merlin). VPN Director is a Merlin added feature. Try the latest Merlin firmware -- 3004.388.8_2.