Business Community > All Threads > Omada Hardware Controller_V5.14 Pre-release (Released on Apr 16th, 2024)
< All Threads

Omada Hardware Controller_V5.14 Pre-release (Released on Apr 16th, 2024)

12

Omada Hardware Controller_V5.14 Pre-release (Released on Apr 16th, 2024)

Omada Hardware Controller_V5.14 Pre-release (Released on Apr 16th, 2024)
Omada Hardware Controller_V5.14 Pre-release (Released on Apr 16th, 2024)
2024-04-15 12:17:42 - last edited 2024-05-29 11:37:20

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

Best Regards! >> Omada EAP Firmware Trial Available Here << >> Get the Latest Omada SDN Controller Releases Here << *Try filtering posts on each forum by Label of [Early Access]*
  3      
 
  3      
 
#1
Options
20 Reply
Re:Omada Hardware Controller_V5.14 Pre-release (Released on Apr 16th, 2024)
2024-04-22 08:43:45

  @Hank21

After updating there's a pop up that says that the Open API and the build in RADIUS will be deleted in 5.15.

Whats the reason? For smaller scenarios nobody wants to use an external radius on dedicated hardware.

We're using this feature a lot in UniFi environments, and were really glad to see this feature integrated in Omada just a few versions ago.

Please consider supporting a simple built in RADIUS in the upcoming versions.

  5  
  5  
#3
Options
Re:Omada Hardware Controller_V5.14 Pre-release (Released on Apr 16th, 2024)
2024-04-22 18:18:58

Hi @Hank21, yesterday I updated my OC200 v1.0 controller to beta firmware 1.30.2_20240410_rel31241, after which I had several issues with DHCP reservation and IP-MAC Binding for my several VLANs. Some of the clients ended up in the correct VLAN with the correct IP address, but several just remained in the default VLAN with IP addres 192.168.1.x where it should be 192.168.2.x or 192.168.3.x, depending on the VLAN.

 

Rebooting my ER605 v2.0 router with firmware 2.2.4 and my two SG2210P v5.20 switches with firmware 5.20.1 did not solve the issue, after which I had to downgrade my OC200 to firmware 1.29.21 Build 20240401 Rel.52515 and lost all of my settings. Luckily I had a backup of my settings available.

  0  
  0  
#4
Options
Re:Omada Hardware Controller_V5.14 Pre-release (Released on Apr 16th, 2024)
2024-04-23 21:06:41 - last edited 2024-04-23 21:07:35

 @WM1

 

Hi,

at wireless lan it has a new option at "VLAN" there you like to change from VLAN-ID to Network Name/ID.

After this you will got back your IP's 192.168.1.X / 192.168.2.X / 192.168.3.X / usw.

 

Greetings Thorsten smiley

 

 

  0  
  0  
#5
Options
Re:Omada Hardware Controller_V5.14 Pre-release (Released on Apr 16th, 2024)
2024-04-24 02:35:27

 

Philldu wrote

  @Hank21

After updating there's a pop up that says that the Open API and the build in RADIUS will be deleted in 5.15.

Whats the reason? For smaller scenarios nobody wants to use an external radius on dedicated hardware.

We're using this feature a lot in UniFi environments, and were really glad to see this feature integrated in Omada just a few versions ago.

Please consider supporting a simple built in RADIUS in the upcoming versions.

Hi @Philldu 

To optimize the start up time of hardware controller especially the OC200, there might be some upgrade including the enhancement/deletion of some features/server. 

 

Regarding the built-in radius, we will collect feedback and the developer department will continue to evaluate it in combination with the product's performance.

Best Regards! >> Omada EAP Firmware Trial Available Here << >> Get the Latest Omada SDN Controller Releases Here << *Try filtering posts on each forum by Label of [Early Access]*
  1  
  1  
#6
Options
Re:Omada Hardware Controller_V5.14 Pre-release (Released on Apr 16th, 2024)
2024-04-24 02:37:11

  @Hank21 Is DPI possible in 5.15?

  0  
  0  
#7
Options
Re:Omada Hardware Controller_V5.14 Pre-release (Released on Apr 16th, 2024)
2024-04-24 03:07:01

 

ceejaybassist wrote

  @Hank21 Is DPI possible in 5.15?

Hi @ceejaybassist 

As far as I know, the DPI function is still under developing on the hardware controller and we have not been informed of the exact date nor it can be guaranteed. But we might expect that it will be added into the hardware controller in the future released version. Please keep an eye on the official website and forum. Thanks!

Best Regards! >> Omada EAP Firmware Trial Available Here << >> Get the Latest Omada SDN Controller Releases Here << *Try filtering posts on each forum by Label of [Early Access]*
  0  
  0  
#8
Options
Re:Omada Hardware Controller_V5.14 Pre-release (Released on Apr 16th, 2024)
2024-05-01 06:16:20

Hank21 wrote

 

Philldu wrote

  @Hank21

After updating there's a pop up that says that the Open API and the build in RADIUS will be deleted in 5.15.

Whats the reason? For smaller scenarios nobody wants to use an external radius on dedicated hardware.

We're using this feature a lot in UniFi environments, and were really glad to see this feature integrated in Omada just a few versions ago.

Please consider supporting a simple built in RADIUS in the upcoming versions.

Hi @Philldu 

To optimize the start up time of hardware controller especially the OC200, there might be some upgrade including the enhancement/deletion of some features/server. 

 

Regarding the built-in radius, we will collect feedback and the developer department will continue to evaluate it in combination with the product's performance.

Please do keep the RADIUS server; that is a desirable feature, I can deal with the extended boot time!

  3  
  3  
#10
Options
Re:Omada Hardware Controller_V5.14 Pre-release (Released on Apr 16th, 2024)
2024-05-01 11:04:06

  @Hank21 

 

+1 on keeping onboard RADIUS support (can leave it disabled by default to improve boot times for those that don't need it)

<< Paying it forward, one juicy problem at a time... >>
  4  
  4  
#11
Options
Re:Omada Hardware Controller_V5.14 Pre-release (Released on Apr 16th, 2024)
2024-05-01 18:54:33

  @Totti_14 thanks for posting this.  You saved me a lot of time tracking down my issue.

 

I have an OC200 and was running 5.13.  I have three Wireless WLANs/SSIDs.  Each was configured with a VLAN using the "By VLAN ID" option.  This worked with 5.13, but upon upgrading to 5.14.0.21 the APs stopped VLAN tagging the 3 WLANs.  The controller configuration still showed the VLANs being configured on each WLAN, but no tagging.  To resolve it I had to create 3 VLANs under "Wired Networks->LAN" and then change the WLANs to set the VLAN using the "By Network" option.  Now the WLAN traffic is being properly tagged again.

 

I don't have Omada switches so I don't really use the "Wired Networks" part of the config.  Maybe I should have.  But I'd say this is a bug.  If the WLAN allows me to configure a VLAN ID (numeric value), then that should be applied.  Having this behavior break during an upgrade can be very disruptive.  I got very lucky to have found the solution quickly.

 

  2  
  2  
#12
Options
Re:Omada Hardware Controller_V5.14 Pre-release (Released on Apr 16th, 2024)
2024-05-02 05:19:15

Well that was an unpleasant experience!

There was nothing in the release notes about deprecating the OpenAPI. I depend on this as a workaround to get DNS resolution of local hosts. The only notification was a popup after the installation!!

I got lucky in that I did have a backup of the configuration because downgrading back to the prior version deleted the entire config. Ugh.

Please don't take away the API!! At least not until we have DNS for localhosts built in along with the DHCP server!!

 

  4  
  4  
#13
Options
12

Information

Helpful: 3

Views: 6555

Replies: 20

Related Articles
Omada SDN Controller_V5.14 Pre-release (Released on Feb 29th, 2024)
8193 4
Omada SDN Controller_V5.14 Pre-release (Released on Feb 29th, 2024)
10 0
Omada Hardware Controller 5.1.7 Release Date?
1392 2
Omada Hardware Controller OC400 V1_1.1.1 Pre-Release(Released on Mar 20th, 2024)
1187 2
Omada SDN Controller_V5.15.6.4 Pre-Release Firmware(Released on Oct 18th, 2024)
7727 1
Omada hardware
259 0
About Us
Press
Copyright © TP-Link Systems Inc. All rights reserved.