Release GT-AXE-16000 Firmware Version: 3.0.0.4.388_24403

[cc666]

I hit my update button manually and low and behold this appeared GT-AXE-16000 Firmware Version:3.0.0.4.388_24403.

Previous version was GT-AXE16000_3.0.0.4_388_24374.

Router updated and is now on a later release than whats posted on the website. I assume its coming.

CC

 

[fruitcornbread]

ASUS ROG Rapture GT-AXE16000 Firmware version 3.0.0.4.388_24403
Version 3.0.0.4.388_24403
55.51 MB
2024/11/13

1. Strengthened input validation and data processing workflows to further protect information security.
2. Enhanced AiCloud password protection mechanisms, safeguarding against unauthorized access attempts.
3. Enhanced device security through improved buffer handling in connection features.
4. Refined data handling processes, ensuring secure and accurate information management.
5. Enhanced file access control mechanisms, promoting a more secure operating environment.
6. Strengthened certificate protection, providing enhanced data security.

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

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

 

[aublumberg]

ASUS must have been busy in recent weeks getting these security fixes rolled out across many devices ...

 

[cc666]

ASUS ROG Rapture GT-AXE16000 Firmware version 3.0.0.4.388_24403
Version 3.0.0.4.388_24403
55.51 MB
2024/11/13

1. Strengthened input validation and data processing workflows to further protect information security.
2. Enhanced AiCloud password protection mechanisms, safeguarding against unauthorized access attempts.
3. Enhanced device security through improved buffer handling in connection features.
4. Refined data handling processes, ensuring secure and accurate information management.
5. Enhanced file access control mechanisms, promoting a more secure operating environment.
6. Strengthened certificate protection, providing enhanced data security.

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

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

Where did you get this info? Whern I check the Asus sites its not listed.
Can you provide the URL to the D/L SITE?

CC

 

[fruitcornbread]

Where did you get this info? Whern I check the Asus sites its not listed.
Can you provide the URL to the D/L SITE?

CC

ROG Rapture GT-AXE16000 | Networking | ROG Canada

Quad-band WiFi 6E gaming router, new 6 GHz band, dual 10G ports, 2.5G WAN port, dual WAN, AiMesh support, VPN Fusion, Triple-level game acceleration and free network security

rog.asus.com

 

[cc666]

ROG Rapture GT-AXE16000 | Networking | ROG Canada

Quad-band WiFi 6E gaming router, new 6 GHz band, dual 10G ports, 2.5G WAN port, dual WAN, AiMesh support, VPN Fusion, Triple-level game acceleration and free network security

rog.asus.com

Interesting, the US site does not have this firmware listed

CC

 

[tgd]

Everything Ok for the main unit ... problem with the node ...(both are GT-AXE16000)
Exactly same problem as previous versions.
Node loses wifi when in Auto mode. Everything works properly when in ethernet mode.
Rolled back to version 23012 the node.

 

[drabisan]

Everything Ok for the main unit ... problem with the node ...(both are GT-AXE16000)
Exactly same problem as previous versions.
Node loses wifi when in Auto mode. Everything works properly when in ethernet mode.
Rolled back to version 23012 the node.

Not sure I'm following...you're talking about "Backhaul Connection Priority" on auto?
And you also have an ethernet link between router and node? I would assume you don't have "Ethernet Backhaul Mode" on, cause that will only use ethernet link for backhaul.

If you have a cable between router and note, why not using only "Ethernet Backhaul Mode"? Chances for that link to fail are minimal and a 1G ethernet link may not be the fastest, but it will be much stable. With a clear predictible performance. If that cable is 10G...no reason whatsoever to instruct the devices to rely on wireless backhaul.

I don't have an ethernet link, unfortunatelly, so my 2 AXE16000 are using a wireless backhaul. But I have absolutely no problems with it. I have this setup for almost 7 months now.

 

[tgd]

Not sure I'm following...you're talking about "Backhaul Connection Priority" on auto?
And you also have an ethernet link between router and node? I would assume you don't have "Ethernet Backhaul Mode" on, cause that will only use ethernet link for backhaul.

If you have a cable between router and note, why not using only "Ethernet Backhaul Mode"? Chances for that link to fail are minimal and a 1G ethernet link may not be the fastest, but it will be much stable. With a clear predictible performance. If that cable is 10G...no reason whatsoever to instruct the devices to rely on wireless backhaul.

I don't have an ethernet link, unfortunatelly, so my 2 AXE16000 are using a wireless backhaul. But I have absolutely no problems with it. I have this setup for almost 7 months now.

You are absolutely right ... this is what I am talking about ... I need it in auto because I have other nodes that connect wirelessly.
I have tried disconnecting the ethernet cable with the last firmware and as you said it works ok then but when I connect the ethernet cable and have it on auto I loose wifi on the node. Only 2.4 appears every few minutes and disappears again. When I roll back to 23012 on the node everything works Ok. All versions after 23012 have the problem.

One other thing that I found out is that exactly the same problem exists on another node I have ( ET12 pro ) that is connected through ethernet. Exactly the same behavior... Again when connected with ethernet in auto backhaul mode I loose wifi on the node but when on ethernet mode everything works ok with last version. On this one the correct version that I rolled back is 23013 and all versions after that have the problem.

So I believe that the problem with aimesh affects more routers and not GT-AXE16000.

 

[jzchen]

All my routers are wired. Unfortunately I have to say that as a node, even with AiMesh Settings Ethernet Backhaul Mode toggled ON, it is not quite stable.

 

[drabisan]

You are absolutely right ... this is what I am talking about ... I need it in auto because I have other nodes that connect wirelessly.
I have tried disconnecting the ethernet cable with the last firmware and as you said it works ok then but when I connect the ethernet cable and have it on auto I loose wifi on the node. Only 2.4 appears every few minutes and disappears again. When I roll back to 23012 on the node everything works Ok. All versions after 23012 have the problem.

One other thing that I found out is that exactly the same problem exists on another node I have ( ET12 pro ) that is connected through ethernet. Exactly the same behavior... Again when connected with ethernet in auto backhaul mode I loose wifi on the node but when on ethernet mode everything works ok with last version. On this one the correct version that I rolled back is 23013 and all versions after that have the problem.

So I believe that the problem with aimesh affects more routers and not GT-AXE16000.

That may require a ticket to Asus.
I found another "weirdness" in the last 2 releases: if I select "use as both backhaul and fronthaul connection" on 5GHz radio#2, I can see 2 BSSIDs broadcasted by the same radio.
That makes no sense in my mind - it's the same radio, same channel, same resources. Why not share the same SSID as it was before?
Factory reset makes no difference, as soon as I select "use as both backhaul and fronthaul connection", 2 BSSIDs.

I tried opening a ticket but Chrome just waits and never actually submit that form. I'll have to try with a different browser.

 

[tgd]

That may require a ticket to Asus.
I found another "weirdness" in the last 2 releases: if I select "use as both backhaul and fronthaul connection" on 5GHz radio#2, I can see 2 BSSIDs broadcasted by the same radio.
That makes no sense in my mind - it's the same radio, same channel, same resources. Why not share the same SSID as it was before?
Factory reset makes no difference, as soon as I select "use as both backhaul and fronthaul connection", 2 BSSIDs.

I tried opening a ticket but Chrome just waits and never actually submit that form. I'll have to try with a different browser.

I have already opened a case through customer service for this behavior months ago when the previous version was released (exactly same problem) but there is no answer yet.