Release AX88U Pro Firmware version 3.0.0.6.102_33340 (2024/11/12)

[Dedel66]

A firmware check via GUI showed that 3.0.0.6.102_33340-g5c167ca_345-gf3514 is available. But it is not yet available on the ASUS website.
Unfortunately I don't have time to test it in detail, but at first glance everything works.

 

[bennor]

Direct download link for 3.0.0.6.102_33340:
https://dlcdnets.asus.com/pub/ASUS/wireless/RT-AX88U%20Pro/FW_RT_AX88U_PRO_300610233340.zip?model=RT-AX88U%20Pro

 

[gammern]

Firmware version 3.0.0.6_102_33340-g5c167ca_345-gf3514
- Release Note -

Bug Fixes and Enhancements:
- Fixed display issues on the AiMesh page.

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

 

[Paliv]

So far so good working from home for the last few hours.

 

[OzarkEdge]

Another observation after installing the last two releases 33338 and then this 33340 to fix the 33338 webUI corruption...

I noticed my 5.0 wireless backhaul turn ON in the Wireless Log (AX; NSS 4 between two 4-stream nodes) despite having a working MoCA wired backhaul. Toggling Ethernet Backhaul Mode ON and then OFF clears this wireless backhaul connection from the log. I'm left wondering why installing the firmware (without and subsequently with a Hard Reset) turns ON the wireless backhaul, and if it would have turned OFF in due time without my intervention. This 'wireless backhaul turning ON' issue did not present with previous firmware upgrades.

Does anyone have i) Ethernet Backhaul Mode disabled to permit wireless backhaul failover; ii) a stable, working wired backhaul; AND iii) a wireless backhaul connection listed in the Wireless Log when it should not be ON? If so, does toggling EBM clear this wireless backhaul entry from the log?

OE

 

[bbunge]

Another observation after installing the last two releases 33338 and then this 33340 to fix the 33338 webUI corruption...

I noticed my 5.0 wireless backhaul turn ON in the Wireless Log (AX; NSS 4 between two 4-stream nodes) despite having a working MoCA wired backhaul. Toggling Ethernet Backhaul Mode ON and then OFF clears this wireless backhaul connection from the log. I'm left wondering why installing the firmware (without and subsequently with a Hard Reset) turns ON the wireless backhaul, and if it would have turned OFF in due time without my intervention. This 'wireless backhaul turning ON' issue did not present with previous firmware upgrades.

Does anyone have i) Ethernet Backhaul Mode disabled to permit wireless backhaul failover; ii) a stable, working wired backhaul; AND iii) a wireless backhaul connection listed in the Wireless Log when it should not be ON? If so, does toggling EBM clear this wireless backhaul entry from the log?

OE

Are you using the 2.5 GB ports for Ethernet backhaul? I have had the 2.5 GB backhaul fail between my AX86U Pro and AX86U node. Switched /o a 1 GB port and it is stable.

 

[OzarkEdge]

Are you using the 2.5 GB ports for Ethernet backhaul? I have had the 2.5 GB backhaul fail between my AX86U Pro and AX86U node. Switched /o a 1 GB port and it is stable.

Yes, using the 2.5GbE ports with MoCA2.5 between Pro models... have not noticed this link having any trouble... it is still the reported AiMesh backhaul while the wireless backhaul is errantly ON in the log.

OE