Early Access Hardware Controller (Built-in Omada SDN Controller V5.15.20.31) Pre-release Update on 10th Mar 2025
This Article Applies to
OC200(UN)_V1_1.35.3_pre-release (Built-in Omada SDN Controller 5.15.20.31)
OC200(UN)_V2_2.20.3_pre-release (Built-in Omada SDN Controller 5.15.20.31)
OC300(UN)_V1_1.29.3_pre-release (Built-in Omada SDN Controller 5.15.20.31)
OC400(UN)_V1_1.7.3_pre-release (Built-in Omada SDN Controller 5.15.20.31)
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.
- Added support to edit Profiles All and Default in Site View > Settings > LAN > Switch Profile.
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.3_pre-release (Built-in Omada SDN Controller 5.15.20.31)
OC200(UN)_V2_2.20.3_pre-release (Built-in Omada SDN Controller 5.15.20.31)
OC300(UN)_V1_1.29.3_pre-release (Built-in Omada SDN Controller 5.15.20.31)
OC400(UN)_V1_1.7.3_pre-release (Built-in Omada SDN Controller 5.15.20.31)
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
Mar 10th, 2025:
1. Update the release note;
2. Update the following download link:
OC200(UN)_V1_1.35.3_pre-release (Built-in Omada SDN Controller 5.15.20.31)
OC200(UN)_V2_2.20.3_pre-release (Built-in Omada SDN Controller 5.15.20.31)
OC300(UN)_V1_1.29.3_pre-release (Built-in Omada SDN Controller 5.15.20.31)
OC400(UN)_V1_1.7.3_pre-release (Built-in Omada SDN Controller 5.15.20.31)
3. Removed the watermark.
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
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 TKID250309009, please check your email box and ensure the support email is well received. Thanks!
Wienumgebung wrote
@Vincent-TP; @Clive_A I really can't tell if it is an issue with the OC200 Controller or the ER8411, but it seems to be a bunch of issues: 1.) NAT gets lost on at least one gateway (ER8411) Other Sites canno longer Connect after a certain time 2.) VPN stops working or even is removed from the configuration... 3.) Some configs seem to be possible, but don't work... Sometimes it looks like the controllers settings are not commited to the router... My "core" network has three sites, two with 8411, one with a 7206. Each site has 3-6 vlans, tunneled as needed, the two sites with the 8411 have 2-3 WANs. All I want is a stable connection between the sites... On Main Site (where the oc200 is), the NAT Rules allow all Sites to access the controller, but they can't reach it. What goes wrong here?
- Copy Link
- Report Inappropriate Content
@GRL I have the same problem with IPsec site-to-site vpn profile
- Copy Link
- Report Inappropriate Content
@Vincent-TP I've been testing this beta on my OC200 v2 since it came out and have been experiencing some issues:
1) Very slow GUI - others have reported this
2) Random messages that the controller has gone offline - NO log entries that say anything about the controller
3) Random disconnection and re-connection of AP's - Log Entries: "Device Disconnected" and "EAP Isolated" - This is happening with both wired and mesh connected EAP's
4) Random adoption issues - "The configurations of device EAP610 are different from the configurations from the controller" - only on EAP 610's after they get disconnected/isolated
- Copy Link
- Report Inappropriate Content
Did you enable auto backup for the controller?
If yes, please disable it, or set the schedule longer, such as backup once a year.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
I am pleased to report some feedback on the 10th March release on my OC200 v1
- Much, MUCH better performance compared to the february beta - seems to perform just as well as the last official version form January👍
- No VPN configs lost on either main or remote sites👍
- Thank god the watermark is gone 👍
- All devices adopted, provisioned and configured correctly👍
- None of my switch SVIs or Static routes were wiped this time👍
- Local and Cloud access both working fine👍
- Remote sites, which are adopted via the vpn internally rather than port forward on main site WAN method, all adopted correctly👍
Further explorations-
- No issues with configs on my EAP650s, and all switches on local and remote sites are all ok
- Everything came back up perfectly after a full reboot of all hardware on main and remote sites
- Still no TP-Link dynamic DNS listed, even on a remote site that has a fully adapted gateway firmware (ER7206 v2 with the latest feb 28th beta)
Some issues i have noticed
- There is still a small amount of lag when switching between tabs on a single page (eg, gateway, switch and eap ACL rules) with a bit of spinny loading, but its nowhere near as bad as the last beta, just a couple seconds delay
- The firmware listing page (global > firmware) took about a minute to load the list applicable to my hardware, but after that initial load was fast again. Again, just a spinny loading animation rather than a full page time-out
- Clicking on a device to load its properties pages has a tiny amount of lag, but again, not much of an issue and still much better than last version. Once loaded, switching between the tabs is just as fast as last stable version
- Switching between sites takes a few seconds longer than previous stable, but not much of an issue, again, just spinny loading rather than page timeouts or controller crashes
I will test further today and let you know if i find anything else
- Copy Link
- Report Inappropriate Content
The new 25/03/10 update is a relief!
it is much more responsive on OC200v1 (devices still take long to get up without a notice that admins click is being reacted to) and seems to have addressed the NAT and VPN "memory" issues. Thank you very much!
I want you @tplink to know that your work is very much appreciated!
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Thank you so much for your positive feedback and for taking the time to share your experience with the latest 25/03/10 update for the controller. We’re thrilled to hear that the update has brought improvements.
We understand how important it is for the system to be efficient and reliable, and we’re glad to hear that the update has made a noticeable difference.
This is closely related to your positive feedback, your kind words mean a lot to us, and we’re grateful for your support and appreciation. At TP-Link, we’re committed to delivering the best possible solutions for our users, and your satisfaction is our ultimate goal.
If you have any further feedback or encounter any issues, please don’t hesitate to reach out. We’re here to help!
- Copy Link
- Report Inappropriate Content
According to the release note, unfortunately, we don't have new feature related to this.
NovaSistemas wrote
With this firmware, can you create NAT rules using the same port for different WAN Aliases using the same wan interface? For example, NAT port 443, on two public wan port IPs, directed to two different local IPs, using the same physical interface wan/lan4 for example.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 5749
Replies: 65
Voters 0
No one has voted for it yet.