Omada Hardware Controller_V5.14 Pre-release (Released on Apr 16th, 2024)
Omada Hardware Controller_V5.14 Pre-release (Released on Apr 16th, 2024)
Thank you all for your valuable feedback on the pre-release firmware!
The early access controller version 5.14.20 has been released, check the following link for details.
Omada SDN Controller_V5.14.20 Pre-release
This Article Applies to
OC200(UN)_V1_1.30.2_Build20240410 (Built-in Omada SDN Controller 5.14.0.21)
OC200(UN)_V2_2.15.2_Build20240410 (Built-in Omada SDN Controller 5.14.0.21)
OC300(UN)_V1_1.23.2_Build20240410 (Built-in Omada SDN Controller 5.14.0.21)
OC400(UN)_V1_1.2.1_Build20240409 (Built-in Omada SDN Controller 5.14.0.21)
Overview
We hope to offer you with a chance to experience the new features added in the Controller v5.14 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 lettings us know about successful upgrades.
Release Notes
New Feature
1. Added support for EAP-OWE management frame encryption.
2. Added support for loopback detection on EAP-Wall series models.
3. Added support to modify Beacon Intervral to a larger range.
4. Added support to disable port and configure port VLAN for Multi-LAN port EAPs.
5. Added support to Logout when using Portal on EAPs.
6. Added support for multiple Radius servers when using MAB on EAPs.
7. Added support to custom channel set.
8. Added support to display the actual working channel width when set channel width to auto.
9. Added support to display the status information of the Multi-Lan port EAPs downstream port.
10. Added support to multicast/broadcast statistics about EAPs.
11. Added support for Terminal and Pack Capture when enable the Cloud Access on Controller.
12. Added support for Controller-configured device names to be delivered to devices (hostname, LLDP, and SNMP).
13. Added support to return error code prompt when configuring status synchronization.
14. Added support for centralized proxying of Radius.
15. Added support to display the Maximum Associated Clients range according to the model.
16. Added support to display information about downlinked Omada devices.
17. Added support for EAP-related DNS queries in Tools.
18. Added support for NAS ID configuration in SSID enterprise encryption, which can be configured as Device Name.
19. Added support that PPSK entries up to 1024.
20. Added support to ER7412-M2.
21. Added support to configure the wireless function of ER706W-4G.
Enhancement
1. Clients related optimization:
- EAP and Switch add the See All logo to jump to the Clients page.
- Add MAC address filtering search for connected clients.
- Add Signal to the EAP Client page.
2. Add support to search MAC Group.
3. AP VLAN related optimization:
- The default LAN name of Network is changed to Default and modification is not supported.
- Management VLAN and SSID VLAN no longer support configuring the same VLAN as the default LAN
- SSID VLAN supports selecting Network
4. Added support to report OFDMA default values, which may be different for different EAP models.
5. Optimize Client association log.
6. Optimize the mechanism of Portal’s Rate Limit function.
7. Reduced the startup time of the Omada Hardware Controller.
Note
1. The built-in Radius authentication server no longer supports the PPSK function, and the configured related SSID will be automatically deleted after the installation of the Controller.
Notes
1. This version of the Controller is fully applied to the Omada APP of version 4.14 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. If you are upgrading from controller v3.x, it's highly recommended to upgrade 3.x to v4.1.5 first, then v4.1.5 to the latest 5.x. Please follow the Omada Controller Upgrade Guide in the installation package before upgrading.
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 upgrade or downgrade.
(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
OC200(UN)_V1_1.30.2_Build20240410 (Pre-release version) > Built-in Omada SDN Controller 5.14.0.21
OC200(UN)_V2_2.15.2_Build20240410 (Pre-release version) > Built-in Omada SDN Controller 5.14.0.21
OC300(UN)_V1_1.23.2_Build20240410 (Pre-release version) > Built-in Omada SDN Controller 5.14.0.21
OC400(UN)_V1_1.2.1_Build20240409 (Pre-release version) > Built-in Omada SDN Controller 5.14.0.21
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 to 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.
-
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
- Copy Link
- Report Inappropriate Content
Would support. Function over start-up time. Thx!
- Copy Link
- Report Inappropriate Content
Hi @Totti_14, I again updated my OC200 v1.0 controller to beta firmware 1.30.2_20240410_rel31241. It indeed seems to work. Thanks for your suggestion!
What I don't understand is that even though after the update the correct VLAN was still selected per WLAN under 'Add VLAN -> By VLAN ID', the correct IP addresses were not assigned anymore. Only after changing to 'Add VLAN -> By Network', the correct IP addresses were again assigned.
Hopefully you can explain what the actual difference is between 'Add VLAN -> By VLAN ID' and 'Add VLAN -> By Network'? By the way, I assume that this is one of the changes as mention under Enhancement (SSID VLAN supports selecting Network).
@Hank21, I notice that the New Feauture 4 (Added support to disable port and configure port VLAN for Multi-LAN port EAPs), disable port does not seem to work on my three-port EAP615-Wall(EU) v1.0 access points. For all three ports, the option 'Status -> Enable' is checked and grayed out. So, I cannot change it if I would.
P.S. The same is the case for my one-port EAP230-Wall(EU) v1.0 access points.
- Copy Link
- Report Inappropriate Content
Hi @WM1,
I'm not a network specialist and I can't explain how VLan work.
I only know we use VLan to set different network's to control the access to the WAN and to different subnet's.
For example ADMIN-Network 192.168.1.XXX / IoT-Network 192.168.20.XXX / Office-Network 192.168.50.XXX / ...
But I know with VLan you can go down to the client NIC.
Ssome PC's you can set a VLan ID to to control the access.
Greetings Totti.
- Copy Link
- Report Inappropriate Content
Hi @WM1
you need to wait for the new firmware for EAP615-wall that will support the port disable function.
- Copy Link
- Report Inappropriate Content
Hi @Tamer_Morcos, thanks. Do you have any idea when the new firmwaer for EAP615-Wall will become available?
- Copy Link
- Report Inappropriate Content
@SirDigby I've created a feature request for this, if you like to you and everyone else here could give it an vote. https://community.tp-link.com/en/business/forum/topic/671250?page=1
- Copy Link
- Report Inappropriate Content
Why would you remove a feature without polling the community first? PPSK without RADIUS is a huge selling feature and capability of the Omada ecosystem. I will not be updating any of my Omada installs to newer controller software as this is a breaking change that will require significant work to remediate. I don't want multiple SSIDs to assign different vlans. Please do not remove the PPSK without RADIUS feature. Just let users disable RADIUS if they want faster boot times and don't use it.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
++1 for keeping OpenAPI and Built in Radius, leave it disabled by default to improve boot times for those that don't need it.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 3
Views: 6625
Replies: 20
Voters 1
