Early Access Omada SDN Controller_V5.15.20 Pre-Release Firmware (Update on 26th Feb, 2025)
This Article Applies to
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
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.
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.
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.
4) For Linux: 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.
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.
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
1) Fixed the bug that the picture with "." in the file name can't be uploaded into Hot Map.
2) 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.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
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
@kogan I have been noticing significantly greater memory usage under linux as well. I had increased from 2Gig to 3Gig ram allocation for docker, but likely need to now increase to 4Gig as the java process is starting to swap a lot more as it uses 2.7+/3Gig allocated.
The java process itself is what seems to be using all the memory:
# smem -s swap -ktr
PID User Command Swap USS PSS RSS
1354930 508 java -server -Xms128m -Xmx1 563.7M 2.5G 2.5G 2.5G
1355231 508 /opt/tplink/EAPController/b 39.4M 281.6M 282.2M 283.5M
15563 root /usr/bin/dockerd -H fd:// - 4.7M 58.6M 58.8M 60.6M
14443 root /usr/bin/containerd 4.5M 21.2M 21.2M 22.5M
1 root /lib/systemd/systemd --syst 1.9M 1.1M 2.9M 7.5M
# top -p 1354930
%Cpu(s): 25.0 us, 0.0 sy, 0.0 ni, 50.0 id, 0.0 wa, 0.0 hi, 25.0 si, 0.0 st
MiB Mem : 8192.0 total, 118.3 free, 6303.3 used, 2701.2 buff/cache
MiB Swap: 1024.0 total, 145.1 free, 878.9 used. 1888.7 avail Mem
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
1354930 508 20 0 10.4g 2.5g 25380 S 0.0 31.1 138:14.55 java
- Copy Link
- Report Inappropriate Content
Hi @daubstep
Thanks for your feedback.
Will the following issue happen on your installation? Or just increasing memory, no other issues?
since Upgrade to 5.15.20.x most linux omada controllers getting killed from OOM , after reboot everything works fine, til the controller is killed again.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
@Vincent-TP
Er706 with fw 1.04 gets shown in global view as stable 1.13 firmware available
in site view it shows 1.12 available..shouldnt it be both 1.13?
btw tested 1.13 stable and its still the same issue like with 1.12
https://community.tp-link.com/en/business/forum/topic/710656
- Copy Link
- Report Inappropriate Content
Hi @kogan
We have sent a support ticket to your email, could you please have a check and try to search the case ID TKID250237912 ?
We appreciate for your cooperation to locate the issue.
- Copy Link
- Report Inappropriate Content
Chaotix wrote
@Vincent-TP
Er706 with fw 1.04 gets shown in global view as stable 1.13 firmware available
in site view it shows 1.12 available..shouldnt it be both 1.13?
btw tested 1.13 stable and its still the same issue like with 1.12
https://community.tp-link.com/en/business/forum/topic/710656
Hi @Chaotix
For the gateway issues, please continue the troubleshooting with @Clive_A.
- Copy Link
- Report Inappropriate Content
Sorry, had a lot of work - sent it 2 days ago already, waiting for some conclusion or solution :-) thanks!
- Copy Link
- Report Inappropriate Content
I've had the controller software installed from 2/2.
Today clients on the wired lan suddenly were unable to get to the internet. Wireless clients continued to work without issue.
I had no errors in my audit log and nothing seemed out of the ordinary. Rebooting my router seemed to resolve the issue. Looking at my server logs however I did see several entries like this
| 2025/02/27 20:47:40 |
stdout | at [Source: REDACTED (`StreamReadFeature.INCLUDE_SOURCE_IN_LOCATION` disabled); line: 1, column: 47] (through reference chain: com.tplink.smb.omada.device.manage.message.body.osg.OsgGetRespBody["urlFiltering"]) |
| 2025/02/27 20:47:40 |
stdout | Caused by: com.fasterxml.jackson.databind.exc.MismatchedInputException: Cannot deserialize value of type `com.tplink.smb.omada.device.manage.message.get.osg.ContentFilterResp` from Array value (token `JsonToken.START_ARRAY`) |
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Information
Helpful: 6
Views: 11549
Replies: 85
Voters 3
