Hi All,
Sometimes, the firmware release information is delayed than the online firmware update, people may be confused what has been fixed with the new firmware, wondering whether it can be updated or which firmware is the one to be updated.
This thread will aperiodically introduce the latest firmware releases for Omada SDN Controller. Hope it help you learn more about the new firmware.
Before upgrading the Omada SDN Controller:
If you are planning to upgrade from the old controller(v3.2.x or below) to Omada SDN Controller (v4 or above), please read the Omada Controller Upgrade Guide first.
Related FAQs:
Why my Omada controller cannot manage the latest EAP
Frequently asked questions of Omada SDN solution related to upgrading and management
----------------------------------------- *Firmware releases for Omada SDN Controller* --------------------------------------------
【Update 2/10/2021】Latest firmware releases for Omada Software Controller v4.2.11
Published Date: 2021-02-09
Omada_Controller_V4.2.11_Windows
Omada_SDN_Controller_v4.2.11_linux_x64.tar
Omada_SDN_Controller_v4.2.11_linux_x64.deb
**The OC200 with built-in Omada SDN Controller v4.2.11 is not available yet.
Bug Fixed:
1. Fixed the bug that the IPSec and L2TP over IPSec VPN cannot be set on the same WAN port at the same time. -> Omada SDN V4.2.11 supports configuring IPSec and L2TP over IPSec VPN on the same WAN.
2. Fixed the bug that the speed test in the dashboard may display general error and internet Capacity and Gateway are still displayed as N/A. Discussed HERE.
3. Fixed the bug that we may not be able to re-adopt the Mesh AP if we failed to adopt it with the wrong password for the first time.
4. Fixed the bug that the wireless client will be displayed as a wired client (LAN) on the controller. Discussed HERE.
5. Fixed the bug that the controller's band steering range is inconsistent with the actual supported range of EAP, resulting in the configuration not taking effect.
6. Fixed the bug that the wired clients that have passed portal authentication may display 0 traffic data in the Authorized Clients list.
7. Fixed the bug that the wired clients that have passed portal authentication may have lower traffic statistics.
8. Fixed the bug that the Controller may show a general error if we forget an EAP and then delete an SSID.
9. Fixed the bug that the wired clients that have passed RADIUS portal authentication may have higher RADIUS accounting traffic statistics.
For more information about the Omada SDN Controller, please check the download link below.
Omada Software Controller:
https://www.tp-link.com/en/support/download/omada-software-controller/#Controller_Software
Omada Hardware Controller-OC200:
https://www.tp-link.com/en/support/download/oc200/#Firmware
----------------------------------------- *Firmware releases for Omada SDN Controller* --------------------------------------------
[Update 12/31/2020] Latest firmware releases for Omada SDN Controller v4.2.8.
Published Date: 2020-12-29
OC200(UN)_V1_1.7.3 Build 20201119
Note: Built-in Omada SDN controller v4.2.8. For OC200 (UN) v1.0 only.
Published Date: 2020-12-11
Omada_SDN_Controller_V4.2.8_Windows
Omada_SDN_Controller_v4.2.8_linux_x64.deb
Omada_SDN_Controller_v4.2.8_linux_x64.tar
Bug Fixed:
1. Fixed the bug that the device will move to the upper left corner when you visit again if the device location is locked in the MAP. Discussed here.
2. Fixed the bug that uplink signal strength of Mesh EAP is not displayed accurately on the devices private configuration page.
3. Fixed the bug that the user without device permission may display that it still has permission in the account settings.
4. Fixed the bug that the function of Log Server/Alert Email may not take effect after restoring the backup file of Controller.
5. Fixed the bug that you may unsuccessfully import the local user account in the Hotspot Manager.
6. Fixed the bug that the “Last Seen” time in the private configuration page of the switch is the last uptime (not the last disconnected time) after the switch disconnects from Omada Controller.
7. Fixed the bug that the expiration time of Facebook authentication in “->authorized clients” is inconsistent with the actual expiration time.
8. Fixed the bug that the Controller may generate lots of roaming logs if clients leave from one EAP to another EAP implicitly since clients still send auth frame to the previous EAP.
New Feature/Enhancement:
1. Support to manage TL-SL2428P (UN) 4.20.
2. Optimize the protocol for the device reporting information of rate/duplex capability.
3. Optimize the password retrieval mechanism. If multiple local accounts are bound to one mailbox, you can choose which account to reset the password.
4. Add the batch cancelling of devices migration in the migration function.
5. Vulnerability optimization