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
@OrangeStreet That's what they said before, at least on paper. They recently released the DPI feature for the ER605 v2, which they also said before that its hardware does not support. So, fingers crossed, there's still hope for the hardware controllers to support DPI since the lowest gateway in the Omada lineup now has DPI support. I hope it will be included in the next update though. The devs sure are taking their time releasing firmware updates for the hardware controllers.
- Copy Link
- Report Inappropriate Content
Update on 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
- Copy Link
- Report Inappropriate Content
@Hank21 Still no DPI with this pre-release of OC?
- Copy Link
- Report Inappropriate Content
Just updated to 5.13.30.8 SDN for Windows...the controller upgraded successfully.
I did notice that after I updated to 5.13.30.8, then logged into the Controller from a web browser, I was presented with another upgrade notification, and a download link which downloaded "Omada_Controller_Windows_v5.13.30.8_1707096437336.zip." The exe within the download is the exact same size, the zip was simply missing the documentation. Seems like a temporary glitch as I logged in a few minutes later and was not prompted with another download notification.
Otherwise the latest release seems to be working well.
- Copy Link
- Report Inappropriate Content
Seriously how do they not fix a bug I've reported like a month or two ago on a new firmware????
Known Clients -> Sort by Download........... MAC ADDRESS DOES NOT MATCH CLIENT!
Omada Pre Release v5.13.30.8
- Copy Link
- Report Inappropriate Content
Hi @Hank21, yesterday I upgraded my OC200 v1 controller to 'OC200(UN)_V1_1.29.3_Build 20240131 (Built-in Omada SDN Controller 5.13.30.10)'. Since then I notice that some of my access point are shown as clients in the Known Clients overview, once they start in the morning (with PoE Time Range). Please see below surrounded in red. Note the name of the last two access points, 'EAP225-Outdoor-B0-4E-26-E5-2B-B8' and 'EAP230-Wall-84-D8-1B-61-24-12'.
Also, surrounded in blue I regularly notice three clients with almost similar MAC addresses showing up, while these clients are not in my network (all clients in my network have IP MAC Binding and DHCP Reservation).
Do you have any idea why this is happening?
- Copy Link
- Report Inappropriate Content
Can we please make it a priority for TPLINK to make the config file transferable to ANY controller........
So if I want to switch between my OC200, Windows, Linux ........... that it just WORK when I download a config retaining all info and try and upload it to another. After all the ENTIRE point of the Omada system is how simple it is to adopt new products......... so it should also be just as simple to move from one controller to another.
- Copy Link
- Report Inappropriate Content
Can anyone tell me what's the context behind the IP Address and Public IP Address columns?
Should they really be the same?
Or should the IP Address be the LAN IP address given by the DHCP server, and the Public IP Address be the WAN IP address given by the ISP?
- Copy Link
- Report Inappropriate Content
Can I just say the difference between the Linux Omada Controller or Windows and the OC200 is nothing.
There's an insinuation that by using something with more power you can use IDS/DPI without such a bandwidth hit, well thats a flat out lie.
I setup a Windows Controller, I setup a Linux Controller and I had my OC200 .......... on the weekend I enabled gigabit internet...... and it made zero difference having more cpu power for the controller.
If I enabled IDS etc........ it was the same hit so it's 100% router limited. In my case being a ER707-M2.......
The OC200 does not have DPI..... but one thing I've learned, all the extra features add latency, you can enable one thing at a time and do a speedtest and watch your download ping and you can see how the router adds latency to filter anything...... even just a DDOS type counting packets........ adds latency. All the packet inspection for x things.
The best thing I did was turn most stuff off........ So I'll stick with my OC200....... It's a gem apart from the startup speed. We run a Linux Controller for work as we have about 4-5 sites attached to it......... but just thought I'd provide some feedback.
If I run gigabit with all the stuff off I run over 900Mbps down.......... if I turn on IDS etc....... it's more like 160-250ish.
- Copy Link
- Report Inappropriate Content
Hi upgrade my OC200v1 with OC200(UN)_V1_1.29.3_Build20240131(Beta) and, now, I can't access controller anyway.
It does not show up on omada cloud nor respond to pings to it's assigned IP.
What should I do now?
Previous version was OC200(UN)_V1_1.28.1_Build20231117(Beta).
EDIT: Upgrade applied successfully. Previous version uploaded using Recovery Mode. Second attempt to upgrade 1_1.29.3_Build20240131(Beta) finished without issues.
Best Regards
- Copy Link
- Report Inappropriate Content
Information
Helpful: 2
Views: 22339
Replies: 63
Voters 1
