Early Access Omada SDN Controller_V5.15.6.4 Pre-Release Firmware(Released on Oct 18th, 2024)
This Article Applies to
Omada_SDN_Controller_v5.15.6.4 Windows (Windows 7/8/10/11/Server, 64bit Recommended)
Omada_SDN_Controller_v5.15.6.4_linux_x64.tar
Omada_SDN_Controller_v5.15.6.4_linux_x64.deb
Overview
We hope to offer you a chance to experience the new features added in the Controller v5.15.6.4 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: DR3650v, ER703WP-4G-Outdoor.
2. Added support for APs: EAP775-Wall, EAP625GP-Wall, EAP115-Bridge v2.0, EAP211-Bridge v2.0, EAP215-Bridge v2.0.
3. Added support to disable ports in the properties window of device.
4. Added support for batch import and export of Radius users in Site View > Settings > Network > Profile > RADIUS Profile > RADIUS Users.
5. Added support to configure DSL Gateway features in Site View > Settings > Wired&Wireless Networks > WAN Mode:
- Virtual WAN
- VoIP
- DSL Dialing
- TP-link DDNS
Enhancements
1. Optimized NAT Configuration, limit the entries of NAT according to Alias IP.
2. Optimized WLAN Optimization, added support to deploy Channel Width and Channel.
3. Optimized properties window, added support for Loopback Detection in Device > Properties window > Config > Services > Loopback Control.
4. Optimized the following features in Omada App:
- Added support for NTP configuration.
- Added support for Static Routing.
- Optimized properties window of the device
Notes
1. This version of the Controller is fully applied to the Omada APP of version 4.20 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_SDN_Controller_v5.15.6.4_pre-release_windows
Omada_SDN_Controller_v5.15.6.4_pre-release_linux_x64_deb
Omada_SDN_Controller_v5.15.6.4_pre-release_x64_tar.gz
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 27th, 2024:
Remove download links for all the controllers v5.15.6.4.
Oct 18th, 2024:
Provide the following controller firmware for early access.
Omada_SDN_Controller_v5.15.6.4_pre-release_windows
Omada_SDN_Controller_v5.15.6.4_pre-release_linux_x64_deb
Omada_SDN_Controller_v5.15.6.4_pre-release_x64_tar.gz
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
@MR.S facing same issue
- Copy Link
- Report Inappropriate Content
@Vincent-TP This release has killed my mongodb on my windows server installation - it errors out that it can't start mongodb - currently dead in the water. I did an upgrade to the latest stable version first, then to the beta. I also noticed that my java needed to be upgraded/patched so I ran that as well... not sure if that would be related for any reason
- Copy Link
- Report Inappropriate Content
Seems like on Ubuntu 22.04 it requires an older version of MongoDB:
omadac : Depends: mongodb-server (< 7.1.0) but 1:3.6.9+really3.6.8+90~g8e540c0b6d-0ubuntu5.3 is installed or
mongodb-10gen (< 7.1.0) but it is not installable or
mongodb-org-server (< 7.1.0) but it is not installable
- Copy Link
- Report Inappropriate Content
Upgrade successful but failed to login with the original password before upgrade. Also disconnected from cloud link
Original software version: v5.14.32.2
Beta software version: v5.15.6.4_beta
MSP mode: Enable
- Copy Link
- Report Inappropriate Content
OrangeStreet wrote
@Vincent-TP This release has killed my mongodb on my windows server installation - it errors out that it can't start mongodb - currently dead in the water. I did an upgrade to the latest stable version first, then to the beta. I also noticed that my java needed to be upgraded/patched so I ran that as well... not sure if that would be related for any reason
I had the same problem when I upgraded the controller for one of the kids, it turned out to be a java problem. installed new java from Adoptium and the problem was solved.
- Copy Link
- Report Inappropriate Content
Is adoptium the version bundles with the controller? Did you uninstall Java and install the adoptium version? Was it the JRE LTS 21?
- Copy Link
- Report Inappropriate Content
I stopped the omada controller and uninstalled the old java version, installed the new one and started the controller again,
More informarion in this link.
https://www.tp-link.com/en/support/faq/3086/
- Copy Link
- Report Inappropriate Content
@Vincent-TP This is working in my Proxmox LXC, three four five things so far (in addition to cloud access being broken like everyone else mentioned):
- Even though the deb installation stops and starts the service I had to stop/start the tpeap service again after the update before I could access the web ui
- This controller update caused an unexpected WiFi disruption, dropping wireless hosts from the network, and some did not re-connect after (have to go debug that now)
- The top-left id="fix-menu-btn" button causes this error when clicked (I assumed it would hide/collapse the left menu, but it does nothing but pop up this error message: "Something went wrong. Please try again later or contact our technical support."
- The results of WLAN Optimization are not readable in Dark mode:
- The color of the CPU and Memory are swapped in the top legend of the Usage (%) Graph under Statistics (orage is CPU in reality)
Edit Updates:
- Added #4
- Added #5
- Copy Link
- Report Inappropriate Content
@Babun-Sikder I have the same issue after fixing Java that was breaking mongodb, the cloud management is stuck offline
- Copy Link
- Report Inappropriate Content
@MR.S This worked! Problem now is cloud access is broken.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 1
Views: 11610
Replies: 86
Voters 1
