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
All of them, sir. Client connections are reliable, except for the Omada APP, which is still buggy or more like not compatible to V5.15
- Copy Link
- Report Inappropriate Content
Thank you so much for your feedback.
We have fixed the issue in the next version.
- Copy Link
- Report Inappropriate Content
ok I'm going to join this gravy train. btw @Vincent-TP
i see what you mean now about the different version numbers this is my first time coming here on my phone.
Anyway. I'm running Debian latest stable. and i will upgrade to the latest beta.
modem <---> js l2 managed switch <----> proxmox ve latest non enterprise repo <---->
[virtual network stack]
vswitch bridge port1 (slaved physical card1 port) <-> pfsense vm pulls isp dhcp off the modem .
vswitch bridge port 2 (slaved physical card2 port) <-> pfsense lan with more vms and configured vlans to seperate my wifi traffic from my wired traffic and .more.
so far it works fine but i will upgrade and see how it goes.
let me know if there is anything extra i can contribute
- Copy Link
- Report Inappropriate Content
Hi @n0izee
Welcome to the Omada world.
If you encounter any interesting issues during the upgrade or while using the beta version, documenting them in detail and sharing your experiences on relevant forums or communities would be very helpful. This could assist other users who might be considering a similar upgrade and also provide valuable feedback to the Debian developers.
- Copy Link
- Report Inappropriate Content
Feature Request: Client Latency Test Option
Hello TP-Link Team,
I’d like to propose a new feature that could greatly improve the user experience: adding an Online Client Latency Test option.
I know there is already a similar feature available through Network Tools where we can manually select the gateway, switch, or EAP and type in the IP/domain to perform a ping test. However, having a dedicated, streamlined option to directly test client latency would save time and make it far more user-friendly.
Benefits of This Feature:
1. Improved User Experience - Users could directly see client latency without navigating to separate tools.
2. Real-time Monitoring - Instantly view current latency data between the client and network.
Integrating this feature into the main interface would make network management smoother and enhance the overall user experience. Thank you for considering this improvement—it would be a fantastic addition!
https://community.tp-link.com/en/business/forum/topic/716018
LIKE THIS
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Hello, I have the same issue with "Omada App and Client does not exists". Any temporary fix until new version will be released?
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
@Vincent-TP Given the many issues discovered in the v5.15.6.4 pre-release, is there any ETA on the next (pre-) release with fixes given it's been over a month so far?
- Copy Link
- Report Inappropriate Content
Vincent-TP wrote
@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.
cannot make any settings on the WAN interface from the web management console, changes can be made from the mobile app without problems.
Do you know when there will be an updated prerelease with all the bug fixes?
- Copy Link
- Report Inappropriate Content
Information
Helpful: 1
Views: 14121
Replies: 92