Early Access Omada SDN Controller_V5.13.30 Pre-release (Updated on Apr 10th, 2024)
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Update as of Apr 10, 2024:
Thank you all for your valuable feedback on the Beta firmware!
The official firmware of 5.13 controller has been released, check the following link for details.
Omada_SDN_Controller_v5.13.30.8_Windows
Omada_SDN_Controller_v5.13.30.8_linux_x64.deb
Omada_SDN_Controller_v5.13.30.8_linux_x64.tar.gz
OC200(UN)_V1_1.29.21 Build 20240401
OC200(UN)_V2_2.14.21 Build 20240401
OC300(UN)_V1_1.22.4 Build 20240304
This Article Applies to
Omada_SDN_Controller_v5.13.30.8 Windows (Windows 7/8/10/11/Server, 64bit Recommended)
Omada_SDN_Controller_v5.13.30.8_Linux_x64.tar.gz (Ubuntu 16.04/18.04/20.04, Debian 8/9/10, CentOS 6/7)
Omada_SDN_Controller_v5.13.30.8_Linux_x64.deb (Ubuntu 16.04/18.04/20.04, Debian 8/9/10)
OC200(UN)_V1_1.29.3_Build 20240131 (Built-in Omada SDN Controller 5.13.30.10)
OC200(UN)_V2_2.14.3_Build 20240131 (Built-in Omada SDN Controller 5.13.30.10)
OC300(UN)_V1_1.22.3_Build 20240131 (Built-in Omada SDN Controller 5.13.30.10)
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. Added support for Layer-3 Switches: SG6428X, SG6428XHP, SG6654X, SG6654XHP, SX6632YF.
2. Added support for Layer-3 Switch features:
- QoS
- VRRP
- OSPF
- STACK
- STP Extension
Enhancement
1. Optimized the PUBLIC IP ADDRESS column in Devices List.
2. Optimized the validation rules for WAN Static IP address, allowing setting to Static IP with a 31-bit network mask.
3. Optimized the Global View for viewer account, allowing users with Viewer permissions to see the Sites they can access in the Global View.
4. Optimized the name of "AI WLAN Optimization" to "WLAN Optimization", removed the Schedule module.
5. Optimized the PMF mode automatic selection logic and the prompts when PMF/WPA mode changes.
6. Optimized the Controller version number to 4 digits, the Backup files are compatible when the first three digits are identical, improving Site import and migration.
7. Optimized the clarity of some texts and icons in Dark mode.
8. Optimized the logic of the authentication logs update.
Bug Fixed
1. Fixed the issue that configuration can’t be sent to the Router and reports “The configurations of device are different from the configuration from the controller”.
2. Fixed the issue that some models’ firmware can’t be upgraded online, but only through manual upgrade.
3. Fixed the issue that the clients can’t connect the SSID with MAC Filtering under some certain configuration steps.
4. Fixed the issue that Controller takes up a lot of disk space after running for a long time.
5. Fixed the issue that LTE models lose the Internet after changing the Rate Limit via Open API.
6. Fixed the issue that the Tx Power (EIRP) setting of the EAP changes to High after the reboot, although the actual EIRP maintains.
7. Fixed the issue that Batch Config of WLAN Group doesn’t work for EAPs.
8. Fixed the issue of the display error of some models in Device Map.
9. Fixed the issue of failing to create SSID via Open API.
Note
1. As this version optimizes the WAN/LAN port configuration of Omada Gateway, it will cause some WAN ports to be enabled by default and cannot be disabled. This may result in changes to the load balance configuration, you can make the changes manually.
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.13.30.4_Windows(Pre-release version)
Omada_SDN_Controller_v5.13.30.8_Windows
Omada_SDN_Controller_v5.13.30.4_Linux_x64.deb(Pre-release version)
Omada_SDN_Controller_v5.13.30.4_Linux_x64.tar.gz(Pre-release version)
Omada_SDN_Controller_v5.13.30.8_linux_x64.deb
Omada_SDN_Controller_v5.13.30.8_linux_x64.tar.gz
OC200(UN)_V1_1.29.3_Build20240131 (Pre-release version) > Built-in Omada SDN Controller 5.13.30.10
OC200(UN)_V2_2.14.3_Build20240131 (Pre-release version) > Built-in Omada SDN Controller 5.13.30.10
OC300(UN)_V1_1.22.3_Build20240131 (Pre-release version) > Built-in Omada SDN Controller 5.13.30.10
-
Download From TP-Link Global "EN" Website:
Omada Controller_Windows/Linux: https://www.tp-link.com/en/support/download/omada-software-controller/
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 28th, 2024:
Update the Omada Software Controller (Linux) beta version to official release.
-
Before
Omada_SDN_Controller_v5.13.30.4_Linux_x64.deb(Pre-release version)
Omada_SDN_Controller_v5.13.30.4_Linux_x64.tar.gz(Pre-release version)
-
After
Omada_SDN_Controller_v5.13.30.8_linux_x64.deb
Omada_SDN_Controller_v5.13.30.8_linux_x64.tar.gz
Feb 7th, 2024:
Add the following controller firmware for early access.
- OC200(UN)_V1_1.29.3_Build 20240131 (Built-in Omada SDN Controller 5.13.30.10)
- OC200(UN)_V2_2.14.3_Build 20240131 (Built-in Omada SDN Controller 5.13.30.10)
- OC300(UN)_V1_1.22.3_Build 20240131 (Built-in Omada SDN Controller 5.13.30.10)
Update the Omada Software Controller (Windows) beta version to official release.
-
Before
Omada_SDN_Controller_V5.13.30.4_Windows(Pre-release version)
-
After
Omada_SDN_Controller_v5.13.30.8_Windows
Jan 9th, 2024:
Add the following controller firmware for early access.
-
Omada_SDN_Controller_v5.13.30.4_Linux_x64.deb(Pre-release version)
-
Omada_SDN_Controller_v5.13.30.4_Linux_x64.tar.gz(Pre-release version)
Jan 8th, 2024:
Provide the following controller firmware for early access.
-
Omada_SDN_Controller_V5.13.30.4_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 OC200 Update? It's been almost a month....
We are still missing alot of things like WOL, DHCP Reservations (be able to set DNS for each reservation as well) ....... Maybe if you guys cannot add this DNS feature you should remove the need to ENFORCE a DHCP....... I'll run DHCP from my Windows Server or whatever that has this function you haven't added since you started this.
- Copy Link
- Report Inappropriate Content
@MrHC1983 Well, when it comes to flexibility of features, the software controller is probably the best bet for this since the devs can just add more and more features to it coz they are not limited to the specs of the hardware that will run it, considering its upgradability.
But for the hardware controllers, the devs are sure taking their time adding new features to it since they are limited to its fixed hardware specs.
That's why until now, the DPI feature is still not added to the hardware controllers, even the IPS/IDS feature is currently (as the devs said before) not supported due to the hardware limitations of the controllers.
- Copy Link
- Report Inappropriate Content
@MrHC1983 Per this post the OC200 does not support DPI (part of the IDS/IPS functionality). Unless there is a recent firmware update that added DPI for the hardware controllers. If you have a screenshots of BOTH the following in the OC200 then they must have very recently added DPI to the hardware controllers:
I truly hope you are correct as tp-link's messaging around this has been unclear at best and I never understood why the hardware controllers could not support this function since it was the router doing all the hard work.
- Copy Link
- Report Inappropriate Content
@OrangeStreet You would be correct, I certainly don't have DPI....... on my OC200.
If I turn on IDS/IPS etc when on Gigabit my speed which averages around 890-940Mbps down will drop to around 200-250...... so I leave it off except for overnight which seems to be when the majority of attacks occur anyway.
I'm wondering however, if I moved the Omada gear to a Linux based controller, with IDS/IPS on would it improve that speed?.....
Seems to me TPLink need to release an updated hardware controller. I like my OC200 in terms of it's size, I would of perfered it not have USB power....... I know it takes POE but having just a standard power back for the rear power would have been better.
So a new hardware controller the size of the OC200 would be nice....... plenty of new chips out there to power the thing.
I am not a fan of software controllers because if the server/vm's go down.... ya stranded and don't want a cloud controller because it costs money so.
- Copy Link
- Report Inappropriate Content
@MrHC1983 When I switched to a software controller and more importantly upgraded the router to the er8411 I haven't seen any significant decrease in throughput and expect that it could handle a multi-gig WAN setup with IDS/IPS enabled - I don't think the controller is the bottleneck in your case, probably the router. I'm completely with you on the need for a higher performing controller - I simply do not understand how these new features can be released without a corresdonding hardware controller that could support it - this problem cost me money as DPI was a required feature I needed to block torrents to prevent tenants from downloading illegal movies and I had the OC300 which doesn't support DPI either. They need to release some kind of "enterprise" or "pro" version that can - an "OC500 Enterprise" or some such thing IMO. The really annoying part is I don't see anywhere in the sales material that states the OC hardware models will not support the DPI feature unless this has finally been updated. It's a bit misleading.
- Copy Link
- Report Inappropriate Content
OC400 is here. perhaps a bit much OC for a small home network.. 
https://www.tp-link.com/en/business-networking/omada-controller-hardware/oc400/
- Copy Link
- Report Inappropriate Content
Why not go with a mini-PC with a newer gen Intel or AMD processor coupled with lots of memory and run it as an Omada software controller? Mini-PC's use very little power and the sky is the limit as far as processing power. Mini-PC's can be run 24x7, most use under 30-40W of power. Should never go down (unless you have a power outage). Either that, or use the Cloud option (understand that it's not free, but you get what you pay for). I run a Windows 11 Intel NUC mini-PC w/32GB of RAM and an Intel N5105 quad-core CPU...I wouldn't recommend it as a gaming PC but for running the Omada software controller it's WAY more than enough. I took a snapshot of what I'm running...CPU utilization is generally below 20% (that's with 75 clients on my network) and I rarely see the memory utilization go above 2GB for the Omada process itself. Only time this mini-PC has ever gone down is for reboots after Windows patches. Not a big deal. Otherwise it's up all the time and is super reliable. You can find N5105 mini-PC's online for as low as $100 w/16GB of RAM and Win 11 Pro preinstalled.
The controllers don't really affect throughput or network performance, but I remember the hardware controllers are limited in terms of number of clients they can accommodate. The OC200 is designed for portability and to accommodate common small home networks. I'd 100% recommend going with the software or cloud-based controller for larger-scale home or small biz networks.
- Copy Link
- Report Inappropriate Content
@MR.S it's still "coming soon" at least in my region (US) - however this looks like a much better option for a network like mine. There is still no documentation that says it will work with DPI so I'd be real sure to ask that BEFORE you buy it or you'll get stuck doing what I had to do (buy a PC for a dedicated software controller). I would hope a device with the specs it shows would be plenty! Thanks for the link!
- Copy Link
- Report Inappropriate Content
Buy a raspberry pi5, I bought one now that I run unifi controller and wireguard server on, it's super fast.
about the same size as the OC200
I run Omada on a Windows PC that runs some other services and is on 24/7 anyway..
- Copy Link
- Report Inappropriate Content
yes, and the OC400 is a waste of money for a small home network. but as I suggested, buy a raspberry pi5 4GB then you have a super fast controller that can also install other things on
- Copy Link
- Report Inappropriate Content
Information
Helpful: 2
Views: 21633
Replies: 63
Voters 1
