Early Access Hardware Controller (Built-in Omada SDN Controller V5.15.20.26) Pre-release Update on 18th Feb 2025
This Article Applies to
OC200(UN)_V1_1.35.2_pre-release (Built-in Omada SDN Controller 5.15.20.26)
OC200(UN)_V2_2.20.2_pre-release (Built-in Omada SDN Controller 5.15.20.26)
OC300(UN)_V1_1.29.2_pre-release (Built-in Omada SDN Controller 5.15.20.26)
OC400(UN)_V1_1.7.2_pre-release (Built-in Omada SDN Controller 5.15.20.26)
Overview
We hope to offer you a chance to experience the new features added in the Controller v5.15.20.26 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.
Upgrade Note (for OC200 & OC300)
If your built-in Controller version is earlier than v5.14, you can upgrade it by using a method below:
Method 1: Download the latest firmware file, then go to Global View > System Settings > Hardware Controller Firmware > Manual Upgrade and upgrade the firmware to Controller v5.15.20.26 directly.
Method 2: Go to Global View > System Settings > Hardware Controller Firmware, check for upgrade to get and upgrade to Controller v5.14.32, then check for upgrade again to get and upgrade to Controller v5.15.20.26.
Since version 5.14.32, Omada Controller no longer supports upgrades from Controller v4.
READ ME
This software is watermarked: please avoid using in a production environment.
Release Notes
1. Version Info
This version of the Controller is fully applied to the Omada App v4.22 or above.
2. Supported Device Models
- Added support for Gateways supporting dual SIM cards: DR3650v-4G v1.0, DR3220v-4G v1.0, ER706W-4G v2.0, and ER706WP-4G v1.0.
- Added support for Switches: IES210GPP v1.0, IES206GPP v1.0, IES208G v1.0, and IES206G v1.0.
- Added support for Access Points: EAP668-Outdoor(EU/US) v1.0, and EAP772-Outdoor(EU/US) v1.0.
- Added support for OLT: DS-P7001-01 v1.0 (firmware update required).
3. New Features
- 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.
Added support for Cluster (Beta) in Global View > Settings > Cluster, supporting only the Hot-Standby Backup Mode currently. For configuration instructions, refer to the FAQ: How to Configure Hot-Standby Backup Mode on Omada Controller.- Added support for Google Authentication (Beta) in Site View > Settings > Portal > Authentication Type.
- *Added support for Disable NAT in Site View > Settings > Transmission > NAT.
- *Added support for LAN DNS in Site View > Settings > Wired & Wireless Network > LAN.
- *Added support for filtering with content in Site View > Settings > Network Security > URL Filtering. This feature can help network managers to achieve efficient, secure and convenient web access control by integrating a large number of categorized URL libraries.
- *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.
- *Added support for ARP Detection on Gateway. With this feature enabled, the dumb terminal can be detected, including POS, printer, etc.
- Added support for 'Remember Device' in Site View > Settings > Site Settings > General Configure. With this feature enabled, after device reset and power-on, the Controller will automatically adopt the device if the controller can find it.
- Added support for Role Super Administrator, which can manage all the other roles (except Owner, which used to be recognized as Main Administrator) and the privileges of most features.
4. Enhancements
- Optimized dependencies. Upgraded built-in JDK to version 21.
- Optimized WAN Mode. Added support for automatic updates to the Gateway Model when a new model is released.
- Optimized Portal Logout Page. Added support to show used and remaining data on the Logout page of Voucher/Local User Portal.
- Optimized MAC Filtering. When adopting devices with MAC filtering enabled, the MAC address of devices will be added into Allow List automatically.
- *Optimized Gateway ACL. Added support for choice as "! -> !". Customers can choose data resources and destinations that are not in certain marked range, which allows customers to configure more flexible profiles.
- *Optimized DHCP Reservation. Added support for DHCP option 60, 66 and 138.
- *Added support for DNS Override in DNS Proxy.
- *Optimized Attack Defense. Added support to customize the length of large PING.
- *Optimized Network Transmission. Added support for domain in settings of OpenVPN and Wireguard VPN.
- *Optimized LAN on the following features:
- Added support to configure DHCP NEXT SERVER.
- Added support to edit Default LAN port of gateway.
- *Added support to display the Device MAC in the WAN port of gateway's properties window.
- Added support for a maximum of 256 VLANs. *With gateway's firmware update, the maximum number can be 512.
- 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 Base Distinguished Name as 512.
- Added support for the maximum length of strings in Additional Filter as 512.
- Added support to show the PPSK profile of SSID used by a client in Client List.
- Optimized PoE Utilization chart. The Utilization will be calculated according to the power limit of each port.
- 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 can choose to turn off this function to avoid it being triggered incorrectly due to a complex wireless environment.
- Added support for 5000 entries in one Voucher Group.
- Added support to edit Profiles All and Default in Site View > Settings > LAN > Switch Profile.
- *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.
- *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
Fixed the bug that the picture with "." in the file name couldn’t be uploaded into Hot Map.- Reduced potential security risks by forcibly redirecting HTTP requests and responses to HTTPS ones.
Notes
- These feature with * sign require gateway's firmware to adapt to Controller v5.15.
- Omada SDN Controller can only manage certain devices running the supported firmware. Please confirm that your device is compatible with the SDN Controller.
- Since version 5.14.32, Omada Controller no longer supports upgrade from Controller v4.
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
OC200(UN)_V1_1.35.2_pre-release (Built-in Omada SDN Controller 5.15.20.26)
OC200(UN)_V2_2.20.2_pre-release (Built-in Omada SDN Controller 5.15.20.26)
OC300(UN)_V1_1.29.2_pre-release (Built-in Omada SDN Controller 5.15.20.26)
OC400(UN)_V1_1.7.2_pre-release (Built-in Omada SDN Controller 5.15.20.26)
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
Feb 18th, 2025:
Update the release note of incorrect information.
Feb 13th, 2025:
Provide the following controller firmware for early access.
-
OC200(UN)_V1_1.35.2_pre-release (Built-in Omada SDN Controller 5.15.20.26)
OC200(UN)_V2_2.20.2_pre-release (Built-in Omada SDN Controller 5.15.20.26)
OC300(UN)_V1_1.29.2_pre-release (Built-in Omada SDN Controller 5.15.20.26)
OC400(UN)_V1_1.7.2_pre-release (Built-in Omada SDN Controller 5.15.20.26)
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
Thank you so much for taking the time to post the issue on TP-Link community!
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 TKID250252600, please check your email box and ensure the support email is well received. Thanks!
- Copy Link
- Report Inappropriate Content
Hey @Vincent-TP, good day! I'd like to let you know of some bits from my experience with the latest firmware.
I'm using OC200(UN)_V1, and my experience has been almost synonymous with that of the others.
First test release of the revamped interface (back from Jan'25), though was lacking much refinement, ran much smoother - without any major issues.
But with the most recent release there have been too many troubling issues.
I had initially loaded the firmware release from Feb 13, which was very sluggish and pain to use. Though the version remained the same, i reloaded the file after 18th - noticing the date change, and i have seen only a slighter improvement thereafter.
My main concerns are with the big ugly background of Confidentiality stating it is a Test Build, Home Assistant integration and mainly what looks like the controller re-configuring the connections every now and then. It feels like you have put out a DEV build with all flags still in place for feature testing / telemetry / verbose logging and released it under the Pre-release tag.
I receive regular notification for WAN Down/Up states via Home Assistant Omada integration (meaning the controller is flipping those states, which is read by the Home Assistant interface), even though the connections remain stable. This happens at irregular intervals, and may be more than a couple of times during the day.
Also, there are daily notifications (via Omada app) of AP / Switch reconnecting - similar to when the device gets reconfigured post system reboot, though there are no actual system reboots (I run monthly jobs for that). And all this started with the second release of the uplifted firmware.
I'd much appreciate if you could have all these issues addressed at a much faster pace. Let me know if you need any further information from my end, I'll gladly assist, thanks.
- Copy Link
- Report Inappropriate Content
Thank you so much for taking the time to post the issue on TP-Link community!
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 TKID250257369, please check your email box and ensure the support email is well received. Thanks!
NittyMDev wrote
Hey @Vincent-TP, good day! I'd like to let you know of some bits from my experience with the latest firmware.
I'm using OC200(UN)_V1, and my experience has been almost synonymous with that of the others.First test release of the revamped interface (back from Jan'25), though was lacking much refinement, ran much smoother - without any major issues.
But with the most recent release there have been too many troubling issues.
I had initially loaded the firmware release from Feb 13, which was very sluggish and pain to use. Though the version remained the same, i reloaded the file after 18th - noticing the date change, and i have seen only a slighter improvement thereafter.
My main concerns are with the big ugly background of Confidentiality stating it is a Test Build, Home Assistant integration and mainly what looks like the controller re-configuring the connections every now and then. It feels like you have put out a DEV build with all flags still in place for feature testing / telemetry / verbose logging and released it under the Pre-release tag.
I receive regular notification for WAN Down/Up states via Home Assistant Omada integration (meaning the controller is flipping those states, which is read by the Home Assistant interface), even though the connections remain stable. This happens at irregular intervals, and may be more than a couple of times during the day.
Also, there are daily notifications (via Omada app) of AP / Switch reconnecting - similar to when the device gets reconfigured post system reboot, though there are no actual system reboots (I run monthly jobs for that). And all this started with the second release of the uplifted firmware.
I'd much appreciate if you could have all these issues addressed at a much faster pace. Let me know if you need any further information from my end, I'll gladly assist, thanks.
- Copy Link
- Report Inappropriate Content
Unable to Find Client's Identified Traffic Option
In the previous version, I was able to see detailed data usage for each client, including which websites and applications were being accessed. However, in the current version, I can no longer find this option.
Has this feature been removed, or is there a setting I need to configure to enable it? I have checked my Omada Software Controller, and it includes this option, but the Omada Hardware Controller does not.
I would appreciate your guidance on this matter.
In this red place, I previously saw an option like 'Client's Identical Traffic Option'.
In this red place, I previously saw an option like 'Users'.
Like this
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
@Babun-Sikder yes i cant check detail statistic too this annoying since 15.5.8 please fix @dev
- Copy Link
- Report Inappropriate Content
Your right I already enabled the DPI option but user's tab not showing also identified traffic option not showing
Kindly check with developer team for the same
- Copy Link
- Report Inappropriate Content
For hardware controllers, there is no User tab.
And for the Client's Identical Traffic Option'. missing issue, this is mostly related to the gateway.
What's the model number of your gateway? What;s the firmware version?
Is it still connecting to the controller?
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 3291
Replies: 42
Voters 0
No one has voted for it yet.