Beta Software Omada SDN Controller_V5.13 Beta (Updated on Feb 22nd, 2024) [Thread Closed]
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
Hello @Spucoly,
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 TKID231223701, 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
@Hank21 Hope you havent missed this comment: https://community.tp-link.com/en/business/forum/topic/628384?replyId=1289786
Also, not sure if related to newest beta, but:
It seems instead of 120 minutes lease clients only get 120 seconds lease
I am getting 10k logs full due to this, spamming DHCP Allocations
Running newest stable firmware v2.2.2 on my completely new ER605 V2
PS: Also posted here: Single device keeps requesting IP on ER605 V2 since upgrade to 2.1.2 - Business Community (tp-link.com)
- Copy Link
- Report Inappropriate Content
Hi @pdu_,
pdu_ wrote
Hope you havent missed this comment: https://community.tp-link.com/en/business/forum/topic/628384?replyId=1289786
Thanks for posting this issue to our community, I have escalated it to the R&D department for further investigation, will update here if I have the progress.
pdu_ wrote
It seems instead of 120 minutes lease clients only get 120 seconds leaseI am getting 10k logs full due to this, spamming DHCP Allocations
PS: Also posted here: Single device keeps requesting IP on ER605 V2 since upgrade to 2.1.2 - Business Community (tp-link.com)
Your can find the answer by @Clive_A in the original post here.
- Copy Link
- Report Inappropriate Content
Hi @Hank21
I'm not trying to adopt, I simply upgrade my docker from 5.12.7 to 5.13.22, then the controller keep trying to adopt my ER7206.
I've tried to adopt my 7206 from that new docker or from a new Windows controller 5.13.22, both won't work.
When I install a new 5.12.7 in Windows, everything works fine, upgraded to 5.13.22, disaster came back, total network down.
I then installed 5.12.7 in docker, everything works right away.
I do not have OC200/300. Migrate from 5.13.22 Windows to 5.13.22 docker totally failed.
Migrate from 5.12.7 Windows to 5.12.7 docker worked well.
Thanks,
Lawrence
- Copy Link
- Report Inappropriate Content
Hi @llccllcc,
llccllcc wrote
I'm not trying to adopt, I simply upgrade my docker from 5.12.7 to 5.13.22, then the controller keep trying to adopt my ER7206.
Did this issue also occur on other devices like your EAPs?
May I know the hardware versions and the firmware versions with the Build number of your ER7206 and EAPs?
llccllcc wrote
I've tried to adopt my 7206 from that new docker or from a new Windows controller 5.13.22, both won't work.
Could you elaborate on the issue phenomenon? Keep trying to adopt? Or Adopt Failed? What is the Error message?
llccllcc wrote
I do not have OC200/300. Migrate from 5.13.22 Windows to 5.13.22 docker totally failed.
Could you share the error message with us? Which Migration did you do? Controller Migration or Site Migration?
- Copy Link
- Report Inappropriate Content
@Hank21 Few more questions...
Can you maybe explain which DNS is exactly being used in DNS Proxy settings ?
e.g. What the heck is Quad9_1 and _2, that is the difference ?
Also, are they queried in parallel or what is the logic behind, what is the priority etc..
Help center info is very vague tbh.
In general I think everyone would appreciate parallel querying and the fastest reply is sent to the client ASAP. - or make it configurable.
As for DNS Cache, is the caching optimistic and so the cache is updated on every request if there is a change, or is it basically that if entry is cached for defined amount of time, its not updated at all just served ?
Would it be possible to also implement rewrites, such as when using wildcard domain for reverse proxy running behind omada gateway, let us configure this domain to serve local IP of the server directly.
Thanks !
- Copy Link
- Report Inappropriate Content
Thanks but I was looking for a detailed comparison, for example:
"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)"
Is there a detailed comparison of the current controllers versions? If not, one has to go throuh every changelog of every release of every controller to see if a feature has been added to the specific controller. If a costumer choosing a product later finds out that specific feature he was counting on is not avaiable, dispite burried in a changelog somewere, hes not going to be happy.
- Copy Link
- Report Inappropriate Content
@Hank21 Version 5.13.22 and the controller is in a docker. I factory reset all devices and readopted them with nop change
- Copy Link
- Report Inappropriate Content
Hi @pdu_,
Regarding the issues/doubts/suggestions, since they cover different aspects and don't have much to do with the controller firmware in this thread, I'd encourage you click here to start a new thread to elaborate on one issue each time, so that we can stay topic and help you get the answers or solutions quickly, which may also help others who are interested in the topic. Thank you for your understanding and cooperation. See you in the forums soon!
- Copy Link
- Report Inappropriate Content
Hi @Gogan,
Currently, you can identify new features and bug fixes for each version of Controller is to look at the Release Note for each version.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 5
Views: 39832
Replies: 130