Omada Software Controller_v5.0.29_Linux has been released on January 7, 2022

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Omada Software Controller_v5.0.29_Linux has been released on January 7, 2022
Omada Software Controller_v5.0.29_Linux has been released on January 7, 2022
2022-01-09 06:04:36 - last edited 2022-01-09 06:18:18

This Article Applies to:

 

Omada_Software Controller_v5.0.29_Linux

 

Release Notes:

 

  • New Feature/Enhancement

 

1) Default port for device adoption and management has been changed to TCP port 29814, please refer to FAQ 3265 for more details. You can change the default ports (29810-29814) by editing the “omada.properties” file (default path: /opt/tplink/EAPController/properties) so that you can deploy multiple Controllers on the same PC or behind the same NAT router.
2) Added Two-Factor Authentication (2FA) feature for Cloud Access, Omada APP (4.0.X and above) and local web login with Cloud Users.
3) Added support for OpenJDK-8 and above versions for the Linux platform.
4) Added support for MongoDB v4 for the Linux platform.
5) Added DHCP Reservation in Services, allowing pre-configuration and support for reserving IP addresses outside the DHCP Range.
6) Removed the insecure WEP and WPA/TKIP algorithms from the wireless network. SSIDs encrypted with these algorithms will be removed after upgrading.
7) Adjusted API for External Portal, please refer to FAQ3231.
8) Optimized the account structure and the privileges of accounts with different roles.
9) Added support for Form Authentication type to the Hotspot Portal.
10) Added support for Korean, Thai, and Vietnamese support to the Portal.

11) Added support for multiple languages for names of Controllers, Devices, and Clients.
12) Added pre-configuration for Internet during Quick Setup.
13) Retain the advanced feature settings when removing or replacing the Omada Gateways, such as VPN, Port Forwarding, etc.
14) Added support for saving the customized names for clients.

-> this can fix the alias missing issue. Related posts can be found Here and Here.
15) Optimized the SSID Override feature and allow disabling SSID.

-> this can meet the requirement for customizing SSID for specific APs without creating a new WLAN Group. Related posts can be found Here and Here​​​​​​.
16) Optimized the upgrading process for EAPs supporting PoE Out.
17) Optimized the export file names for Backup and Export Data functions.
18) Increased the number of “Limited IP Addresses” for Port Forwarding to a maximum of 24.

 

  • Bug Fixed

 

1) Updated Log4j to 2.16 to fix the vulnerability CVE-2021-44228 and CVE-2021-45046. Please refer to FAQ 3255 for more details.
2) Fixed the bug that the VPN status was not updated in time.
3) Fixed the bug that speed test statistics would be cleared when the Omada Gateway was disconnected from the controller.
4) Fixed the bug that the push notification of Omada APP on the iOS platform displayed the MAC addresses of the devices instead of their names. Mentioned Here.
5) Removed the limitation on the length of the Top-Level Domain Name.
6) Fixed the bug that IP addresses cannot be entered using the French keyboard.
7) Fixed the bug that the RADIUS server failed to properly limit the client bandwidth via WISPr-Bandwidth attributes.
8) Fixed the bug that the blocked clients might still be listed as AUTHORIZED in the clients list.
9) Fixed the bug that caused the “General Error” when disabling the rate limit profile for the first time.
10) Fixed the bug that the Omada devices are frequently in Provision status in some cases.
11) Fixed the bug that the background and logo pictures uploaded to Portal via cloud access are not displayed in the preview page.
12) Fixed the bug that the Omada Gateway might be in Heartbeat Missed status in some cases.
13) Fixed the error of “400 Bad Request” when accessing static resources if the custom page in zip format was imported.

 

  • 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 using an old Controller and plan to upgrade to this version, please follow the Omada Controller Upgrade Guide.

3) Once upgraded to this version of Omada Controller, you will be NOT able to downgrade to version 3.2.14 or below.

4) This version of the controller is applied to the Omada APP of version 4.0.X or above.

5) Java 8 (or OpenJDK-8) and above, MongoDB v3 and v4 are necessary for Controller.
6) 64-bit Linux Operating System is supported.
7) Please save the backup file, then uninstall the old version before upgrading.

 

Download Link:

 

Omada_Controller_V5.0.29_Linux_x64.deb Full Release Note >

Omada_Controller_V5.0.29_Linux_x64.tar Full Release Note >

 

To get the latest firmware release for Omada Controller, welcome to subscribe to topic below.

https://community.tp-link.com/en/business/forum/topic/245226

 

Feedback:

 

If you have any further feedback on the new firmware, please feel free to start a new thread from HERE.

 

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)

 

Thank you in advance for your great cooperation and support!

Best Regards!
2
2
#1
Options