Beta Software Omada Software Controller_v5.2.4 For Trial (Beta Edition) - Closed on 7 May 2022
Updated on 7 May 2022:
Thank you all for your valuable feedback on the Controller v5.2.4 beta.
Official release for Omada Software Controller v5.3.1 is now available.
For more details, please refer to this post.
Thank you for your attention!
------------------------------------------------------------------------
Hello Everyone,
Now we have the Beta firmware of Omada Software Controller v5.2.4 (Windows & Linux OS) for trial!
The Purpose Of The Beta Firmware
We hope to offer you with a chance to experience the new features added in the Controller v5.2 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.
Release Notes:
- New Features & Enhancements
-
Added button to disable cloud-connection behavior of Omada Devices. It requires upgrading the Omada devices to the adapted firmware.
-
Upgraded spring-boot version to 2.6.6 and spring-framework version to 5.3.18 to avoid the potential Spring vulnerability (CVE-2022-22965). Mentioned Here.
-
Omada Controller won't delete the device's private configuration when the device is in the "Managed by Others" status.
-
Added "Duration Type" options for vouchers, with "Voucher Duration" and "Client Duration" optional.
-
Optimized the upgrading orders for Upgrade Schedule and Rolling Upgrade.
-
Adapted new features of Omada APP 4.2:
- SSID Override
- DHCP Reservation
- WiFi Control
- TP-Link Email service for Invitation and Password Reset
- Configure Device Account when creating a new site
- Display SN codes of devices managed by Omada Cloud-Based Controller
-
Updated the database encryption to enhance security.
-
Added support for Facebook Wi-Fi 2.0 for wired networks, which requires upgrading the Omada Gateway to the adapted firmware.
-
Updated some help information.
-
Optimized FTP configuration saving process.
-
Network Report performance optimization in large network scale.
-
Support to detect software updates at customized schedule time.
- Bug Fixed
-
Fixed the bug that clients connected to non-EAP wireless networks were not listed.
-
Fixed the bug that the controller cannot be accessed via HTTPS using Chrome on MAC.
-
Fixed the bug that Insight -> Past Connections does not show association failure records.
-
Fixed the bug that the Controller may execute the deleted reboot schedule in certain cases.
-
Fixed the bug that the Omada Router may be disconnected after upgrading the Controller version to 5.0.30.
-
Fixed the bug that the portal customized page may be lost after upgrading Controller version from v4 to v5.
-
Fixed the bug that fail to install the Controller 5.1.7 deb with the error of “needs MongoDB version dependency <=v4”. Mentioned Here and Here.
- Notes
1) Omada SDN Controller can only manage certain devices running the supported firmware. Please confirm that your device is compatible with the SDN Controller.
2) If you are planning to upgrade to this version from an old Controller (V3.2.14 or below), please read the Omada Controller Upgrade Guide before upgrading.
3) Once upgraded to this version of Omada Controller, you will be unable to downgrade to version 3.2.14 or below.
4) This version of the controller is fully applied to the Omada APP of version 4.2.X or above.
Download Link:
Please be sure you have read the Beta Test Agreement before upgrading the Beta firmware below!
Omada_SDN_Controller_v5.2.4_Windows (Beta)
Omada_SDN_Controller_v5.2.4_Linux_x64.deb (Beta)
Omada_SDN_Controller_v5.2.4_Linux_x64.tar.gz (Beta)
Attention:
1. Cloud Access is unavailable for the Beta Controller.
2. We strongly suggest you save the backup file before upgrading.
3. To revert to the previous Controller version from this Beta firmware, you must completely uninstall it.
Updated on 7 May 2022:
Official release for Omada Software Controller v5.3.1 is now available.
For more details, please refer to this post.
Feedback:
Any further feedback on the new firmware, please feel free to comment below.
When reporting an issue, especially it's about firmware upgrade, it's suggested to include the following info:
-- Omada Controller version (previous and current)
-- Device Model(s) and Hardware
-- Device Firmware (previous and current)
Note: if you decide to downgrade the firmware before sending feedback to us, we recommend you save a copy of the current Log file* and Backup Config file** before you do that, which might be helpful to address the issue you suffered from the new firmware.
* The Log file of Controller can be exported under Settings -> Services -> Export Data -> Running Log.
** The Backup Config file of Controller can be exported under Settings -> Maintenance via local access.
Thank you in advance for your great cooperation and support!
We look forward to hearing from your real and valued feedback here!
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Dear @abhi182,
abhi182 wrote
Has the WAN fail over issue been sorted out?
To elaborate, er605 in standalone mode supports custom pings to detect WAN status. This works for failover if primary wan goes down.
In omada managed mode, this option is not available and the default online detection fails to detect WAN outage on the primary for static IP wan setups
Sorry for any trouble caused. I'm afraid that the Manual option for Online Detection hasn't been added on Controller v5.2 yet.
I've recorded this to the developer team for further confirmation.
- Copy Link
- Report Inappropriate Content
Dear @RO2,
RO2 wrote
@Fae How can i be included in the BETA testing?
Thank you for your support. At present, all of our community users have the access to the Beta testing.
I'll actively update this post once there is a new controller version available, including the Beta edition, welcome to subscribe!
- Copy Link
- Report Inappropriate Content
@Fae Thanks for your reply.
As I already described in my thread https://community.tp-link.com/en/business/forum/topic/533962?replyId=1065068 the behaviour of the previous versions is strange and for a reasonable usage of the voucher function "Voucher Duration" should be the default state. I cannot imagine a usagecase for "Client Duration", especially when switching MAC-adresses of the device.
- Copy Link
- Report Inappropriate Content
is there any option to prioritize whatsapp and imo calls on omda controller & ER7206 vpn router???
can anyone pls help me if so.
thanks
- Copy Link
- Report Inappropriate Content
EDIT
- Copy Link
- Report Inappropriate Content
What channel do you use on root EAP? when enable channel limit is ch100 the lowest on outdoor EAP, if you have root ap on ch36 they newer could speak to each other.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
EDIT
- Copy Link
- Report Inappropriate Content
Information
Helpful: 6
Views: 9729
Replies: 31