Early Access Omada Software Controller_v5.2.4 For Trial (Beta Edition) - Closed on 7 May 2022
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
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
@Fae Thank you for the updates. Are there any updates on when 5.1 will be available on the OC 200/300?
- Copy Link
- Report Inappropriate Content
EDIT
- Copy Link
- Report Inappropriate Content
Dear @NicholasA,
NicholasA wrote
Thank you for the updates. Are there any updates on when 5.1 will be available on the OC 200/300?
OC200 v5.1.7 has been released last Friday, you may check this post for an update.
OC300 v5.1 was found to have some issues before release, so it's delayed and will be released once the issues are resolved.
- Copy Link
- Report Inappropriate Content
Dear @MatthiasLoi,
MatthiasLoi wrote
@Fae I would be happy if the possibility to connect to OpenVPN with username and password authentification could be implemented until release.
It was announced to be available in 5.2. version by TP-Link Suppport.
Nevertheless - so far the BETA is working for me.
Thank you for your valued feedback!
I'm also waiting to see the implement of OpenVPN with username and password on controller v5.2.
However, I didn't see this added in the release note of controller v5.2 yet. So we may need to wait for the next version.
- Copy Link
- Report Inappropriate Content
Dear @btx,
btx wrote
I've experienced strange issue, telling me that log space is full, therefore it raises a question: What is the max size of logs for omada controller? Where can I check what "full" means? Controller has more than enough space for quite some time, meaning that device is not out of space, here is root info:
Another question of full log would be, what happens when the log is full, no further entries are created?
I am also aware that one can set notifications and if it is too much for one, some can be disabled (like DFS changing channels, I had hunderds of errors before disabling). If one can enable/disable notifications and there is enough free space on omada controllers running on pc's, could you please add a field where one sets custom max. size of logs like in MB/GB?
Thank you for taking the time to post your feedback.
The FAQ below explains why you get the alert and how to handle it.
What to do if you get an alert of “The number of logs is up to the limit”
About the kernel, do you find any security issues with any omada devices, or what's your main concern?
To submit a security-related inquiry regarding TP-Link products, welcome to Contact TP-Link Technical Support.
BTW, this thread is mainly to collect feedback on the Controller v5.2.4 Beta. For other off-topic issues, it's highly recommended to Start a New Thread with more detailed information, so we can discuss further and try to help.
- Copy Link
- Report Inappropriate Content
EDIT
- Copy Link
- Report Inappropriate Content
@Fae How can i be included in the BETA testing?
- Copy Link
- Report Inappropriate Content
thanks for the beta-version. I just installed it to test the features of the hotspot voucher portal:
Coming from 3.x going trough v4.2.11 I migrated to 5.2.4 (beta). Seems to work this way but all the already created vouchers get "Client Duration" as default value. But for us it should be "Voucher Duration" - any ideas how to change that?
- Copy Link
- Report Inappropriate Content
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
- Copy Link
- Report Inappropriate Content
Dear @indigo,
indigo wrote
thanks for the beta-version. I just installed it to test the features of the hotspot voucher portal:
Coming from 3.x going trough v4.2.11 I migrated to 5.2.4 (beta). Seems to work this way but all the already created vouchers get "Client Duration" as default value. But for us it should be "Voucher Duration" - any ideas how to change that?
Thank you for your valuable feedback. For "Client Duration", each new connected client using the same voucher code to get authenticated can have Internet access for a same duration time. While for "Voucher Duration", once the first client has used the voucher code to get authenticated, the duration countdown begins and the voucher code will be expired after the duration time is up no mater how late other clients get authenticated.
The previous controller version seems to adopt the "Client Duration" mechanism, so all your previously created vouchers get "Client Duration" as default value. Sorry that I don't find the option to change them to "Voucher Duration" either.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 6
Views: 8490
Replies: 31
Voters 4
