Early Access EAP Beta Firmware for Omada SDN Controller v5.9 (Updated on May 6th, 2024)- [Thread Closed]
This Article Applies to
EAP223(EU) V2.0
EAP225(US) V3.0
EAP225(EU) V3.20
EAP225(EU) V4.0
EAP225-Outdoor(US) V1.0
EAP225-Outdoor(EU) V3.0
EAP230-Wall(EU) V1.0
EAP235-Wall(EU/US) V1.0
EAP223(EU/US) V1.0
...
EAP610 v1.0 /v1.6 (EU/US/CA)
EAP610 v2.0 /v2.6 /v2.20 /v2.26 (EU/US/CA/JP/EG)
EAP610 v3.0 (EU/US/CA/JP/EG)
EAP613 v1.0 /v1.6 (EU/US/JP)
EAP615-Wall v1.0 /v1.6 (EU/US/CA/JP/EG)
EAP650-Wall v1.0 (EU/US)
EAP655-Wall v1.0 /v1.6 (EU/US/CA/JP)
EAP650 v1.0 /v1.6 /v1.20 /v1.26 (EU/US/CA/JP)
EAP653 v1.0 /v1.6 (EU/US/CA/JP)
EAP670 v1.0 /v1.6 /v1.20 /v1.26 (EU/US/CA/JP)
EAP620HD v2.0 (CA)
EAP620HD v2.0 /v2.6 /v2.8 (EU/US/JP)
EAP620HD v3.0 /v3.6 /v3.20 /v3.26 (EU/US/CA/JP/EG)
EAP610-Outdoor v1.0 /v1.6 /v1.20 /v1.26 (EU/US/CA/JP/EG)EAP650-Outdoor v1.0 /v1.6 (EU/US/CA/JP/EG)
...
*More EAP Firmware for Omada SDN Controller v5.9 will be provided soon, stay tuned!
Release Notes
New Feature/Enhancement
1. Added support for the following new features which were added on Omada Controller v5.9.
- Added support for shared bandwidth while using the "SSID Rate Limit" feature.
- Added support for IPv6 ACL/URL Filtering/Guest Network.
- Added support for IPv6 dial-up/Client address acquisition/MLD to unicast.
- Added support for LLDP (Link Layer Discovery Protocol).
- Added support for the Network Check.
Select an Omada EAP and perform a ping or traceroute test to check the network connectivity.
- Added support for Packet Capture.
Select an Omada EAP, set the capture filter, and perform a packet capture for troubleshooting. Omada Controller uses TCP port 29815 to download the packets.
- Added support for Terminal.
Select an Omada device (EAP or Switch), open Terminal, and then you can execute CLI or Shell commands. Omada Controller uses TCP port 29816 to create remote control terminall sessions with the devices.
- Added support for downloading device info.
Omada Controller uses TCP port 29815 to receive the information from the devices. You can download a device's info by opening its Properties window, going to Config > Manage Device, and clicking Download. This feature helps to confirm the operational status of Omada devices and to perform troubleshooting.
- Added support for the "Lock To AP" feature.
Open a client's Properties window, go to Config, enable the function, and select one or multiple EAPs, then the client will be locked to the selected EAPs. This feature helps prevent a static client from roaming frequently between multiple EAPs.
- Added support for RADIUS username report.
When the SSID is configured with WPA-Enterprise authentication, the username used by the wireless client will be displayed in the 802.1X Authentication column of the Clients page.
2. Added support for some remaining new features on some EAP devices, which were added on controller v5.8 and earlier.
-
EAP610 v3, EAP613 v1
-
Added support for PPSK function in Controller mode.
-
Added support for Band Steering.
-
Added support for 802.11r fast roaming protocol.
-
Added support for Multiple RADIUS server.
-
-
EAP655-Wall v1
- Added support for PPSK function in Controller mode.
- Added support for 802.11r fast roaming protocol.
- Added support for Multiple RADIUS server.
- Added support for Multicast/Broadcast Management.
- EAP650 v1, EAP670 v1
- Added support for Multiple RADIUS server.
- Added support for Multicast/Broadcast Management.
- EAP615-Wall v1
- Added support for Band Steering.
- Added support for 802.11r fast roaming protocol.
- EAP650-Outdoor v1
- Added support for RE mode in Standalone. Please refer to FAQ3646 to learn how to configure it.
- EAP650-Wall v1, EAP610 v2
- Added support for PPSK function in Controller mode.
Bug Fixed
Fixed some issues that may occur on some EAP devices.
- EAP655-Wall v1
- Fixed abnormal IPv6 address acquisition for clients when enables Dynamic VLAN.
- EAP650 v1, EAP670 v1
- Fixed abnormal IPv6 address acquisition for clients when enables Dynamic VLAN.
- Fixed the disconnected issue caused by weather radar channels.
- EAP610 v3, EAP613 v1
- Fixed the issue that the Bonjour service may cause the AP to restart under certain circumstances.
- Fixed the issue that the Mesh AP may fail to return to the Connected state after a reboot in some cases.
- Fixed the issue that the SNMP may fail to get the correct number of clients with OID 1.3.6.1.4.1.11863.10.1.1.1.0.
Firmware Download
Before the Upgrade
(1) Please be sure you have read the Beta Test Agreement before upgrading the Beta firmware!
(2) You may follow the following guide to upgrade your Omada EAP devices. How to Upgrade/Downgrade Omada EAPs.
Firmware Download Link
EAP223 V2, EAP225 V3&V3.2, EAP225 V4, EAP225-Outdoor V1&V3 Pre-release
EAP230-Wall V1, EAP235-Wall V1 3.2.0_Build 20240103 Pre-release
EAP223 V1_1.3.0_Build 20240131 Pre-release
EAP610(EU)_V1_1.1.2 Build 20230922
EAP610(EU)_V2_1.1.4 Build 20230922
EAP610(EU)_V3_1.4.3 Build 20231215
EAP613(EU)_V1_1.4.3 Build 20231215
EAP615-Wall(EU)_V1_1.2.3 Build 20231215
EAP650-Wall(EU)_V1_1.1.4 Build 20231208
EAP655-Wall(EU)_V1_1.2.4 Build 20231208
EAP653(EU)_V1_1.0.9 Build 20230814
EAP650(EU)_V1_1.0.13 Build 20240131
EAP670(EU)_V1_1.0.12 Build 20230922
EAP620 HD(EU)_V2_1.1.2 Build 20230922
EAP620 HD(EU)_V3_1.2.3 Build 20230922
EAP610-Outdoor(EU)_V1_1.2.3 Build 20230922
EAP650-Outdoor(EU)_V1_1.1.3 Build 20240131
Additional Information
All feedback is welcome, including letting us know about successful device upgrades.
If somehow you encounter an issue during or after the EAP upgrade, it's suggested to contact us with the following info:
- Omada Controller version
- Device Firmware version with Build number (previous and current)
If your EAP gets bricked during the firmware upgrade, you may follow the guide below to recover the firmware.
How to use the Recovery Mode to recover the firmware for EAP
Update Log
May 6, 2024:
Update to provide the Pre-Released version for the following EAPs:
EAP650-Wall V2_1.0.2, EAP650 V2_1.1.0 Pre-release (Released on May 6th, 2024)
Mar 13, 2024:
Update to provide the Pre-Released version for the following EAPs:
EAP223 V2, EAP225 V3&V3.2, EAP225 V4, EAP225-Outdoor V1&V3 (Pre-release version)
EAP230-Wall V1, EAP235-Wall V1 3.0.2_Build 20240103 (Pre-release version)(Pre-release version)
EAP223 V1_1.3.0_Build 20240131 (Pre-release version)(Pre-release version)
Feb 4th, 2024:
Update EAP650/EAP650-Outdoor beta version to official release.
EAP650v1: https://www.tp-link.com/support/download/eap650/v1/#Firmware
EAP650-Outdoorv1: https://www.tp-link.com/support/download/eap650-outdoor/v1/#Firmware
Jan 4th, 2024:
Update EAP610/EAP613/EAP615-Wall/ EAP655-Wall/ EAP650-Wall beta version to official release.
EAP610v3: https://www.tp-link.com/support/download/eap610/#Firmware
EAP613v1: https://www.tp-link.com/support/download/eap613/#Firmware
EAP615-Wallv1: https://www.tp-link.com/support/download/eap615-wall/#Firmware
EAP655-Wallv1: https://www.tp-link.com/support/download/eap655-wall/#Firmware
EAP650-Wallv1: https://www.tp-link.com/support/download/eap650-wall/#Firmware
Dec 18th, 2023:
Update EAP610/EAP620 HD/EAP610-Outdoor beta version to official release.
EAP610v1: https://www.tp-link.com/support/download/eap610/v1/#Firmware
EAP610v2: https://www.tp-link.com/support/download/eap610/v2/#Firmware
EAP620 HDv2: https://www.tp-link.com/support/download/eap620-hd/v2/#Firmware
EAP620 HDv3: https://www.tp-link.com/support/download/eap620-hd/v3/#Firmware
EAP610-Outdoorv1: https://www.tp-link.com/support/download/eap610-outdoor/v1/#Firmware
Nov 24th, 2023:
Update the EAP650-Wall v1 and EAP655-Wall v1 firmware, which fixed some issues.
-
Before
EAP650-WALL_V1_1.1.1_Build 20230814 (Beta)
EAP655-WALL_V1_1.2.0_Build 20230717 (Beta)
-
After
EAP650-WALL_V1_1.1.3_Build20231120 (Beta)
EAP655-WALL_V1_1.2.3_Build20231120 (Beta)
Nov 15th, 2023:
Update the EAP610 v3, EAP613 v1 and EAP615-Wall v1 firmware, which fixed some issues.
-
Before
EAP610_V3_1.4.1_Build 20230828 (Beta)
EAP613_V1_1.4.1_Build 20230828 (Beta)
EAP615-WALL_V1_1.2.0_Build 20230711 (Beta)
-
After
EAP610_V3_1.4.2_Build 20231011 (Beta)
EAP613_V1_1.4.2_Build 20231011 (Beta)
EAP615-WALL_V1_1.2.2_Build 20231018 (Beta)
Nov 8th, 2023:
Update EAP670 v1 beta version to official release.
EAP670v1: https://www.tp-link.com/support/download/eap670/v1/#Firmware
Sep 27th, 2023:
Update the EAP610 v3 and EAP613 v1 firmware, which fixed some issues.
-
Before
EAP610_V3_1.4.0_Build 20230718 (Beta)
EAP613_V1_1.4.0_Build 20230718 (Beta)
-
After
EAP610_V3_1.4.1_Build 20230828 (Beta)
EAP613_V1_1.4.1_Build 20230828 (Beta)
Aug 31st, 2023:
1) Add the following EAP firmware for early access.
EAP610(EU&US&CA)_V1_1.1.1_Build 20230814 (Beta)
EAP650-WALL(EU)_V1_1.1.1_Build 20230814 (Beta)
EAP653(EU&US&CA&JP)_V1_1.0.9 Build 20230814
EAP620HD(CA)_V2_1.1.1_Build 20230815 (Beta)
EAP620HD(EU&US&JP)_V2_1.1.1_Build 20230814 (Beta)
2) Update the following EAP firmware for early access.
EAP610(EU&US&CA&JP&EG)_V2_1.1.3_Build 20230814 (Beta)
EAP650(EU&US&CA&JP)_V1_1.0.10_Build 20230814 (Beta)
EAP620HD(EU&US&CA&JP&EG)_V3_1.2.2_Build 20230814 (Beta)
Aug 15th, 2023:
Add the following EAP firmware for early access.
EAP610_V2_1.1.2_Build 20230717 (Beta)
EAP620HD_V3_1.2.1_Build 20230717 (Beta)
EAP610-Outdoor_V1_1.2.1_Build 20230717 (Beta)
EAP650-Outdoor_V1_1.1.0_Build 20230811 (Beta)
Aug 7th, 2023:
Add the following EAP firmware for early access.
EAP615-Wall_V1_1.2.0_Build 20230711 (Beta)
Aug 2nd, 2023:
Post the following EAP firmware for early access.
EAP610_V3_1.4.0_Build 20230718 (Beta)
EAP613_V1_1.4.0_Build 20230718 (Beta)
EAP655-WALL_V1_1.2.0_Build 20230717 (Beta)
EAP650_V1_1.0.9_Build 20230702 (Beta)
EAP670_V1_1.0.11_Build 20230702 (Beta)
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
Hello @jg1212,
jg1212 wrote
@Fae I ended up returning my new EAP670 because of this. After a while 4 of my devices in the 2.4 range would not receive IP addresses. They show connected but no IP. The Logs showed that they were being blocked by ACL rules which didn't exist. I tried upgrading to 1.0.11 but it didn't help. I could not downgrade to 1.0.6 because the EAP670 shipped with something between 1.0.6 and 1.0.11 which isn't available to download. The AP refused 1.0.6. I replaced it with an EAP610 and all is working perfectly again. Something very wrong with the EAP670. Just wanted you to know it is not just you. Thanks, JG
When you find the "Blocked by ACL" logs at Insights > Past Connection > Association Failure, it may cause by the following feature:
- ACL
- MAC Filter
- Lock to AP
If the issue starts after you upgrade to 1.0.11 firmware, it's recommended to check whether you have configured the Lock to AP feature on your 4 devices in question.
Go to Insights > Known Clients or Past Connections, find your devices in question and highlight it to open its properties window, go to Config to check whether the Lock to AP feature is enabled. If it is, please disable the Lock to AP feature and Save the settings, then check whether it works.
- Copy Link
- Report Inappropriate Content
Hello @jg1212,
jg1212 wrote
One of my EAP610 V2 APs was received with firmware 1.1.1. I tryied updating it to Beta 1.1.3 but it keeps failing saying that the upgrade file is invalid. Do you know what the issue could be? My other two APs upgraded from 1.0.2 to 1.1.3 just fine.
May I know where you got the 1.1.1 firmware from? Do you still have the firmware download link?
And could you please provide the firmware Build number of your 1.1.1 firmware?
How to get the firmware Build number:
In Devices list, highlight the EAP610 V2 with 1.1.1 firmware, then find the full Build number at Details > Overview from its properties window.
- Copy Link
- Report Inappropriate Content
Hello @bitjump,
bitjump wrote
We upgraded the EAP670 to 1.0.11 and noticed that we are unable to negotiate to 2.5G. We even tried using a 2' CAT7 patch cable connected directly to the Netgear switch (MS108EUP). Other devices on the network have no issues negotiating to 2.5G to the same switch.
Please let me know if there are any other test cases. We own three of these devices and all three behave the same way.
What's the previous firmware version of the EAP670? Are you able to negotiate to 2.5G before you upgrade to 1.0.11 firmware?
If you are using a PoE switch to power up the EAP670, you may replace with the original 12 V / 1.5 A DC power adapter for tests.
Besides, if possible, please check if the EAP670 can negotiate to 2.5G with other 2.5G devices.
- Copy Link
- Report Inappropriate Content
Fae wrote
Hello @jg1212,
jg1212 wrote
@Fae I ended up returning my new EAP670 because of this. After a while 4 of my devices in the 2.4 range would not receive IP addresses. They show connected but no IP. The Logs showed that they were being blocked by ACL rules which didn't exist. I tried upgrading to 1.0.11 but it didn't help. I could not downgrade to 1.0.6 because the EAP670 shipped with something between 1.0.6 and 1.0.11 which isn't available to download. The AP refused 1.0.6. I replaced it with an EAP610 and all is working perfectly again. Something very wrong with the EAP670. Just wanted you to know it is not just you. Thanks, JG
When you find the "Blocked by ACL" logs at Insights > Past Connection > Association Failure, it may cause by the following feature:
- ACL
- MAC Filter
- Lock to AP
If the issue starts after you upgrade to 1.0.11 firmware, it's recommended to check whether you have configured the Lock to AP feature on your 4 devices in question.
Go to Insights > Known Clients or Past Connections, find your devices in question and highlight it to open its properties window, go to Config to check whether the Lock to AP feature is enabled. If it is, please disable the Lock to AP feature and Save the settings, then check whether it works.
I checked all of those places and NONE of them had any data. I had previously used "Lock to AP" but removed it once the issues started. Unfortunately I can not do any further testing on this since I already returned the 670 and replaced it with a 610 which is working perfectly.
Thanks,
JG
- Copy Link
- Report Inappropriate Content
Fae wrote
Hello @jg1212,
jg1212 wrote
One of my EAP610 V2 APs was received with firmware 1.1.1. I tryied updating it to Beta 1.1.3 but it keeps failing saying that the upgrade file is invalid. Do you know what the issue could be? My other two APs upgraded from 1.0.2 to 1.1.3 just fine.
May I know where you got the 1.1.1 firmware from? Do you still have the firmware download link?
And could you please provide the firmware Build number of your 1.1.1 firmware?
How to get the firmware Build number:
In Devices list, highlight the EAP610 V2 with 1.1.1 firmware, then find the full Build number at Details > Overview from its properties window.
The EAP610 came from Amazon with this firmware a couple days ago.
Here is the full model and firmware build:
Model: EAP610(US) v2.0
Firmware Version: 1.1.1 Build 20230524 Rel. 74262
- Copy Link
- Report Inappropriate Content
@Fae 
Is it right when I lock a client to a specific ap and it will connect to a another ap I ve got the message blocked ?
so yes can I turn off that messages or can I solve it ?
- Copy Link
- Report Inappropriate Content
i tried updating my three EAP610 v2 to the 1.1.2 builds last week and one of my access points was no longer accepting connections. devices were unable to connect to it so i rolled back to 1.0.2 on all three devices. has anyone been running 1.1.3 on their EAP610 v2 and not had any issues yet? i was hoping 1.1.3 resolved whatever issue was going on so i can use the Lock to AP feature.
- Copy Link
- Report Inappropriate Content
dictoresno wrote
i tried updating my three EAP610 v2 to the 1.1.2 builds last week and one of my access points was no longer accepting connections. devices were unable to connect to it so i rolled back to 1.0.2 on all three devices. has anyone been running 1.1.3 on their EAP610 v2 and not had any issues yet? i was hoping 1.1.3 resolved whatever issue was going on so i can use the Lock to AP feature.
i'm on 1.1.3 and have no issues. Everything is running great.
JG
- Copy Link
- Report Inappropriate Content
i updated one of my access points to 1.1.3 and even though theres a device in the same room with it and its set up to lock to that AP, it refuses to connect to it. this is the same issue i was having before. it appears to be favoring the one AP i didnt update of the three. do all the AP's on the network need to be lock capable for them to work right?
- Copy Link
- Report Inappropriate Content
i believe they all need to be updated. .
- Copy Link
- Report Inappropriate Content
Information
Helpful: 2
Views: 63886
Replies: 274
Voters 1
