Omada Controller v5.5.6+rhel7

rhel to v5.5.6

Omada Controller Version 5.4.6

Tested on

• Debian 10, 11
• Ubuntu 18.04, 20.04
• RockyLinux 8, 8.4
• RHEL 8

Full Changelog: v5.3.1...v5.4.6

Release v5.3.1

check release notes https://static.tp-link.com/upload/software/2022/202205/20220507/Linux_Release_Note.pdf

Upgrade Guide https://blog.puvvadi.me/posts/upgrade-omada-controller/

Full Changelog: v5.1.7...v5.3.1

Version v5.1.7

Full Changelog: v5.0.30...v5.1.7

Version 5.0.30

Bug Fixes

• Fix the bug that AI Roaming function may cause an abnormal adopting behavior.
• Fix the bug that a disabled portal entry will cause the Controller fails to upgrade.
• Fix the bug that with static routing entries sometimes Controller will fail to adopt the gateway after updating from firmware version v4.
• Fix the bug that the gateway will drop out for a short time after modifying the client name.
• Fix the bug that the configuration can’t be saved if create Dynamic DNS/NO-IP DNS entries with the same Username.

What's Changed

• new version 5.0.30 by @kdpuvvadi in #5

Full Changelog: v5.0.29...v5.0.30

Omada V5.0.29

Changelog

• Add v5.0.29 124d1dd
• Add support for Centos 8 (Out of support anyway) 124d1dd
• Tp-Link again changed the tar directory structure. So, using strip components in the unzip module. 1be6bf3
• Mongodb support 124d1dd
• jsvc on centos(apache-commons-daemon-jsvc) a80f891

Full Changelog: v4.4.6...v5.0.29

Official Notes

New Feature/Enhancement

• 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).
• Added Two-Factor Authentication (2FA) feature for Cloud Access, Omada APP (4.0.X and above) and local web login with Cloud Users.
• Added support for OpenJDK-8 and above versions for the Linux platform.
• Added support for MongoDB v4 for the Linux platform.
• Added DHCP Reservation in Services, allowing pre-configuration and support for reserving IP addresses outside the DHCP Range.
• Removed the insecure WEP and WPA/TKIP algorithms from the wireless network. SSIDs encrypted with these algorithms will be removed after upgrading.
• Adjusted API for External Portal.
• Optimized the account structure and the privileges of accounts with different roles.
• Added support for Form Authentication type to the Hotspot Portal.
• Added support for Korean, Thai, and Vietnamese support to the Portal.
• Added support for multiple languages for names of Controllers, Devices, and Clients.
• Added pre-configuration for Internet during Quick Setup.
• Retain the advanced feature settings when removing or replacing the Omada Gateways, such as VPN, Port Forwarding, etc.
• Added support for saving the customized names for clients.
• Optimized the SSID Override feature and allow disabling SSID.
• Optimized the upgrading process for EAPs supporting PoE Out.
• Optimized the export file names for Backup and Export Data functions.
• Increased the number of “Limited IP Addresses” for Port Forwarding to a maximum of 24.

Bug Fixed

• Updated Log4j to 2.16 to fix the vulnerability CVE-2021-44228 and CVE-2021-44228.
• Fixed the bug that the VPN status was not updated in time.
• Fixed the bug that speed test statistics would be cleared when the Omada Gateway was disconnected from the controller.
• 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.
• Removed the limitation on the length of the Top-Level Domain Name.
• Fixed the bug that IP addresses cannot be entered using the French keyboard.
• Fixed the bug that the RADIUS server failed to properly limit the client bandwidth via WISPr-Bandwidth attributes.
• Fixed the bug that the blocked clients might still be listed as AUTHORIZED in the clients list.
• Fixed the bug that caused the “General Error” when disabling the rate limit profile for the first time.
• Fixed the bug that the Omada devices are frequently in Provision status in some cases.
• Fixed the bug that the background and logo pictures uploaded to Portal via cloud access are not displayed in the preview page.
• Fixed the bug that the Omada Gateway might be in Heartbeat Missed status in some cases.
• Fixed the error of “400 Bad Request” when accessing static resources if the custom page in zip format was imported.

v4.4.6 Log4j CVE-2021-45046 fix

Updated log4j to 2.16.0

Release v4.4.6-beta Build

Official Build 4.4.6 Beta with build 20211213180823

• Official Release here
• Download Build here
• To uninstall Omada Controller, run sudo bash /opt/tplink/EAPController/uninstall.sh
• Updated log4j binaries from 2.8.2 to 2.15.0. Following files have been changed
  • log4j-api-2.8.2.jar to log4j-api-2.15.0.jar
  • log4j-core-2.8.2.jar to log4j-core-2.8.2.jar
  • log4j-slf4j-impl-2.8.2.jar to log4j-slf4j-impl-2.15.0.jar

Full Changelog: v4.4.6...4.4.6-beta

v4.4.6 Log4j Fix

Temporary fix for Apace log4j exploit CVE-2021-44228.

What's Changed

• release link fix by @kdpuvvadi in #4

Full Changelog: v4.4.4...v4.4.6-log4j-fix

Version 4.4.6

Upgrade Omada Controller to V4.4.6

• Changelog: Here
• Directory Structure change in 4.4.6.
  • To address that removed --strip-components=1 from unarchive task on setup.yml

What's Changed

• release link fix by @kdpuvvadi in #4

Full Changelog: v4.4.4-23092021...v4.4.6