Beta Software Omada SDN Controller_V5.13 Beta (Updated on Feb 22nd, 2024) [Thread Closed]
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Update as of Feb 22nd, 2024:
The 5.12 beta has been updated to official release, and this early access post is locked for further replies.
Omada Software Controller_V5.13.22 (Released on Nov 23rd, 2023)
Omada Hardware Controller_V5.13.24 (Released on Feb 22nd, 2024)
Any further questions or assistance needed with Omada SDN Controller, please feel free to contact TP-Link Tech Support by submitting a support ticket or connect with community by clicking Start a New Thread in the Business Community forums.
This Article Applies to
Omada_SDN_Controller_v5.13.22 Windows (Windows 7/8/10/11/Server, 64bit Recommended)
Omada_SDN_Controller_v5.13.10_Linux_x64.tar.gz (Ubuntu 16.04/18.04/20.04, Debian 8/9/10, CentOS 6/7)
Omada_SDN_Controller_v5.13.10_Linux_x64.deb (Ubuntu 16.04/18.04/20.04, Debian 8/9/10)
OC200(UN)_V1_1.28.1_Build 20231117 (Built-in Omada SDN Controller 5.13.24)
OC200(UN)_V2_2.13.1_Build 20231117 (Built-in Omada SDN Controller 5.13.24)
OC300(UN)_V1_1.21.1_Build 20231117 (Built-in Omada SDN Controller 5.13.24)
Overview
We hope to offer you with a chance to experience the new features added in the Controller v5.13 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. Expanded Language Support: Added language support for Română, Български, Українська, Српски.
2. 2FA: Added support for Two-Factor Authentication (2FA) in Global view > Account Security, all accounts will be asked for extra authentication to log in for higher account security.
3. DPI: Added support for Deep Packet Inspection in Site view > Settings > Network Security > Application Control, which helps you to manage your network traffic through Application Layer. (except the OC200 and OC300)
4. Batch Delete VLAN: Added support for Batch Delete VLAN in Site View > LAN, which allows you to delete mutiple VLAN at once.
5. Remember Device: Added support for remember of devices in Site View > Devices-Sidebar > Config-General, which allows your Controller to remember this device and automatically adopt it after it is reset and being found by your Controller.
6. Application result: Added support for display of application result of devices configuration in Site View > Devcies.
Enhancement
1. Device: Added support for hyperlink of uplink and downlink devices, which will jump to specific devcie page after you click the link. Besides, support more downlink information display in Switch > Details.
2. Sorting Optimization: Optimized sorting for the following locations:
- Firmware Version.
- DHCP Reservation.
- LAN Network.
3. Voucher Groups: Added support for code format of English Letters.
Notes
1. This version of the Controller is fully applied to the Omada APP of version 4.13 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. 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 Beta 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.13.22_Windows(Beta)
Omada_SDN_Controller_v5.13.10_Linux_x64.deb(Beta)
Omada_SDN_Controller_v5.13.10_Linux_x64.tar.gz(Beta)
Omada_SDN_Controller_V5.13.22_Windows
Omada_SDN_Controller_v5.13.22_Linux_x64.deb
Omada_SDN_Controller_v5.13.22_Linux_x64.tar.gz
OC200(UN)_V1_1.28.1_Build 20231117 (Beta) > Built-in Omada SDN Controller 5.13.24
OC200(UN)_V2_2.13.1_Build 20231117 (Beta) > Built-in Omada SDN Controller 5.13.24
OC300(UN)_V1_1.21.1_Build 20231117 (Beta) > Built-in Omada SDN Controller 5.13.24
OC200(UN)_V1_1.28.2 Build 20240110 Full Release Note >
OC200(UN)_V2_2.13.2 Build 20240110 Full Release Note >
OC300(UN)_V1_1.21.2 Build 20240110 Full Release Note >
-
Download From TP-Link Global "EN" Website:
Omada Controller_Windows/Linux: https://www.tp-link.com/en/support/download/omada-software-controller
OC200 v1/v1.6: https://www.tp-link.com/en/support/download/oc200/v1/#Firmware
OC200 v2/v2.6: https://www.tp-link.com/en/support/download/oc200/v2/#Firmware
OC300 v1/v1.6: https://www.tp-link.com/en/support/download/oc300/#Firmware
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
Feb 22nd, 2024:
Update the OC200 v1/v2 and OC300 v1 beta firmware to official release.
-
Before
OC200(UN)_V1_1.28.1_Build 20231117 (Beta) > Built-in Omada SDN Controller 5.13.24
OC200(UN)_V2_2.13.1_Build 20231117 (Beta) > Built-in Omada SDN Controller 5.13.24
OC300(UN)_V1_1.21.1_Build 20231117 (Beta) > Built-in Omada SDN Controller 5.13.24
-
After
OC200(UN)_V1_1.28.2 Build 20240110 (Built-in Omada SDN Controller 5.13.24)
OC200(UN)_V2_2.13.2 Build 20240110 (Built-in Omada SDN Controller 5.13.24 )
OC300(UN)_V1_1.21.2 Build 20240110 (Built-in Omada SDN Controller 5.13.24 )
Nov 23rd, 2023:
Update the Omada Software Controller beta version to official release.
-
Before
Omada_SDN_Controller_V5.13.22_Windows(Beta)
Omada_SDN_Controller_v5.13.10_Linux_x64.deb(Beta)
Omada_SDN_Controller_v5.13.10_Linux_x64.tar.gz(Beta)
-
After
Omada_SDN_Controller_V5.13.22_Windows
Omada_SDN_Controller_v5.13.22_Linux_x64.deb
Omada_SDN_Controller_v5.13.22_Linux_x64.tar.gz
Nov 21st, 2023:
Add the following controller firmware for early access.
- OC200(UN)_V1_1.28.1_Build 20231117 (Beta) > Built-in Omada SDN Controller 5.13.24
- OC200(UN)_V2_2.13.1_Build 20231117 (Beta) > Built-in Omada SDN Controller 5.13.24
- OC300(UN)_V1_1.21.1_Build 20231117 (Beta) > Built-in Omada SDN Controller 5.13.24
Nov 3rd, 2023:
Update the newer Windows Omada Software Controller beta version.
-
Before
Omada_SDN_Controller_V5.13.9_Windows(Beta)
-
After
Omada_SDN_Controller_V5.13.22_Windows(Beta)
Oct 27th, 2023:
Add the following controller firmware for early access.
- Omada_SDN_Controller_v5.13.10_Linux_x64.deb(Beta)
- Omada_SDN_Controller_v5.13.10_Linux_x64.tar.gz(Beta)
Oct 8th, 2023:
Provide the following controller firmware for early access.
- Omada_SDN_Controller_V5.13.9_Windows(Beta)
Recommended Threads
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
Hi @akikoy,
This issue has been reported to the engineer for further investigation. I'll try to provide an update when there's progress.
- Copy Link
- Report Inappropriate Content
I just purchased the OC200 and no longer have the DPI feature - debating on returning this and going back to the software. Will DPI be enable on the hardware controller anytime soon?
- Copy Link
- Report Inappropriate Content
Hi @pmootrey，
Thanks for your valuable feedback.
After confirming with the Support team, the DPI is not supported for hardware controllers due to hardware limitation.
Please note that the information provided here is based on the current information we have, it's provided for informational purposes only, not a guarantee or a promise. Any plans are subject to change, the final firmware releases shall prevail.
- Copy Link
- Report Inappropriate Content
Hi,
For Hardware versions of OC200/OC300 software is being optimized to support DPI. This is planned for Q1/2024. It is under development, so we will inform you of any changes.
- Copy Link
- Report Inappropriate Content
We are having a problem with the login timeout feature on 5.13.22, it's causing a problem because we have not found a way to turn it off.
When a 5.13.22 Windows Controller in running in a container on a remote on-property Win 11 Pro Server and is connected via a pipe to a local central server to a local Edge Web page when the Controller looses access to the pipe (between the container and the off property central server due to a network data transport issue), and it times out, the only way to recover is to restart the remote controller process. If the controller does NOT time out, there is no issue at recovering the pipe connection. We could host the controller in the native environment and log back in after timeout not protected in a container and remote desktop in the server but this looses isolation and protection features provided by the container and the headless features of the pipe.
There are two solutions
1) run a local version of Edge Web page on the remote system and remote desktop into the server. After a timeout delete the tab and start a new again and log back in.
2) Run a space / backspace ever 10 minutes if the pipe does see any traffic from the user who signed in to prevent a login timeout.
-Or-
3) Did I miss the setting to turn off the auto log out setting perhaps under site management.
This auto log out forced us to quit using the local controller Radius server to connect our hotel key system into user guest password settings for hotel guest. I was trying to use our Hotel Guest Database for Hotel Management and connect the Key System to the guest ledger for WiFi authorization. I am going to be forced to go back to using an external Radius Server to make it happen. When you introduced the internal Radius Server it made things easy. When the login timeout feature was introduced, IT BROKE THINGS, if the data connection failed. If it doesn't time out, recovery is handled by the pipe. The pipe can't recover if one end is gone due to the Java timeout feature.
I was trying to avoid setting up yet another Radius application, and database and plumbing to connect everything so it is self healing.
We are currently using a another SDN network system at our properties and are trying to come up with a less expensive solution and it is not easy to connect the Hotel guest ledger database to the SDN guest user database. The system must be self healing, idiot proof, and isolated and protected from intrusion. Keeping stuff in containers, encrypted, and locally headless helps make it idiot and hack resistant.
- Copy Link
- Report Inappropriate Content
Hi All,
A newer 5.13.30.4 Beta firmware of Windows Controller has been released for trial, please follow the post link below for details.
Omada SDN Controller_V5.13.30.4 Beta (Released on Jan 8th, 2024)
Edit:
Add the following controller firmware for early access.
- Omada_SDN_Controller_v5.13.30.4_Linux_x64.deb(Beta)
- Omada_SDN_Controller_v5.13.30.4_Linux_x64.tar.gz(Beta)
Please find the Firmware Download Link from this post.
- Copy Link
- Report Inappropriate Content
@Hank21
After you upgrade the firmware to 5.13, will i able to access the cloud server? It say on the before upgrade (4) The following beta firmware cannot be upgraded via TP-Link cloud access, please access the controller through the local IP for the manual upgrade option. And you can't access your controller via TP-Link cloud after you install the following 5.13 firmware. Im using cloud server for controlling the hardware. I want to make sure before i will upgrade the firmware that im using right now
- Copy Link
- Report Inappropriate Content
@Hank21 How about for hardware controllers? Any final version of this beta?
- Copy Link
- Report Inappropriate Content
Hi @wickedcool13,
What kind of controller do you have?
If you have the software controller, they have released the official version.
If the controller you have is OC, and yes, it supports the Cloud website accessible.
- Copy Link
- Report Inappropriate Content
Hi @ceejaybassist，
Thank you for your feedback. Each firmware will need to pass a full testing phase before the release, which would take a long time. And the entire firmware development of OC200/OC300 usually takes longer time than that of the Omada Software Controller as further adjustment and optimization will be required on the OC200/OC300 firmware. Sorry to keep you waiting. Hope the official firmware for OC200/OC300 is available soon.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 5
Views: 38913
Replies: 134
Voters 4
