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 @jg1212,
jg1212 wrote
Thank you for the advice. I forgot the EAP610 "V2" with 1.1.1 firmware and logged in as standalone mode and the firmware updated to 1.1.3 just fine. This may be a re-occurring question if a lot of these devices shipped with 1.1.1. You may want to have the controller team add some code to check for which port is being used for firmware upgrades.
Thank you for updating us with your solution, good to know that upgrade via standalone works.
And thank you for your kind suggestion, I've forwarded it to the controller team for evaluation.
- Copy Link
- Report Inappropriate Content
My Setup:
Controller on Ubuntu 22.04 LTS
Version: 5.12.6
| DEVICE NAME | IP ADDRESS | STATUS | MODEL | VERSION | UPTIME | CLIENTS |
|---|
| 10.10.233.2 |
CONNECTED |
7 |
||||
| 10.10.233.7 |
CONNECTED |
18 |
||||
| 10.10.233.8 |
CONNECTED |
20 |
||||
| 10.10.233.6 |
CONNECTED |
7 |
||||
| 10.10.233.9 |
CONNECTED |
3 |
All wired - no Mesh active.
The only candidate for this beta fw is the EAP615-wall. So I tried it. After some issues re-adoping it it seems to work. However in the long run, all clients connected to that AP, had serious connection issues while browsing. Youtube was insanely slow - google news showed partly - pictures came very slow.
Ping was always good. I was not able to track down the issue. I believe some DNS-SSL-Whatever thing was not working smoothly anymore. There were time windows where all worked as expected. And then 2-5 minute windows with the above issues were visible.
Thus I reverted and it looks good again.
- Copy Link
- Report Inappropriate Content
Hi @wuppi,
wuppi wrote
I believe I ran into the same issue with my 615wall.
Looking at the status during upgrading, the last visible step was "configuring". Then "heartbeat missed" and now "disconnected".
DISCONNECTED
Edit: had to reset - re-adopt and now it looks working
Hope you are doing well. I'm wondering whether you encounter a second Disconnected or Other Unusual Status after you reset and re-adopt the EAP615-Wall?
Regarding the disconnected issue you encountered during the firmware upgrade, our support engineer would like to look into the issue further. I've created a support ticket via your registered email address, the ticket ID is TKID230912994, if you're willing to help, please pay attentiont to this ticket email and respond to the support engineer. Thanks!
- Copy Link
- Report Inappropriate Content
Hello @wuppi,
wuppi wrote
The only candidate for this beta fw is the EAP615-wall. So I tried it. After some issues re-adoping it it seems to work. However in the long run, all clients connected to that AP, had serious connection issues while browsing. Youtube was insanely slow - google news showed partly - pictures came very slow.
Ping was always good. I was not able to track down the issue. I believe some DNS-SSL-Whatever thing was not working smoothly anymore. There were time windows where all worked as expected. And then 2-5 minute windows with the above issues were visible.
Thus I reverted and it looks good again.
Thank you for your valued feedback. I've created a support ticket for you, the support engineer will follow up with your case later.
- Copy Link
- Report Inappropriate Content
Hi, hope you are doing well.
EAP 615-Wall V1.0 was upgraded to beta EAP615-WALL(EU&US&CA&JP&EG)_V1_1.2.0_Build 20230711 (Beta) and i lost roaming in that area of the home , i was able to connect to the EAP 615 running beta firmware but no internet., I have 4 EAP650 running beta firmware and roaming and other aspect seem to be working fine, but as soon as any device is connected to EAP 615-wall internet is lost and device Wi-Fi need to be switch off and back again to connect and than the internet is restored.
I have downgraded to the Original V1.0 firmware EAP615-Wall(EU)_V1_1.1.6 Build 20230330 and it better now, no more internet loss or reconnect/Wi-Fi on or off required.
but just one thing i noticed is that the hops between EAP650 to EAP650 are considerably faster than hops between EAP650 to EAP615.
below in my home H/W post downgrade of EAP 615 back to V1_1.1.6 all others remain at beta
Thank you and regards
- Copy Link
- Report Inappropriate Content
@Fae a few minutes ago I recieved this message in my log that AP gang was connected .
accespoint gang is connected while the AP gave no message for disconnecting (strange right?)
AP say also connected two days ago see image below
👇
also I don't no if my devices lost connection
using the beta firmware for EAP 650
- Copy Link
- Report Inappropriate Content
Hi
I'm running the beta firmware for the EAP655-Wall(EU) v1.0 ( 1.2.0 Build 20230717 Rel. 63070 ) on top of the ER7212PC v1.0 ( 1.1.0 Build 20230803 Rel.83667 ).
However, I noticed that with the beta firmware, after a few days the EAPs become disconnected.
The only mention in the log seems to be: "[Failed]Failed to readopt <eap-name-here> automatically. "
A powercycle (e.g. unplug them) resolves this, and they are readopted and reconfigured.
However, the wifi remains 'up' for the offending AP (ssid visible) but can't be connected to anymore (I'm using PPSK without Radius).
For now I've implemented a workaround by setting a nightly reboot for all APs, which seems to keep them alive.
Meanwhile, the gateway etc. is working fine, wired network is up, but everything on the 'crashed' eaps becomes disconnected.
To me, it feels like something fills up (out of memory?) which is prevented by a periodic reboot.
Other than that, no real issues, and real happy that PPSK is now on it's way :)
- Copy Link
- Report Inappropriate Content
Hello @Kash01976,
Kash01976 wrote
EAP 615-Wall V1.0 was upgraded to beta EAP615-WALL(EU&US&CA&JP&EG)_V1_1.2.0_Build 20230711 (Beta) and i lost roaming in that area of the home , i was able to connect to the EAP 615 running beta firmware but no internet., I have 4 EAP650 running beta firmware and roaming and other aspect seem to be working fine, but as soon as any device is connected to EAP 615-wall internet is lost and device Wi-Fi need to be switch off and back again to connect and than the internet is restored.
Trying to understand the issue here. Are you saying that the clients connected to EAP650 will roam to EAP615-Wall_V1_1.2.0 (Beta) when they are moving closer to the EAP615-Wall, but the clients are only connected with no Internet access, and you have to manually turn the Wi-Fi off on the EAP615-Wall and turn it back on to get the clients connected with Internet access? If I get anything wrong, please feel free to correct me. Thank you!
Kash01976 wrote
I have downgraded to the Original V1.0 firmware EAP615-Wall(EU)_V1_1.1.6 Build 20230330 and it better now, no more internet loss or reconnect/Wi-Fi on or off required.
but just one thing i noticed is that the hops between EAP650 to EAP650 are considerably faster than hops between EAP650 to EAP615.
What does the "hops" mean here and how did you test it to get the above conclusion? Do you mean clients roam between EAP650 and EAP650 will take shorter time than the same clients roam between EAP650 and EAP615-Wall?
- Copy Link
- Report Inappropriate Content
Hello @Mariomark1541,
Mariomark1541 wrote
@Fae a few minutes ago I recieved this message in my log that AP gang was connected .
accespoint gang is connected while the AP gave no message for disconnecting (strange right?)
First, you probably know that a "device was disconnected" log means that the device has lost connection with the Omada controller for more than 5 minutes. When the device is changed back to "Connected" state very quickly, the controller cannot sense its status change but will only report with "device was connected", that's why you only get one "AP was connected" log.
Generally speaking, we may get a single "device was connected" log when the device was rebooted. You can click the reboot icon on an AP from the Devices list of your Controller to have a test.
- Copy Link
- Report Inappropriate Content
Hello @YetOneMore,
YetOneMore wrote
I'm running the beta firmware for the EAP655-Wall(EU) v1.0 ( 1.2.0 Build 20230717 Rel. 63070 ) on top of the ER7212PC v1.0 ( 1.1.0 Build 20230803 Rel.83667 ).
However, I noticed that with the beta firmware, after a few days the EAPs become disconnected.
The only mention in the log seems to be: "[Failed]Failed to readopt <eap-name-here> automatically. "
A powercycle (e.g. unplug them) resolves this, and they are readopted and reconfigured.
However, the wifi remains 'up' for the offending AP (ssid visible) but can't be connected to anymore (I'm using PPSK without Radius).
For now I've implemented a workaround by setting a nightly reboot for all APs, which seems to keep them alive.
Regarding the wifi cannot be connected issue, did you fix it by a second reboot on the EAP that was disconnected, or how did you sort it out finally?
To figure out the issue, I've created a support ticket via your registered email address and escalate to our support engineer for further investigation, the ticket ID is TKID230919422, please pay attention to this ticket email and respond to the support engineer for follow-up. Thanks!
- Copy Link
- Report Inappropriate Content
Information
Helpful: 2
Views: 75577
Replies: 275
Voters 1
