[Release Note] Zyxel Access Point - V7.10(ACGG.1)C0 firmware has been released
Access Points Firmware Release Note
January 2025
Overview
This document provides firmware release information on Zyxel Access Points platforms, introduce new Access Points, new features and enhancements, bug fix, known issues and workarounds information for Release V7.10 Patch 1 C0.
Supported Platforms
(Click Hyperlink to download the firmware directly)
WiFi 7 model(s):
Zyxel WBE660S - V7.10(ACGG.1)C0
Zyxel WBE630S - V7.10(ACLW.1)C0
Zyxel WBE530 - V7.10(ACLE.1)C0
Zyxel WBE510D - V7.10(ACLX.1)C0
Zyxel NWA210BE - V7.10(ACLY.1)C0
Zyxel NWA110BE - V7.10(ACLZ.1)C0
Zyxel NWA130BE - V7.10(ACIL.1)C0
WiFi 6E model(s):
Zyxel WAX640S-6E - V7.10(ACCM.1)C0
Zyxel WAX620D-6E - V7.10(ACCN.1)C0
Zyxel NWA220AX-6E - V7.10(ACCO.1)C0
WiFi 6 model(s):
Zyxel WAX655E - V7.10(ACDO.1)C0
Zyxel WAX650S - V7.10(ABRM.1)C0
Zyxel WAX630S - V7.10(ABZD.1)C0
Zyxel WAX610D - V7.10(ABTE.1)C0
Zyxel WAX510D - V7.10(ABTF.1)C0
Zyxel WAX300H - V7.10(ACHF.1)C0
Zyxel NWA210AX - V7.10(ABTD.1)C0
Zyxel NWA110AX - V7.10(ABTG.1)C0
Zyxel NWA90AX PRO - V7.10(ACGF.1)C0
Zyxel NWA50AX PRO - V7.10(ACGE.1)C0
Zyxel NWA50AX - V7.10(ABYW.1)C0
Zyxel NWA55AXE - V7.10(ABZL.1)C0
Zyxel NWA90AX - V7.10(ACCV.1)C0
New Features and Enhancements
1. Captive Portal now supports authentication utilizing Microsoft Entra ID on Nebula Control Center.
2. Supports Wi-Fi 7 Smart Mesh using MLO technology on Nebula Control Center.
Bug Fix
Bug fix | C | M | S |
1. [eITS: 240700214] [Symptom] SSID schedule function not working correctly on NWA130BE. | V | - | - |
2. [eITS: 240800279, 240800576] [Symptom] STA cannot connect to the network, with the event log showing 'key handshake fail. | V | - | - |
3. [eITS: 240800663, 240901933, 241000202, 241000532, and 241101053] [Symptom] NWA50AX, NWA90AX, NWA55AXE, the 2.4GHz radio does not initialize properly when the AP boots up. | V | - | V |
4. [eITS: 240800619] [Symptom] CAPWAP uses broadcast instead of option 138 for AC-IP. | - | - | V |
5. [eITS: 240900432] [Symptom] Reboot by hardware watchdog. | V | V | V |
6. [eITS: 240900715] [Symptom] After an AP reboot and reset to default, the AP fails to apply the Bug fix Cloud Managed Standalone correct SSID profile, causing configuration errors and VAP failure. | V | - | - |
7. [eITS: 240901703, 240900146, 240701656, 241001953, and 241101572] [Symptom] WAX640S- 6E, WAX655E, device kernel panic reboot. | V | V | V |
8. [eITS: 240801045] [Symptom] APs could not connect to the controller after switching Device HA roles. | - | - | V |
9. [eITS: 240801694] [Symptom] Layer 2 isolation not working as expected on standalone AP when using Dynamic VLANs. | - | - | V |
10. [eITS: 241000253] [Symptom] Users connecting to an SSID assigned a dynamic VLAN by the server experience a performance drop when accessing WAN internet. | V | V | V |
11. [eITS: 241001339] [Symptom] MLO SSID is not visible. | V | - | - |
12. [eITS: 240901360] [Symptom] The accounting feature is not working correctly. | - | - | V |
13. [eITS: 241000005] [Symptom] The repeater AP experiences frequent disconnections when broadcasting de-auth packets in the environment. | V | - | - |
14. [eITS: 241100885] [Symptom] The NWA130BE experiences a kernel panic and reboots. | V | V | V |
15. [eITS: 241100826] [Symptom] AP broadcast default SSID even added to Nebula. | V | - | - |
16. [eITS: 241200366 ] [Symptom] When Wi-Fi 7 stations connect to a WPA3 SSID, they do not use 802.11be mode. | V | V | V |
Known Issue
Known Issue | C | M | S |
1. [SPRID: 240820168] [Symptom] When enabling MLO, the WPA-Enterprise security mode may occasionally fail to convert to WPA | V | - | - |
2. [SPRID: 240913082] [Symptom] Stations cannot authenticate when an SSID is configured with MLO (4G+5G bands) and the security mode is set to WPA3 with MAC Authentication via RADIUS. | V | - | - |
3. [SPRID: 241202036] [Symptom] When the Repeater AP reaches the Wireless Health threshold, the non-mesh bands will not act. | V | - | - |
4. [SPRID: 241203097] [Symptom] When the Mesh topology consists of a non-supported MLO Root combined with MLO Repeater Hop1 and Hop2, it may affect the Repeater's downlink and cause issues with the service VAP lacking MLO functionality. | V | - | - |
5. [SPRID: 241216264] [Symptom] When the WAC5302D-Sv2 model is used as the Root in a Mesh setup, and Wi-Fi 7 series models with firmware versions 00 & 10 are used as Repeaters, the Mesh connection cannot be established. | V | - | - |
6. [SPRID: 241219349] [Symptom] The 'By Traffic Level' option incorrectly appears in the Load Balancing section of the GUI. | - | - | V |
7. [SPRID: 241219350] [Symptom] The wireless monitoring data exhibits abnormal behavior. | V | - | - |
8. [SPRID: 250113159] [Symptom] The MLO (Multi-Link Operation) on SSID and smart mesh MLO feature are malfunctioning on the following models: NWA110BE, NWA210BE, WBE510D, and WBE630S. | V | - | - |
Limitation of Settings
N/A
Comments
-
Anyone get MLO to work on this release? If so what are you settings?
0 -
Yes, MLO works seems to work fine (after a few tests). Only switch MLO on and follow the rules for your client (latest driver, Windows Update 24H2 etc).
0
Categories
- All Categories
- 415 Beta Program
- 2.4K Nebula
- 151 Nebula Ideas
- 98 Nebula Status and Incidents
- 5.7K Security
- 277 USG FLEX H Series
- 277 Security Ideas
- 1.4K Switch
- 74 Switch Ideas
- 1.1K Wireless
- 42 Wireless Ideas
- 6.4K Consumer Product
- 250 Service & License
- 395 News and Release
- 85 Security Advisories
- 29 Education Center
- 10 [Campaign] Zyxel Network Detective
- 3.6K FAQ
- 34 Documents
- 34 Nebula Monthly Express
- 85 About Community
- 75 Security Highlight