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
EAP245(US) V4.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)
EAP680 v1.0(EU)
EAP683 UR/LR v1.0/1.6(EU/US/CA/JP)
...
*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
EAP680(EU)_v1_1.1.0_Build20240423(pre-release)
EAP683LR(EU_US_CA_JP)_v1_EAP683LR(US)_v1.6_1.1.0_Build20240412(pre-release)
EAP683UR(EU_US_CA_JP)_v1_EAP683UR(US)_v1.6_1.1.0_Build20240412(pre-release)
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
July 5, 2024:
Official version EAP245 V4(US) 1.3.1 has been released.
Currently we only have US version, for other regions, please keep waiting for the update.
June 19, 2024:
Update to provide the Pre-Released version for the following EAPs:
EAP680 V1, EAP683 LR V1, EAP683 UR V1 Pre-release (Released on June 19th, 2024)
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 @Philldu,
Philldu wrote
I noticed similar issues like Kash01976.
Right now I'm waiting for my iPad to connect to my EAP225-Outdoor, it sicks to the EAP670 indoor, which is definitely out of range, iPad is connected with 2,4GHz and only one signal indicator.
Sitting next to the outdoor AP my iPhone has full signal strength on 5GHz, after turning Wi-Fi on and off. The iPad doesn't connect automatically since about 20 minutes.
Also got the same issue with the EAP670 and an EAP615-Wall, client sicks till the connection is cut manually.
Are you now running with EAP670_V1_1.0.11_Build 20230702 (Beta), and EAP615-Wall_V1_1.2.0_Build 20230711 (Beta) provided here? Does the issue started after you install the EAP670 1.0.11, EAP615-Wall 1.2.0 Beta firmware?
From your description, it seems that your issue is that the iPad will not connect to the nearest AP or switch to another AP automatically, no matter it is EAP225-Outdoor, EAP670 or EAP615-Wall, is that right? If it is the case, you may follow the guide below to do some wireless optimization, and try disable Fast Roaming and Lock to AP feature for tests if you have enabled them.
How to optimize wireless performance of EAP product
If the issue is not specific to the Beta firmware provided in this thread, I'd encourage you click here to start a new thread to avoid misleading other community members who subscribed to this thread. Starting with a new thread will help you get the answers or solutions quickly, which may also help others who may have the same issues to join the topic easily and find solutions. Thanks and see you in the forums soon!
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Thank you for your prompt response and support.
I went through the Wireless Networks --> WLAN ---> Edit wireless network setting and found the 802.11r box unchecked and grayed out. This was a surprise as i always keep 802.11r box checked, and i found the following option : MLO box checked.
Upon uncheck of the MLO options box., the 802.11r became active for selection again. As soon as the 802.11r option was enabled and changes applied within 30 seconds the APs lost connections and reconnected, and i got my roaming capability back working flawlessly.
Thanks again for your help and support.
Kind
Regards
- Copy Link
- Report Inappropriate Content
Multiple times I've tried installing the firmware for my EAP615 Wall's, and each time that I do, the ability for the Nest Protects installed in my home to connect to the network begins to fail.
When I try to re-add them to the network, I get a very unhelpful message from Google "Nest protect unable to connect to WiFi, error code P006 (3.10)"
Try as I might, nothing will get the Protects back on the network until I roll back the firmware to 1.1.6 and reset the Nest Protects. This to me indicates "something" is broken in the 1.2.0 firmware.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Hello @Kash01976,
Thanks for updating us on what happened and what you've done to have it sorted out.
If there is anything new came out, please feel free to let me know.
@Philldu, perhaps you may check your wireless settings and enable 802.11r as @Kash01976 did, see if that helps for you.
If the issue still persists, welcome to click here to start a new thread with your device firmware and issue description for further assistance.
- Copy Link
- Report Inappropriate Content
Hello @Cozz,
Cozz wrote
I have just found out via Insights that the Nest Protects - when the EAP is on the 1.2.0 firmware - are blocked by an ACL that I have not setup. When I rollback the firmware, this mystery ACL block vanishes.
Could you please attach a screenshot of the ACL block entry for checking?
Did you enable Multicast Filtering at Wireless Networks > WLAN > Edit wireless network > Multicast/Broadcast Management?
Upon the following article from Google Nest, it seems that Multicast should be enabled if you want to connect a Nest Protect.
Can’t connect Nest Protect to the app or Wi-Fi
- Copy Link
- Report Inappropriate Content
Fae wrote
Hello @Cozz,
Cozz wrote
I have just found out via Insights that the Nest Protects - when the EAP is on the 1.2.0 firmware - are blocked by an ACL that I have not setup. When I rollback the firmware, this mystery ACL block vanishes.
Could you please attach a screenshot of the ACL block entry for checking?
Did you enable Multicast Filtering at Wireless Networks > WLAN > Edit wireless network > Multicast/Broadcast Management?
Upon the following article from Google Nest, it seems that Multicast should be enabled if you want to connect a Nest Protect.
Can’t connect Nest Protect to the app or Wi-Fi
I've checked the ACL and they are all blank; I've never added anything in there.
I did see that IPv6 needed to be enabled, so I have done that as well.
Multicast settings are correct I think; screenshot attached as well.
- Copy Link
- Report Inappropriate Content
@Hank21 I've upgraded my EAP670 to 1.0.11 beta and this is causing one of my IoT unable to connect. Rolling back to 1.0.6 beta fixed the issue.
I have no clue what's the reason, the IoT is one of the Chinese dongles for PV (solar panels). Other devices (phones, printer) and other IoT devices works normally on 1.0.11 beta.
- Copy Link
- Report Inappropriate Content
@Hank21 Can you please provide an URL to version 1.0.6 beta (which fixes the Adoption Loop). I am stuck as 1.0.11 crashes my IoT and official stable 1.0.6 has a loop.
If you could provide URLs to every version between 1.0.6 stable and 1.0.11 beta I can verify which one exatly crashes my IoT.
Thanks
EDIT: when I connect my IoT to open (no pass) network (hosted by the same EAP670) - it works.
EDIT 2: Changing PMF from "Mandatory" to "Capable" fixed the issue. (wifi settings)
Worth to metion that using 1.0.6 beta and Mandatory PMF used to work - probably this was not implemented properly.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 2
Views: 76834
Replies: 275
Voters 1
