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
@Hank21
Theres an issue with the time and date when If theres a blackout and it takes like more than hour for the electricity to be back the time and date will not sync properly and it would cause the voucher to be buggy. Lets say the blackout occurs at 10am and it goes back around 4pm and 5 people have 1 hour voucher with pause time activated, when i checked the time it will stay at the time that the blackout occurs which is 10am instead of 4pm. People who have voucher will have unlimited time instead of having a limited time for 1 hour. Its buggy and i need to resync the controller time in order for the voucher not to be buggy
- Copy Link
- Report Inappropriate Content
I was out of town this week... I finally got back and realized all my wireless vlans were set to 1. Everything was landing in the core.
Everything still worked like usual. But changing the wireless VLAN tag to the Network, fired it back up.
- Copy Link
- Report Inappropriate Content
I tried to backup and restore from one install to another (both this version) but it always fails to restore from the backup. I had to set everything up again manually. Seems like an issue if a backup can't be restored onto the exact same version?
- Copy Link
- Report Inappropriate Content
MrAdministrator wrote
I tried to backup and restore from one install to another (both this version) but it always fails to restore from the backup. I had to set everything up again manually. Seems like an issue if a backup can't be restored onto the exact same version?
Are you using the software controller? What is the version of them? Please help to send the screenshot about the page you browse the backup file and the screenshot of error message. Thanks!
- Copy Link
- Report Inappropriate Content
Hank21 wrote
MrAdministrator wrote
I tried to backup and restore from one install to another (both this version) but it always fails to restore from the backup. I had to set everything up again manually. Seems like an issue if a backup can't be restored onto the exact same version?
Are you using the software controller? What is the version of them? Please help to send the screenshot about the page you browse the backup file and the screenshot of error message. Thanks!
Yeah I am using the 5.14.0.11 Linux deb package. Installed on a RPi 4B on latest OS, trying to restore onto an RPi 5 on latest OS, also with
5.14.0.11 Linux deb package. I have confirmed both report identical versions in System Settings.
I've tried creating and restoring any which-way I can come up with, including from the migration wizard on the RPi 4 controller and importing the backup file during setup of the RPi 5 controller. I have also tried it the way pictured below.
========================================
Backing up from RPi 4 controller
========================================
Restoring onto RPi 5 controller
========================================
Error during restore
========================================
Are there some logs I should look at to see if something is being logged out here?
- Copy Link
- Report Inappropriate Content
Normally this problem occurs to linux, containers and dockers with wrong java lib. only max ver. 11 is allowed to get restore work. with 17 and above restore wont work. Had this problem some time ago. New install and creation works perfectly, what makes the whole thing looks strange...
- Copy Link
- Report Inappropriate Content
kogan wrote
Normally this problem occurs to linux, containers and dockers with wrong java lib. only max ver. 11 is allowed to get restore work. with 17 and above restore wont work. Had this problem some time ago. New install and creation works perfectly, what makes the whole thing looks strange...
This must be the problem. I followed the guide from the thread here to install on RPi, which installs Java 17. I'll try to downgrade Java versions and see if I can get a restore to work
- Copy Link
- Report Inappropriate Content
I confirmed switching java from 17 to 11 solved the restore issue. Sadly java 11 is no longer part of the default app store for debian bookworm, so adding the unstable repository to install it was necessary.
- Copy Link
- Report Inappropriate Content
MrAdministrator wrote
I confirmed switching java from 17 to 11 solved the restore issue. Sadly java 11 is no longer part of the default app store for debian bookworm, so adding the unstable repository to install it was necessary.
Thanks for your update. Our R&D department has noticed this restore issue between Java 17 and the latest several controller versions. And we can expect a new version release in the near future that may resolve this issue. But please note that whether it can be resolved in the near future is not guaranteed. Please keep an eye on the forum or our official website about the updates.
- Copy Link
- Report Inappropriate Content
@Hank21 https://www.tp-link.com/support/faq/3386 tells me "Oops! The page you're looking for can't be found"
- Copy Link
- Report Inappropriate Content
Information
Helpful: 4
Views: 8300
Replies: 32
Voters 3
