Early Access Omada SDN Controller_V5.14.32 Pre-release (Updated on Nov 8th, 2024)
This Article Applies to
Omada_SDN_Controller_v5.14.32.3 Windows (Windows 7/8/10/11/Server, 64bit Recommended)
Omada_SDN_Controller_v5.14.32.3_linux_x64.tar
Omada_SDN_Controller_v5.14.32.3_linux_x64.deb
OC200(UN)_V1_1.32.6_pre-release (Built-in Omada SDN Controller 5.14.32.56)
OC200(UN)_V2_2.17.6_pre-release (Built-in Omada SDN Controller 5.14.32.56)
OC300(UN)_V1_1.26.6_pre-release (Built-in Omada SDN Controller 5.14.32.56)
OC400(UN)_V1_1.4.6_pre-release (Built-in Omada SDN Controller 5.14.32.56)
Overview
We hope to offer you a chance to experience the new features added in the Controller v5.14.20 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 letting us know about successful upgrades.
Release Notes
New Features
1. Added support for gateways: ER8411 v1.2, ER7412-M2 v1.2, ER706W v1.2, ER605 v2.2.
2. Added support for APs: EAP 772 v2.
3. Added support for Controller IP Access Rules in Global View > Settings > Account Security.
4. Added support for Upgrade Logs, Upgrade Schedules, Beta Firmware Program, Cloud Firmware Pool and other function in Global view > Firmware.
5. Added support for Audit Logs unit in Global View: user’s operations will be recorded to facilitate system maintenance.
6. Added support for configuring following features with Omada APP:
- Bandwidth Control
- Deep Packet Inspection
- IPS/IDS
- IP Group
- MAC Filtering
- Dynamic DNS
- WLAN Optimization
- Load Balancing
Enhancements
1. Optimized Backup, added support of selection of configurations and data.
2. Optimized Restore, data is no longer supported to be kept after restoring backup file, only configurations can be kept.
3. Optimized distribution of Export Data, added support for exporting data in the corresponding features module directly.
4. Optimized adaptability to SSL certificate, added support for importing certificate chain file of PEM format in Global view > Settings > System Settings > HTTPS Certificate.
5. Optimized default settings, enabled Fast Roaming, Gateway LLDP automatically.
6. Optimized the stability when using the terminal of devices.
7. Optimized the performance when managing clients in huge scale.
8. Optimized the Upgrade Schedule, added support to select model for upgrading, not single device anymore.
Notes
1. This version of the Controller is fully applied to the Omada APP of version 4.17 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. Since version 5.14.32.2, Omada Software Controller no longer supports upgrade from Controller v4.
4. Since version 5.14.32.2, Omada Software Controller(windows) only supports installation on Windows64-bit platform.
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 upgrading or downgrading.
(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_Controller_Windows_v5.14.32.3
Omada_SDN_Controller_v5.14.32.3_linux_x64.tar
Omada_SDN_Controller_v5.14.32.3_linux_x64.deb
OC200(UN)_V1_1.32.6 (pre-release version) > Built-in Omada SDN Controller 5.14.32.56
OC200(UN)_V2_2.17.6 (pre-release version) > Built-in Omada SDN Controller 5.14.32.56
OC300(UN)_V1_1.26.6 (pre-release version) > Built-in Omada SDN Controller 5.14.32.56
OC400(UN)_V1_1.4.6 (pre-release version) > Built-in Omada SDN Controller 5.14.32.56
Omada_Controller_Windows_v5.14.32.2 (Pre-release version)
Omada_Controller_Windows_v5.14.32.2
Omada_SDN_Controller_v5.14.32.2_linux_x64_20240920174215.tar
Omada_SDN_Controller_v5.14.32.2_linux_x64.tar.gz
Omada_SDN_Controller_v5.14.32.2_linux_x64_20240920174223.deb
Omada_SDN_Controller_v5.14.32.2_linux_x64.deb
OC200(UN)_V1_1.32.5 (pre-release version) > Built-in Omada SDN Controller 5.14.32
OC200(UN)_V2_2.17.5 (pre-release version) > Built-in Omada SDN Controller 5.14.32
OC300(UN)_V1_1.26.5 (pre-release version) > Built-in Omada SDN Controller 5.14.32
OC400(UN)_V1_1.4.5 (pre-release version) > Built-in Omada SDN Controller 5.14.32
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 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
Nov 8th, 2024:
Add the following controller firmware for early access.
- OC200(UN)_V1_1.32.6 (pre-release version) > Built-in Omada SDN Controller 5.14.32.56
- OC200(UN)_V2_2.17.6 (pre-release version) > Built-in Omada SDN Controller 5.14.32.56
- OC300(UN)_V1_1.26.6 (pre-release version) > Built-in Omada SDN Controller 5.14.32.56
- OC400(UN)_V1_1.4.6 (pre-release version) > Built-in Omada SDN Controller 5.14.32.56
Update the Omada Software Controller pre-release version to the official release.
Oct 30th, 2024:
Remove download links for all the controllers 5.14.32.
Oct 28th, 2024:
Add the following controller firmware for early access.
- OC200(UN)_V1_1.32.5 (pre-release version) > Built-in Omada SDN Controller 5.14.32
- OC200(UN)_V2_2.17.5 (pre-release version) > Built-in Omada SDN Controller 5.14.32
- OC300(UN)_V1_1.26.5 (pre-release version) > Built-in Omada SDN Controller 5.14.32
- OC400(UN)_V1_1.4.5 (pre-release version) > Built-in Omada SDN Controller 5.14.32
Update the Omada Software Controller pre-release version to the official release.
Sep 26th, 2024:
Provide the following controller firmware for early access.
- Omada_Controller_Windows_v5.14.32.2 (Pre-release version)
- Omada_SDN_Controller_v5.14.32.2_linux_x64_20240920174215.tar
- Omada_SDN_Controller_v5.14.32.2_linux_x64_20240920174223.deb
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
- Copy Link
- Report Inappropriate Content
I would imagine the reason it was taken down entirely was due to the reasons myself and a few others have reported - under some circumstances, it is deleting and resetting WAN port settings killing internet connectivity - especially on remote managed sites
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
@Vincent-TP Aren't the two firmwares incompatible? So backing up the config files will be useless?
- Copy Link
- Report Inappropriate Content
Quick question: is the FW still suspended or safe to use now? Controller shows me this version as update but have not seen any unblock notification in the forum (perhaps overlooked).
Thanks & Br's
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
@Vincent-TP Is there an estimated date for when the firmware will be available to download again?
- Copy Link
- Report Inappropriate Content
Thanks! Was unsure due the problem mentioned re. ISP login credentials on different sites. Exactly my use case.
Will give it a try then.
- Copy Link
- Report Inappropriate Content
So far I haven't encountered any problems since I applied the firmware.
I must admit that I'm really enjoying this new experience.
I decided to abandon the software on my computer to use an OC200 controller. When I realized that it didn't have what was in the software, I was very disappointed and even tried to understand.
I saw a post that made my eyes shine and my hope was greatly rekindled when I saw someone from TP-Link respond that they were working internally to make one of the features available, DPI.
When I was browsing the forum a little after 10/28, I came across this post and in the notes I saw a bunch of new features including DPI. Ask me how I felt? Like a child and super happy with TP-Link's competence.
I didn't have much time to assess the wonders introduced in the product, but I really must congratulate them.
I would like to make two suggestions for the OC200:
1- Storing logs on a USB flash drive - I see that the product saves logs locally and that this ends up being somewhat limited due to space constraints. Is it possible to enable the storage of logs on a USB flash drive?
2- I see in the logs that the TCP SYN attack blocks are effective. However, I cannot identify the device that is generating these attacks.
Ex.: 2024-11-07 17:11:13 DEVICE WARNING [gateway:ROUTER:00-00-00-00-00-00] Detected TCP SYN packets attack and dropped 101 packets.
Is it possible to do something to identify the source in the log itself? I would really like TP-Link to provide this information in the logs.
Now I have a question.
What are these Webhooks? I still don't understand what they are for, but the idea sounds very similar to APIs.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Information
Helpful: 1
Views: 8009
Replies: 55
Voters 1
