Early Access EAP Beta Firmware for Omada SDN Controller v5.9 (Updated on Mar 13, 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
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 @jmacul2,
Thank you for your valuable feedback.
jmacul2 wrote
I appreciate this firmware beta drop fro the EAP 655 Wall. I installed it and indeed, the PPSK withouth radius is working. Great throughput on the 5Ghz band, but 2.4Ghz is not usable. Definitely some serious collisions and major packet loss. I tried to troubleshoot, but had to take them offline as most of my smart IOT devices are on the 2.4 band. I also getting 100+ mbs using that 615-walls, but on the 655-walls, major packet loss and average throughput of about 20 mbps for 2.4 Ghz. I'll keep a watch when the next beta drops and try again. Thanks.
Do you get much higher throughput on 2.4GHz before you upgrade to this firmware EAP655-WALL_V1_1.2.0_Build 20230717 (Beta)?
If yes, how much throughput would you get and what is the previous firmware (with the Build number)?
BTW, may I know your Omada Controller version? What is the current firmware (with the Build number) of your EAP655-Wall?
- Copy Link
- Report Inappropriate Content
schoolboy error from me. Just realised the fw posted for the 650 is the non "wall" variant. Can you say when 650-wall fw will be available?
- Copy Link
- Report Inappropriate Content
I have 4 EAP 615 walls, and wanted to upgrade 2 of them to EAP 655 walls to take advantage of the DFS channels and the 160 MHz spread since no one in my area is using DFS. I only had 2 of the 4 615s using 2.4 ghz (channel 6 and 11). So when I upgraded, I replaced 2 615s with 655s keeping the 2.4 Ghz of channel 6 and 11. I normally would get 50-100+ mbps on the 615s. I am using 20 Mhz spreads. I kept the settings that same for the 2.4 wifi on the 655s. It seemed, though I am not sure, it was transmitting an excessive amount of traffic especially on channel 11. My first though was that it was multicast traffic. The channel utiilization on channel 11 was really high compared to the same channel on the 615s.
To be fair, I do have a lot of clients on 2.4 wifi....90% of them are smart home IOT devices (wifi switches, etc). I have enabled multicast storm control on the omada switch and I had all the multicast to unicast conversion enabled on both the 615s as well as the 655s. I didn't realize that maybe multicast to unicast wasn't supported yet on the 615s until now?
In any case, performance seemed to be fined until about 24 hours after upgrading where the 2.4 wifi seems to crawl to a halt. Tons of packet loss. I didn't have time to inspect it because I needed things functioning, so I just swapped the 655s back to the 615s for now.
I have since upgraded all my 615s to the 1.2 beta firmware and haven't had any issues so far.
Tonight I will switch them back again and run a tcpdump to see whats going on and return and report. This could be some race condition with something I'm doing on my network. I have 95 clients spread across the 4 APs....with about 70% of them on the two main aps that I've attempted to swap out.
Thanks again.
-J
- Copy Link
- Report Inappropriate Content
Hello @jmacul2,
Thank you for providing the details. I've created a support ticket via your registered email address, the ticket ID is TKID230815335, if you're willing to work with our support engineer, please pay attention to this ticket email and respond to the support engineer. Thanks!
- Copy Link
- Report Inappropriate Content
Hello @JCUK,
JCUK wrote
schoolboy error from me. Just realised the fw posted for the 650 is the non "wall" variant. Can you say when 650-wall fw will be available?
Oh okay, so you are actually using EAP650-Wall.
Sorry that we have no idea when the EAP650-Wall firmware will be available, but will update this post once it's available.
- Copy Link
- Report Inappropriate Content
EAP670 Bug report only
After 2-3 days device go to adopting and stay with this status. power cycle switch port is only option to get it online again.
all client loos connection.
never happened before update to 1.0.11
Controller 5.12 windows
Switch connected to AP SG2008P v1 software version 1.0.8
it has happened 3 times, I am waiting to downgrade the software until it happens on more time.
- Copy Link
- Report Inappropriate Content
Hi,
the announced feature "Added support for Multicast/Broadcast Management." for EAP650v1 does not work in my case (on1.0.9 beta). I'm running dynamic VLANs and want to stop multicast traffic to stop propagating to all VLANs on the EAP but neither does "Multicast-to-Unicast" work not "Multicast filtering" having an effect. I receive mDNS packets from other VLANs on EAP only.
How do I open a ticket for that?
Thanks
- Copy Link
- Report Inappropriate Content
Hello @MR.S,
Thank you for reporting the issue here. Our support engineers would like to check some details with you for further investigation. I've created a support ticket via your registered email address, the ticket ID is TKID230815775, if you're willing to help, please pay attention to this ticket email and respond to the support engineer. Thanks!
- Copy Link
- Report Inappropriate Content
Hello @CuBiC,
Thank you for bringing this to my attention. I've helped to open a ticket for your case, the ticket case ID is TKID230815793, which has been escalated to our support engineer to look into the issue further, please keep an eye on your mailbox and reply to the support email. Thanks!
- Copy Link
- Report Inappropriate Content
Fae wrote
Hello @bentoboxchicken,
Thank you for your valuable feedback. Please allow me to check some details to understand what happened.
bentoboxchicken wrote
@Hank21 The firmware update didn't work on my EAP670 v1.26. After upgrade it remained disconnnected from the controller. Trying to access the AP directly through a direct Ethernet connection through the IP address 192.168.0.254 would cause it to power off and on.
May I know your Omada Controller version? What is the current firmware (with the Build number) of your EAP670? Are you still running the EAP670_V1_1.0.11_Build 20230702 (Beta) firmware?
When you found that the EAP remained disconnected from the Controller, was the EAP670 itself still working? Were the wireless clients still connected and working well?
How did you power up your EAP670, via the DC power or via a PoE switch? Have you tried to reset the EAP670 (hold ~5s until LED flash) and see if it helps? Or have you tried to recover the firmware by following the guide below?
How to use the Recovery Mode to recover the firmware for EAP
Edit:
Our support engineers would like to check more details with you to look into the issue. I've created a support ticket via your registered email address, the ticket ID is TKID230813337, if you're willing to help, please pay attention to this ticket email and respond to the support engineer. Thanks!
@Fae I updated my original post. The unit i had was refurbished and likely defective. After replacing it with a new one, firmware upgrade went through without issue.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 2
Views: 60054
Replies: 273
Voters 1
