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.
-
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
OrangeStreet wrote
@MR.S This worked! Problem now is cloud access is broken.
Yes, there is something buggy there, try deactivating the cloud and activating it again
- Copy Link
- Report Inappropriate Content
@MR.S The slider to deactivate the cloud access is not available - It will not allow me to turn it off to try the workaround.
- Copy Link
- Report Inappropriate Content
try pressing it twice, i had the same problem, first press nothing happened second press disabled cloud.
- Copy Link
- Report Inappropriate Content
@MR.S That doesn't work for me - it is stuck in a disconnected state
- Copy Link
- Report Inappropriate Content
@Vincent-TP Cloud access is stuck on "disconnected" now and cannot be disabled/re-enabled - I get a red circle when I hover over the slider. I have rebooted and tried to click numerous times and nothing changes. Otherwise it seems to work fine.
- Copy Link
- Report Inappropriate Content
Hi, @daubstep
thank you so much for all these valued feedback. As for point 1, may we know your deb's version? And what's the firmware version of the software controller before this update? Does the wifi issue persist?
- Copy Link
- Report Inappropriate Content
@Babun-Sikder
Normally, The Internet vlanId is automatically assigned when the device is adopted.
If this is pre-config, you may input any value between 1-4086 as long as it doesn't duplicate with LAN, virtual wan, iptv custom configuration (if any) ID.
Note: The default LAN ID is 1.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
> As for point 1, may we know your deb's version? And what's the firmware version of the software controller before this update? Does the wifi issue persist?
This is the deb I installed for this update: Omada_SDN_Controller_v5.15.6.4_beta_linux_x64.deb Before this update I was running the latest previous update (from a few weeks prior): 5.14.32.2. Both were running on the same LXC running Debian 12 under Proxmox 6.8.12-1-pve.
Once I forced the devices with the initial issue to reconnect to wifi they worked. I've had one other issue with wifi devices not being connected that were always stable prior to the update, but I couldn't tell if I just didn't notice them at first and they were actually dropped during the update as well or if they were dropped later - after resetting these other devices they have reconnected and are working again as well, and I haven't noticed any other issues.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 1
Views: 10649
Replies: 81
Voters 1
