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
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Hi @Hank21 ,
thanks for your support and sorry for answering late. With the update of the firmware, at least sometimes the IPv6 traffic was possible, but sometimes not.
In the meantime, after trying several setups, settings, devices, and so on, I finally can reproduce the error exactly with both of the access points EAP650-Wall and EAP650-Wall:
Here is the summary:
Setup:
- Access points are connected to switch TL-SG2016P on port 1 (EAP-655-Wall) and port 2 (EAP650-Wall)
- EAP655-Wall: Firmware 1.2.4 Build 20231208 Rel. 73353(4555)
- EAP650-Wall: Firmware 1.1.4 Build 20231208 Rel. 66358(4555)
- (only) one SSID is configured per access point:
SSID with VLAN ID 10 on EAP-655-Wall
SSID with VLAN ID 20 on EAP-650-Wall - in a first step, the ports on the switch are configured as following:
- port (port 1 on the switch) of EAP655-Wall is a tagged port of VLAN 10, port of EAP650-Wall is not part of VLAN 10
- port (port 2 on the switch) of EAP-650-Wall is a tagged port of VLAN 20, port of EAP655-Wall is not part of VLAN 20
- one port on the switch (11) is configured as untagged in VLAN 10 (running gateway1/DHCP on this port)
- another port on the switch (12) is configured as untagged in VLAN 20 (running another gateway2/DHCP on this port)
- summary of VLANs: there are two VLAN running in parallel but not on the same ports, as AP and gateway are in separated VLANs with no overlap:
- VLAN ID 10: tagged (1) AP, untagged (11) gateway1
- VLAN ID 20: tagged (2) AP, untagged (12) gateway 2
Reproducible error:
- As soon as I add one of the ports of the access points to the other VLAN by configuring it as a tagged port (for a potential other SSID with another VLAN ID), I got these strange IPv6 errors, where a valid access is not possible anymore (tested with site https://test-ipv6.com/index.html.en_US)
Example: adding port (1) as a tagged port of VLAN ID 20 leads to the IPv6 error
Goal for the final setup:
- My final setup of the access points VLAN setup would be:
- having two SSIDs running on the access points with two different VLAN IDs (10 & 20)
- having this acces point on the switch with a tagged port of VLAN ID 10 and a tagged port of VLAN ID 20 configured
- one SSID should use the gateway1 (over VLAN 10) and the other SSID should use the other gateway2 (over VLAN ID 20)
Problem:
- With the current limitation, that one of the access points (EAP650-Wall or EAP655-Wall) couldn't be part of two VLANs by a tagged port in both VLANs, the mentioned solution wouldn't be possible at all.
Do you have any further advice or an estimation of when this bug would be fixed in the firmware? I'm currently setting up the infrastructure with several access points and switches of this type but with this limitation, an implementation as expected wouldn't be possible at all, so I'm currently waiting with ordering the complete set of devices.
Thanks in advance!
- Copy Link
- Report Inappropriate Content
Hi @Jay_3_14,
Jay_3_14 wrote
Reproducible error:
- As soon as I add one of the ports of the access points to the other VLAN by configuring it as a tagged port (for a potential other SSID with another VLAN ID), I got these strange IPv6 errors, where a valid access is not possible anymore (tested with site https://test-ipv6.com/index.html.en_US)
Example: adding port (1) as a tagged port of VLAN ID 20 leads to the IPv6 error
May I confirm whether the IPv4 is working properly in this scenario?
"As soon as I add one of the ports of the access points to the other VLAN by configuring it as a tagged port"
Do you mean set the ETH Vlan ID like the below image on the EAPs but it will cause the current issue?
What is the firmware version of your Controller?
- Copy Link
- Report Inappropriate Content
Hi @Hank21,
I'm sorry, my description was a little bit misleading perhaps...
The Eth-Ports on the access points I'm not using at all, only the one on the background to connect the AP to the switch (TL-SG2016P).
On this switch, I had the AP as (tagged) port of one VLAN ID (10) only first and everything went well with IPv6. When adding the port on the switch to another VLAN ID (20), I got these troubles with IPv6, and only with IPv6. IPv4 works well without any problems.
As a workaround, I turned of the Router Advertisement on the Router to avoid having IPv6 in my local network. By this, all timeouts on the wifi clients are gone but the price is not having IPv6 anymore. I assume that as soon as the access point is part in multiple VLANs (by tagged connection/port on the switch), something went wrong with multicast/RA messages to the access point, could that be?
- Copy Link
- Report Inappropriate Content
To better assist you, 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 TKID240145443, please check your email box and ensure the support email is well received. Thanks!
Once the issue is addressed or resolved, welcome to update this topic thread with your solution to help others who may encounter the same issue as you did.
Many thanks for your great cooperation and patience!
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
I had to grab it from here. I thinks it's because it's not release for your region.
https://www.tp-link.com/en/support/download/eap655-wall/#Firmware
- Copy Link
- Report Inappropriate Content
that was the case! Thank you. I'm not sure why the Canadian website doesn't have the firmwares but US does...
thanks again!
- Copy Link
- Report Inappropriate Content
Information
Helpful: 2
Views: 75056
Replies: 275