Early Access EAP223 V2, EAP225 V3&V3.2 EAP225 V4 EAP225-Outdoor V1&V3 Pre-release (Released on Mar 3rd, 2024)
This Article Applies to: EAP223 V2, EAP225 V3&V3.2, EAP225 V4, EAP225-Outdoor V1&V3 | Adapted to Omada SDN Controller v5.9
Update as of Apr 24, 2024:
Thank you all for your valuable feedback on the Beta firmware!
The official firmware of mentioned EAPs have been released, check the following link for details.
EAP223(EU)_V2_5.1.6 Build 20240313
EAP225(US)_V3_5.1.6 Build 20240313
EAP225(EU)_V3_5.1.6 Build 20240313
EAP225(EU)_V4_5.1.6 Build 20240313
EAP225-Outdoor(EU)_V3_5.1.6 Build 20240313
EAP225-Outdoor(US)_V1_5.1.6 Build 20240313
Release Notes
New Feature/Enhancement
1. Add support for IPv6.
2. Add support for Bonjour Service in Controller mode.
3. Add support for multiple Radius Servers.
4. Add support for diagnose tools function, including Ping, Traceroute, Packet Capture, Terminal, and Device Info.
Add support for LLDP (Link Layer Discovery Protocol).
5. Add support for ‘Lock to AP’.
6. Add support for reporting RADIUS username.
7. Add support for PMF in Controller mode.
8. Add support for SSID Rate Limit.
9. Add support for Multicast Management in Controller mode.
10. Add support for switch button on disable access to management page through HTTP in Standalone mode.
11. Add support for Mesh in standalone mode.
12. Optimize stability.
Bug Fixed
1. Fixed the bug of Band steering Feature working abnormally.
2. Fix the bug of supporting HTTP by default.
3. Fixed the bug that the HTTP process works abnormally when a post request does not carry any fields.
4. Fixed the bug that the UI cannot be automatically refreshed when delete MAC Groups in MAC Filter.
5. Fixed the issue where Terminal showed that, the target address was unreachable but was actually reachable when try ping before Traceroute ends.
6. Fixed the bug that 802.11r works abnormally when PPSK with RADIUS is enabled.
7. Fixed the bug that the client can still connect to the SSID when WPA-Persona and MAC-based authentication were set and the Radius server was offline.
8. Fixed the bug that the AP would reboot when the SSID enable ARP-to-Unicast Conversion and the clients associated with the SSID send ARP packets to each other in controller mode.
9. Fixed the bug that the destination IP address cannot be pinged normally when the ping packet size at Network Check is an odd number.
10. Fixed the bug that the Group Key Update Period value becomes default value when update the SSID in APP.
11. Fixed the bug of auto rebooting when using IPv6 URL Filtering.
12. Fixed the bug of duplicate Rogue AP entries.
13. Fixed the bug that mDNS packets with VLAN tags would cause the AP to reboot when only custom rules were configured for mDNS Bonjour rules.
14. Fixed the bug that the VLAN works abnormally when using PPSK with RADIUS.
15. Fixed the bug of stuck inter-process communication when number of clients performing the MAC Authentication at the same time.
16. Fixed the bug of device crash when switching WLAN Group.
17. Fixed some security issues.
Firmware Download
Attention:
1. Please be sure you have read the Beta Test Agreement before upgrading the Pre-release firmware!
2. Please ensure that you know which version (EU/US/CA/JP/EG) you shall use on your Omada EAP devices before you download the following EAP firmware.
EAP223(EU)_v2.0_5.1.3_Build20240222(Pre-release Version)
EAP225(EU)_v3.20_5.1.3_Build20240222(Pre-release Version)
EAP225(EU)_v4.0_5.1.3_Build20240222(Pre-release Version)
EAP225(US)_v3.0_5.1.3_Build20240222(Pre-release Version)
EAP225-Outdoor(EU)_v3.0_5.1.3_Build20240222(Pre-release Version)
EAP225-Outdoor(US)_v1.0_5.1.3_Build20240222(Pre-release Version)
Notes:
(1) The above firmware is applied to EAP223(EU) V2, EAP225(US) V3.0, EAP225(EU) V3.20, EAP225(EU) V4.0, EAP225-Outdoor(US) V1.0 and EAP225-Outdoor(EU) V3.0
(2) Your device’s configuration won’t be lost after upgrading.
(3) The above firmware is fully adapted to Omada SDN Controller v5.9.
Feedback
Any further feedback on the new firmware, please feel free to comment below or start a new thread from HERE.
To get better assistance, you may check Tips For Efficiently Reporting an Issue In The Community.
When reporting an issue, especially it's about firmware upgrade, it's suggested to include the following info:
- Management mode (Controller or Standalone)
- Device Model(s) and Hardware
- Device Firmware (previous and current)
Thank you in advance for your great cooperation and support.
Recommended Threads
Experience the Latest Omada EAP Firmware - Trial Available Here, Subscribe for Updates!
Current Available Solutions to Omada EAP Related Issues [Constantly Updated]
Get the Latest Omada SDN Controller Releases Here - Subscribe for Updates
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
After updating to 5.1.6, older devices and all of my smart lights would not connect except for newer devices. I opted to drop to 5.1.1, and all issues were resolved.
- Copy Link
- Report Inappropriate Content
@Hank21 After upgrading a Windows 10 PC crashed (blue screened) when connecting to the WiFi. Stop code: DPC WATCHDOG VIOLATION. it uses a TP-Link Archer T2u Plus wifi adapter. It does not make a difference if you're using the Microsoft supplied default driver, or using the driver supplied from the TP-Link website.
Initially I did not link this to the wifi, so I re-installed the machine with Windows 11 (clean install). This crashes seconds after connecting to the wifi, even in the windows 11 setup phase. When removing the WiFi adapter everything keeps working. After I've downgraded the firmware to 5.1.1 the PC then works flawlessly using this WiFi adapter.
- Copy Link
- Report Inappropriate Content
Jorgh wrote
@Hank21 After upgrading a Windows 10 PC crashed (blue screened) when connecting to the WiFi. Stop code: DPC WATCHDOG VIOLATION. it uses a TP-Link Archer T2u Plus wifi adapter. It does not make a difference if you're using the Microsoft supplied default driver, or using the driver supplied from the TP-Link website.
Initially I did not link this to the wifi, so I re-installed the machine with Windows 11 (clean install). This crashes seconds after connecting to the wifi, even in the windows 11 setup phase. When removing the WiFi adapter everything keeps working. After I've downgraded the firmware to 5.1.1 the PC then works flawlessly using this WiFi adapter.
Hi @Jorgh
May I know the model number and the controller version of your Omada devices? Please try to change the WPA mode to WPA2 NOT including the WPA3, and disable the PMF in SSID setting.
If you would rather, I've created a support ticket via your registered email address, and escalated it to our support engineer to look into the issue. The ticket ID is TKID240434613, please check your email box and ensure the support email is well received. Thanks!
- Copy Link
- Report Inappropriate Content
Omadauser200131 wrote
After updating to 5.1.6, older devices and all of my smart lights would not connect except for newer devices. I opted to drop to 5.1.1, and all issues were resolved.
Have you tried to change the WPA mode to WPA2 NOT including the WPA3, and disable the PMF in SSID setting? The PMF might be not compatible for some of the older wireless devices.
- Copy Link
- Report Inappropriate Content
Thanks for the recommendations, sir. Unfortunately, it still does not connect. I tried WPA-WPA2 mode, Auto to AES mode, and disabled PMF, but it still does not connect. My only alternative was to downgrade to the 5.1.1 version, which is the most stable for older devices.
- Copy Link
- Report Inappropriate Content
@Hank21 I'm using the software controller version 5.13.30.8. My devices are 2 x EAP225 V3 and 1 x EAP225-Outdoor V3.
I've disabled WPA 3 and PMF, for which I needed to deselect 6GHz otherwise WPA3 was the only option, this is in my case not an issue, because I've not got any 6GHz capable access points.
After upgrading to 5.1.6 the windows client using the TP-Link Archer T2u plus keeps working correctly. It was the only system on which I experienced these kind of issues.
The support e-mail ticket asked if I could make a settings backup available, If this is still needed, should I submit this by replying to the email? Or is there an other way to upload this backup. If this would be helpfull, I could upload the config, but I'm a bit concerned if any passwords are contained in the backup that could be exposed, could you clarify?
Kind regards,
Jorg
- Copy Link
- Report Inappropriate Content
Jorgh wrote
@Hank21 I'm using the software controller version 5.13.30.8. My devices are 2 x EAP225 V3 and 1 x EAP225-Outdoor V3.
I've disabled WPA 3 and PMF, for which I needed to deselect 6GHz otherwise WPA3 was the only option, this is in my case not an issue, because I've not got any 6GHz capable access points.
After upgrading to 5.1.6 the windows client using the TP-Link Archer T2u plus keeps working correctly. It was the only system on which I experienced these kind of issues.
The support e-mail ticket asked if I could make a settings backup available, If this is still needed, should I submit this by replying to the email? Or is there an other way to upload this backup. If this would be helpfull, I could upload the config, but I'm a bit concerned if any passwords are contained in the backup that could be exposed, could you clarify?
Kind regards,
Jorg
Hi @Jorgh
May I confirm it improves after you disabled the WPA and PMF? Generally the support will need your help to provide the back up file when they want to re-duplicate the scenario. There is an option as back up settings only, which will not contain any data of your controller. If you still encounter the same issue, you can reply the email with the back up file.
Thanks for understanding.
- Copy Link
- Report Inappropriate Content
Omadauser200131 wrote
Thanks for the recommendations, sir. Unfortunately, it still does not connect. I tried WPA-WPA2 mode, Auto to AES mode, and disabled PMF, but it still does not connect. My only alternative was to downgrade to the 5.1.1 version, which is the most stable for older devices.
May I confirm what are the model of your wireless devices? And could you share the configuration details about your SSID?
Besides, I've created a support ticket via your registered email address, and escalated it to our support engineer to look into the issue. The ticket ID is TKID240437236, please check your email box and ensure the support email is well received. Thanks.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 4066
Replies: 22
Voters 0
No one has voted for it yet.