Early Access Omada SDN Controller_V5.15.20 Pre-Release Firmware (Update on 20th Mar, 2025)
This Article Applies to
Omada_SDN_Controller_v5.15.20.17 Windows (Windows 10/11/Server, 64bit Recommended)
Omada_SDN_Controller_v5.15.20.16_linux_x64.tar.gz
Omada_SDN_Controller_v5.15.20.16_linux_x64.deb
Overview
We hope to offer you a chance to experience the new features added in the Controller v5.15.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 for Omada SDN Controller
1. Version Info
This version of the Controller is fully applied to the Omada APP of version 4.22 or above.
2. Supported Device Models
For device models Omada Software Controller supports, refer to: Omada Cloud SDN Platform Compatibility List
1) Added support for Gateways supporting double SIM cards: DR3650v-4G v1.0, DR3220v-4G v1.0, ER706W-4G v2.0, ER706WP-4G v1.0.
2) Added support for Switches: IES210GPP v1.0, IES206GPP v1.0, IES208G v1.0, IES206G v1.0, SG5452X v1.0, SG5452XMPP v1.0.
3) Added support for APs: EAP668-Outdoor(EU/US) v1.0, EAP772-Outdoor(EU/US) v1.0.
4) Added support for OLT: DS-P7001-01 v1.0 (firmware update required).
3. New Features
1) Added support for AFC (Automated Frequency Coordination) with EAP772-Outdoor (EU/US) v1.0. The privilege of 6GHz Standard Power will be assigned to Access Points according to the device's location, so the available channels and the power of each channel can be adjusted dynamically.
Here's the guide to configure AFC: Getting Started with AFC.
2) Added support for Service Port Profile in Devices > OLT Properties Window > OLT Settings > PON > Profiles. This feature can help to create a service port automatically and simplify the configuration of the OLT PON unit.
3) Added support for Site/Device Template in Global View > Site Template (Beta). With Site Template, customer can batch manage and edit the configuration of sites bound to the template. With Device Template, customer can batch manage and edit the configuration of devices (currently, Switch & Gateway only) bound to the template. Here's the guide to configure Site/Device Template: How to Configure Site Template Feature on Omada Controller.
4) Added support for Cluster(Beta) in Global View > Settings > Cluster, including Modes as Distributed Cluster and Hot-Standby Backup.
Here are two FAQs: How to Configure Distributed Cluster Mode on Linux Controller
How to Configure Hot-Standby Backup Mode on Omada Controller
5) Added support for Google Authentication (Beta) in Site View > Settings > Portal > Authentication Type. Currently, Google Authentication can only be configured on SSID, and the device type must be Access Point. For Wireless Gateway, firmware compatible with Controller v5.15 is required.
Here's the guide to configure Google Authentication: How to Configure Google Authentication on Local Omada Controller.
6) Added support to display the used and remaining data in Logout Page of Voucher and Local Users Portal.
7) Added support for 'Remember Device' in Site View > Settings > Site Settings > General Configure. After device reset and power-on, the Controller will automatically adopt the device if the controller can find it.
8) Added support to edit Profiles All and Default in Site View > Settings > LAN > Switch Profile.
9) Added support for Role Super Administrator, which can manage all the other roles (except Main Administrator) and the privilege of most features.
10) *Added support to Disable NAT in Site View > Settings > Transmission > NAT.
11) *Added support for LAN DNS in Site View > Settings > Wired & Wireless Network > LAN.
12) *Added support for filtering with content in Site View > Settings > Network Security > URL Filtering. This feature helps network managers to achieve efficient, secure and convenient web access control by integrating a large number of categorized URL libraries.
13) *Added support for SD-WAN in Global View. Users can easily connect multiple gateways together without complicated VPN configuration through SD-WAN in enterprise scenarios.
14) *Added support for ARP Detection on Gateway. When you enable this feature, the dumb terminal can be detected, including POS, printer, etc.
4. Enhancements
1) Optimized dependencies:
Windows: Added support for built-in Java Runtime Environment in Controller, no need for the customer to install and configure Java anymore.
Linux: Added support MongoDB v8.0. Since Linux Controller v5.15.20, JDK below version 17 is no longer compatible.
Here's the guide on how to upgrade the OpenJDK to version 17 on Linux System: How to Upgrade the Dependency Environment for Controller 5.15.20 on Linux System. Here're the guides on how to upgrade MongoDB to version 7 on Linux System: How to Upgrade MongoDB from v3.6 to v4.4 on Linux System, How to Upgrade MongoDB from v4.4 to v7 on Linux System.
2) Optimized WAN Mode. Added support for automatic updates to the Gateway Model when a new model is released.
3) Optimized Portal Logout Page. Added support to show used and remaining data on the Logout page of Voucher/Local User Portal.
4) Optimized MAC Filtering. When adopting devices with MAC filtering enabled, the MAC address of devices will be added into Allow List automatically.
5) *Optimized Gateway ACL. Added support for choice as "! -> !", customer can choose data resources and destinations not in certain marked range, which allows customer to configure more flexible profiles.
6) *Optimized DHCP Reservation. Added support for DHCP option 60, 66 and 138.
7) *Added support for DNS Override in DNS Proxy.
8) *Optimized Attack Defense. Added support to customize the length of large PING.
9) *Optimized Network Transmission. Added support for domain in settings of OpenVPN and Wireguard VPN.
10) *Optimized LAN on the following features: Added support to configure DHCP NEXT SERVER. Added support to edit Default LAN port of gateway.
11) *Added support to display the Device MAC in the WAN port of gateway's properties window.
12) *Added support for a maximum of 512 VLANs.
13) Optimized LDAP Profile in Site View > Settings > Network Profile:
- Added support for the maximum length of strings in Regular DN as 256.
- Added support for the maximum length of strings in Regular Password as 256.
- Added support for the maximum length of strings in Base Distinguished Name as 512.
- Added support for the maximum length of strings in Additional Filter as 512.
- Added support for the maximum length of strings in Group Distinguished Name as 512.
14) Added support to show the PPSK profile of SSID used by a client in Client List.
15) Optimized PoE Utilization chart. The Utilization will be calculated according to the power limit of each port.
16) Added support to enable and disable PoE Adapter Remote Reset in Devices > Properties Window(AP) > Config > General for EAP211-Bridge and EAP215-Bridge. With this function, the EAP can be reset remotely. Customers may choose to turn off this function to avoid it being triggered incorrectly due to a complex wireless environment.
17) Added support for 5000 entries in one Voucher Group.
18) Optimized the following Controller properties:
- Added support for maximum number of reports email sent via Cloud Access as 100.
- Added support for maximum number of reports email sent via SMTP Server as unlimited.
19) *Added support to show DHCP LEASE TIME in Client List. This feature will show the remaining time of this assigned IP address for certain client.
20) *Added support for Downlink chart in Detail unit of Gateway's properties window. Downlink chart will show the information of downstream Omada devices connected to this Gateway
5. Bug Fixed
Reduced potential security risks by forcibly redirecting HTTP requests and responses to HTTPS ones.
Notes
1. These feature with * sign requires gateway's firmware to adapt to Controller v5.15.
2. Please note that Controllers on different platforms may have some differences on features, even their first three digits of the version code are the same. For example, Linux Controller currently supports Cluster Mode but Windows Controller doesn't support it yet.
3. Omada SDN Controller can only manage certain devices running the supported firmware. Please confirm that your device is compatible with the SDN Controller.
4. Since version 5.14.32, Omada Software Controller no longer supports upgrade from Controller v4.
5. Since version 5.14.32, 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_SDN_Controller_v5.15.20.19 Windows (Windows 10/11/Server, 64bit Recommended)
Omada_SDN_Controller_v5.15.20.18_linux_x64.tar.gz
Omada_SDN_Controller_v5.15.20.18_linux_x64.deb
Omada_SDN_Controller_v5.15.20.17 Windows (Windows 10/11/Server, 64bit Recommended)
Omada_SDN_Controller_v5.15.20.16_linux_x64.tar.gz
Omada_SDN_Controller_v5.15.20.16_linux_x64.deb
Omada_SDN_Controller_v5.15.20.13 Windows (Windows 10/11/Server, 64bit Recommended)
Omada_SDN_Controller_v5.15.20.12_linux_x64.tar.gz
Omada_SDN_Controller_v5.15.20.12_linux_x64.deb
Omada_SDN_Controller_v5.15.20.8_windows
Omada_SDN_Controller_v5.15.20.11 Windows (Windows 10/11/Server, 64bit Recommended)
Omada_SDN_Controller_v5.15.20.10_linux_x64.tar.gz
Omada_SDN_Controller_v5.15.20.10_linux_x64.deb
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
Apr 2nd, 2025
Update the download link to the official ones:
Omada_SDN_Controller_v5.15.20.19 Windows (Windows 10/11/Server, 64bit Recommended)
Omada_SDN_Controller_v5.15.20.18_linux_x64.tar.gz
Omada_SDN_Controller_v5.15.20.18_linux_x64.deb
Mar 20th, 2025
1. Update the release note: add some config guides for new features;
2. Update the following controller firmware for early access :
Omada_SDN_Controller_v5.15.20.17 Windows (Windows 10/11/Server, 64bit Recommended)
Omada_SDN_Controller_v5.15.20.16_linux_x64.tar.gz
Omada_SDN_Controller_v5.15.20.16_linux_x64.deb
Feb 26th, 2025
Update the following controller firmware for early access (fixed some known bugs) :
Omada_SDN_Controller_v5.15.20.11 Windows (Windows 10/11/Server, 64bit Recommended)
Omada_SDN_Controller_v5.15.20.10_linux_x64.tar.gz
Omada_SDN_Controller_v5.15.20.10_linux_x64.deb
Feb 18th, 2025
Update the release note of incorrect information.
Jan 24th, 2025
Update the following controller firmware for early access.
Omada_SDN_Controller_v5.15.20.11_pre-release_windows
Provide SDN controller for Linux system:
Omada_SDN_Controller_v5.15.20.10_linux_x64_deb
Omada_SDN_Controller_v5.15.20.10_x64_tar.gz
Jan 17th, 2025
Update the following controller firmware for early access.
Omada_SDN_Controller_v5.15.20.8_pre-release_windows
Jan 10th, 2025
Provide the following controller firmware for early access.
Omada_SDN_Controller_v5.15.20.7_pre-release_windows
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
I am currently using an Omada SDN setup with a Linux-based Omada Controller as the primary controller and an OC200 as the secondary (backup). However, I've noticed that Cluster Mode is not supported on the OC200 at the moment.
I wanted to inquire if there are any plans to support Cluster Mode for the OC200 in a future firmware or software update. It would be great to have the OC200 support this feature to enable a more seamless primary/secondary controller setup.
Has anyone heard anything about this in upcoming updates or have suggestions for alternative configurations that could achieve similar results?
Looking forward to hearing your thoughts!
- Copy Link
- Report Inappropriate Content
Babun-Sikder wrote
I am currently using an Omada SDN setup with a Linux-based Omada Controller as the primary controller and an OC200 as the secondary (backup). However, I've noticed that Cluster Mode is not supported on the OC200 at the moment.
I wanted to inquire if there are any plans to support Cluster Mode for the OC200 in a future firmware or software update. It would be great to have the OC200 support this feature to enable a more seamless primary/secondary controller setup.
Has anyone heard anything about this in upcoming updates or have suggestions for alternative configurations that could achieve similar results?
Looking forward to hearing your thoughts!
@Babun-Sikder
I would recommend a second backup failover Linux-based SDN set up since you can replicate the configurations and run identical Omada controller versions between the two Linux systems. Invest in a cheap mini-PC or use a VDI as your secondary. That way you have identical versions of Omada SDN on both Linux systems, making a move to the secondary seamless. The SDN versions differ somewhat with the hardware and software-based controllers.
- Copy Link
- Report Inappropriate Content
Thanks for the suggestion! I already have a Linux-based Omada controller running, and I also have an OC200 in spare. That’s why I was exploring whether it’s possible to utilize the OC200 as a secondary or failover controller in sync with my Linux setup. If this can be implemented, it would be a great way to put the OC200 to good use while ensuring redundancy.
- Copy Link
- Report Inappropriate Content
Babun-Sikder wrote
Thanks for the suggestion! I already have a Linux-based Omada controller running, and I also have an OC200 in spare. That’s why I was exploring whether it’s possible to utilize the OC200 as a secondary or failover controller in sync with my Linux setup. If this can be implemented, it would be a great way to put the OC200 to good use while ensuring redundancy.
I'm sure it could, if you completely manually configured your OC200 for your network, following the configuration you currently use on your Linux SDN Omada controller. I do not believe you'd be able to just "import" configuration from one to another, it would be completely manual. More of a "cold swap" from your Linux SDN to the OC200. You'd have to re-adopt and re-provision all of your Omada-capable TP-Link devices onto the OC200.
- Copy Link
- Report Inappropriate Content
You're absolutely right—it would likely require a manual setup to configure the OC200 as a fallback, following the current network setup on my Linux SDN Omada controller. The inability to directly import configurations does make it more of a 'cold swap' solution, which would require re-adopting and re-provisioning all TP-Link devices to the OC200.
While it’s not as seamless as having two synced Linux controllers, the OC200 could still serve as a useful emergency fallback option. I appreciate your insight—this helps me weigh whether it’s worth the effort or if I should focus more on enhancing my primary setup’s reliability
- Copy Link
- Report Inappropriate Content
Babun-Sikder wrote
You're absolutely right—it would likely require a manual setup to configure the OC200 as a fallback, following the current network setup on my Linux SDN Omada controller. The inability to directly import configurations does make it more of a 'cold swap' solution, which would require re-adopting and re-provisioning all TP-Link devices to the OC200.
While it’s not as seamless as having two synced Linux controllers, the OC200 could still serve as a useful emergency fallback option. I appreciate your insight—this helps me weigh whether it’s worth the effort or if I should focus more on enhancing my primary setup’s reliability
@Babun-Sikder
Make sure you're utilizing the auto-backup option in Global > Settings > Maintenance. Schedule a Cron job or something to that effect that moves your backup files to a cloud-based storage provider or something more robust (such as a SAN or storage array) on your own LAN to ensure you always have reliable backups just in case you run into major system failure. Assuming you have a recent backup file...if you're concerned about redundancy/backup & restore on an individual LAN it only takes minutes to bring an Omada controller back up after a total failure. If you have a more complicated network layout with hundreds of devices restoration will take a bit more time and effort.
- Copy Link
- Report Inappropriate Content
Added support to configure DHCP NEXT SERVER
Hello - I'm trying to find this configuration option and I can't seem to find where to set it. Has anyone figured this out - Option 66 does not automatically set this (and to be fair - it shouldn't if it's going to follow strict RFC) - but I can't figure out where to set this separately.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
There's a * in front of that line so you have to wait for the gateway firmware update so you can use/see it. If you have an ER7206 v2 there's an EA firmware with some of the new features but I'm not so sure this one is in there.
10) *Optimized LAN on the following features: Added support to configure DHCP NEXT SERVER. Added support to edit Default LAN port of gateway.
Notes
1. These feature with * sign requires gateway's firmware to adapt to Controller v5.15.
Any ETA on the gateways firmwares ? It's pretty hard to test the new features and give you guys feedback without those firmwares.
Thank you !
- Copy Link
- Report Inappropriate Content
Thank you - missed that.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 7
Views: 19899
Replies: 100
Voters 4
