Early Access Omada SDN Controller_V5.14 Pre-release (Released on Feb 29th, 2024)
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Thank you all for your valuable feedback on the pre-release firmware!
The early access controller version 5.14.20 has been released, check the following link for details.
Omada SDN Controller_V5.14.20 Pre-release
This Article Applies to
Omada_SDN_Controller_v5.14.0.10 Windows (Windows 7/8/10/11/Server, 64bit Recommended)
Omada_SDN_Controller_v5.14.0.11 Windows (Windows 7/8/10/11/Server, 64bit Recommended)
Omada_SDN_Controller_v5.14.0.11_Linux_x64.tar.gz (Ubuntu 16.04/18.04/20.04, Debian 8/9/10, CentOS 6/7)
Omada_SDN_Controller_v5.14.0.11_Linux_x64.deb (Ubuntu 16.04/18.04/20.04, Debian 8/9/10)
Overview
We hope to offer you with a chance to experience the new features added in the Controller v5.14 in advance, and also give us TP-Link the opportunity to fully test the firmware in your real network environment and scenarios before the official release. All feedback is welcome, including lettings us know about successful upgrades.
Release Notes
New Feature
1. Added support for EAP-OWE management frame encryption.
2. Added support for loopback detection on EAP-Wall series models.
3. Added support to modify Beacon Intervral to a larger range.
4. Added support to disable port and configure port VLAN for Multi-LAN port EAPs.
5. Added support to Logout when using Portal on EAPs.
6. Added support for multiple Radius servers when using MAB on EAPs.
7. Added support to custom channel set.
8. Added support to display the actual working channel width when set channel width to auto.
9. Added support to display the status information of the Multi-Lan port EAPs downstream port.
10. Added support to multicast/broadcast statistics about EAPs.
11. Added support for Terminal and Pack Capture when enable the Cloud Access on Controller.
12. Added support for Controller-configured device names to be delivered to devices (hostname, LLDP, and SNMP).
13. Added support to return error code prompt when configuring status synchronization.
14. Added support for centralized proxying of Radius.
15. Added support to display the Maximum Associated Clients range according to the model.
16. Added support to display information about downlinked Omada devices.
17. Added support for EAP-related DNS queries in Tools.
18. Added support for NAS ID configuration in SSID enterprise encryption, which can be configured as Device Name.
19. Added support that PPSK entries up to 1024.（Do not apply to Omada_SDN_Controller_v5.14.0.11 Windows ）
20. Added support to ER7412-M2.
21. Added support to configure the wireless function of ER706W-4G.
Enhancement
1. Clients related optimization:
- EAP and Switch add the See All logo to jump to the Clients page.
- Add MAC address filtering search for connected clients.
- Add Signal to the EAP Client page.
2. Add support to search MAC Group.
3. AP VLAN related optimization:
- The default LAN name of Network is changed to Default and modification is not supported.
- Management VLAN and SSID VLAN no longer support configuring the same VLAN as the default LAN
- SSID VLAN supports selecting Network
4. Added support to report OFDMA default values, which may be different for different EAP models.
5. Optimize Client association log.
6. Optimize the mechanism of Portal’s Rate Limit function.
Note
1. The built-in Radius authentication server no longer supports the PPSK function, and the configured related SSID will be automatically deleted after the installation of the Controller.
Notes
1. This version of the Controller is fully applied to the Omada APP of version 4.14 or above.
2. Omada SDN Controller can only manage certain devices running the supported firmware. Please confirm that your device is compatible with the SDN Controller.
3. For Windows OS, Java 8 (or OpenJDK-8) and above are required. How to install Java Runtime Environment (JRE) for Omada SDN Controller on Windows?
4. For Linux version, 64-bit Linux OS is supported and Java 8 (or OpenJDK-8) and above, MongoDB v3 and v4 are necessary required. How to install Omada SDN controller on Linux system (above Controller 5.0.29)
5. If you are upgrading from controller v3.x, it's highly recommended to upgrade 3.x to v4.1.5 first, then v4.1.5 to the latest 5.x. Please follow the Omada Controller Upgrade Guide in the installation package before upgrading.
Firmware Download
Before the Upgrade
(1) Please be sure you have read the Beta Test Agreement before upgrading the Pre-release firmware!
(2) For the sake of insurance, it's always recommended to save a copy of the controller Backup Config file before upgrade or downgrade.
(3) You may follow the following guide to upgrade your Omada Controller. How to Upgrade or Downgrade Omada SDN Controller
Firmware Download Link
-
Direct Download
Omada_SDN_Controller_v5.14.0.10_Windows(Pre-release version)
Omada_SDN_Controller_v5.14.0.11_Windows(Pre-release version)
Omada_SDN_Controller_v5.14.0.11_Linux.tar.gz(Pre-release version)
Omada_SDN_Controller_v5.14.0.11_Linux.deb(Pre-release version)
Additional Information
If somehow you encounter an issue during or after the controller upgrade, it's suggested to contact us with the following info:
- Omada Controller version (previous and current)
- Device Model(s), Hardware and Firmware versions
- (if possible) A copy of the Log file and Backup Config file
If you decide to downgrade the controller before reporting the issue to TP-Link, it's suggested to save a copy of the current Log file and Backup Config file before you do that, which could help to investigate and address the issue quickly.
>> How to get the Log file and Backup Config file for Omada SDN Controller:
-
If your windows software controller failed to get launched, please locate to the controller installation path for the Log file.
-
If it's not a launch issue, you can export the Log file and Backup Config file in the local network.
-
For Omada Controller v5.8 or later version,
In the Global View, go to Settings > Maintenance > Backup & Restore > Retained Data Backup, select Settings Only, then click Export for the Backup Config file. On the same page, scroll down for Export for Support, click Export Running Logs for desensitized Log file.
-
For Omada Controller v5.6 or v5.7,
Go to Settings > Maintenance > Backup & Restore > Retained Data Backup, select Settings Only, then click Export for the Backup Config file. On the same page, scroll down for Export for Support, click Export Running Logs for desensitized Log file.
-
For Omada Controller v5.5 or previous version,
Go to Settings > Maintenance > Backup & Restore > Retained Data Backup, select Settings Only, then click Export for the Backup Config file . Go to Settings > Services > Export Data > Running Log to export the Log file.
-
Update Log
March 21,2024：
Provide the following controller firmware for early access.
- Omada_SDN_Controller_V5.14.0.11_Windows(Pre-release version)
March 20,2024：
Provide the following controller firmware for early access.
- Omada_SDN_Controller_v5.14.0.11_Linux.tar.gz(Pre-release version)
- Omada_SDN_Controller_v5.14.0.11_Linux.deb(Pre-release version)
Feb 29th, 2024:
Provide the following controller firmware for early access.
-
Omada_SDN_Controller_V5.14.0.10_Windows(Pre-release version)
Recommended Threads
TP-Link Early Access Program Is Now Available!
Get the Latest Omada SDN Controller Releases Here - Subscribe for Updates
Experience the Latest Omada EAP Firmware - Trial Available Here, Subscribe for Updates!
Get the Latest Firmware Releases for Omada Routers Here - Subscribe for Updates
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Thanks @Hank21, the "Known Clients" page issue is now finally fixed in this version! (also thanks to @MrHC1983 @sb0373 for reporting this too!)
But, I found a new problem with VLAN configuration on this version, the VLAN config conversion from previous version (5.13.8.30) is not smooth for me. I have to manually open each wifi network setting and change the VLAN option from "By VLAN ID" to "By Network" to make it work.
- Copy Link
- Report Inappropriate Content
Cross posting here in case it is Contorller and not EAP firmware:
https://community.tp-link.com/en/business/forum/topic/660772
Where did the IPv6 support go in the EAP690E HD?
a minute ago
Tags: #IPv6
Model: EAP690E HD
Hardware Version: V1
Firmware Version: 1.0.3
Where did the IPv6 option go in the EAP690E HDs? I swear it was there, or am I on something? I am on the 5.14 Controller Beta...
Any insight? I found this older thread:
https://community.tp-link.com/en/business/forum/topic/609100
Where is seems to indicate it is fixed in 1.0.3, so...
- Copy Link
- Report Inappropriate Content
I also had the same VLAN issue as reynhartono, and I also fixed it by changing the VLAN option from "By VLAN ID" to "By Network".
I use the Linux version of the contoller (mbentley omada-contoller docker image). I have a third-party (Mikrotik) router, with an Omada switch (SG3428x), and two access points (EAP650, EAP773).
- Copy Link
- Report Inappropriate Content
@Hank21 I just realized there's no "Association Failure" log anymore in the Insights -> Past Connections page. Is this feature removed or moved somewhere else?
- Copy Link
- Report Inappropriate Content
what do you mean? what is the issue? I don't understand what the problem is and what this resolved?
- Copy Link
- Report Inappropriate Content
W38122077 wrote
what do you mean? what is the issue? I don't understand what the problem is and what this resolved?
@W38122077 the resolved one is this one: https://community.tp-link.com/en/business/forum/topic/649884?replyId=1322006
New problems:
- VLAN in Wifi Network is not working after the update. I have to manually open each wifi network setting and change the VLAN option from "By VLAN ID" to "By Network" to make it work. (confirmed by @bmaddison)
-
No "Association Failure" log anymore in the Insights -> Past Connections page. Is this feature removed or moved somewhere else?
- Copy Link
- Report Inappropriate Content
Very interesting. Mine did not convert over correctly either, but I still have functional WiFi. But perhaps that is because I do not use an Omada gateway. I did change it, and interestingly enough, a couple Apple HomePods that were constantly dropping off nad back on the network and trying to roam from one AP to another have completely quieted back down.
Definitely seems like a bug.
- Copy Link
- Report Inappropriate Content
reynhartono wrote
@Hank21 I just realized there's no "Association Failure" log anymore in the Insights -> Past Connections page. Is this feature removed or moved somewhere else?
Hi @reynhartono
The next controller version will optimize Client association log. The association failures column has been removed. But you are still able to find the detail logs in Logs page. Thanks.
- Copy Link
- Report Inappropriate Content
Hi @Hank21
Is the controller had this feature that when a controller is off the time/date still running? Because it will cause an issue on the voucher that it will not sync. Instead of having the voucher will expired, it will become unlimited time
- Copy Link
- Report Inappropriate Content
wickedcool13 wrote
Hi @Hank21
Is the controller had this feature that when a controller is off the time/date still running? Because it will cause an issue on the voucher that it will not sync. Instead of having the voucher will expired, it will become unlimited time
Thanks for your feedback. If the controller is off, the portal function will be provided by the EAP itself. There are only a few portal options on the EAP itself, not including the voucher. You can refer to this FAQ to find more details.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 4
Views: 8153
Replies: 32
Voters 3
