Early Access Omada SDN Controller_V5.14.32 Pre-release (Updated on Nov 8th, 2024)
This Article Applies to
Omada_SDN_Controller_v5.14.32.3 Windows (Windows 7/8/10/11/Server, 64bit Recommended)
Omada_SDN_Controller_v5.14.32.3_linux_x64.tar
Omada_SDN_Controller_v5.14.32.3_linux_x64.deb
OC200(UN)_V1_1.32.6_pre-release (Built-in Omada SDN Controller 5.14.32.56)
OC200(UN)_V2_2.17.6_pre-release (Built-in Omada SDN Controller 5.14.32.56)
OC300(UN)_V1_1.26.6_pre-release (Built-in Omada SDN Controller 5.14.32.56)
OC400(UN)_V1_1.4.6_pre-release (Built-in Omada SDN Controller 5.14.32.56)
Overview
We hope to offer you a chance to experience the new features added in the Controller v5.14.20 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 letting us know about successful upgrades.
Release Notes
New Features
1. Added support for gateways: ER8411 v1.2, ER7412-M2 v1.2, ER706W v1.2, ER605 v2.2.
2. Added support for APs: EAP 772 v2.
3. Added support for Controller IP Access Rules in Global View > Settings > Account Security.
4. Added support for Upgrade Logs, Upgrade Schedules, Beta Firmware Program, Cloud Firmware Pool and other function in Global view > Firmware.
5. Added support for Audit Logs unit in Global View: user’s operations will be recorded to facilitate system maintenance.
6. Added support for configuring following features with Omada APP:
- Bandwidth Control
- Deep Packet Inspection
- IPS/IDS
- IP Group
- MAC Filtering
- Dynamic DNS
- WLAN Optimization
- Load Balancing
Enhancements
1. Optimized Backup, added support of selection of configurations and data.
2. Optimized Restore, data is no longer supported to be kept after restoring backup file, only configurations can be kept.
3. Optimized distribution of Export Data, added support for exporting data in the corresponding features module directly.
4. Optimized adaptability to SSL certificate, added support for importing certificate chain file of PEM format in Global view > Settings > System Settings > HTTPS Certificate.
5. Optimized default settings, enabled Fast Roaming, Gateway LLDP automatically.
6. Optimized the stability when using the terminal of devices.
7. Optimized the performance when managing clients in huge scale.
8. Optimized the Upgrade Schedule, added support to select model for upgrading, not single device anymore.
Notes
1. This version of the Controller is fully applied to the Omada APP of version 4.17 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. Since version 5.14.32.2, Omada Software Controller no longer supports upgrade from Controller v4.
4. Since version 5.14.32.2, Omada Software Controller(windows) only supports installation on Windows64-bit platform.
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 upgrading or downgrading.
(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
Omada_Controller_Windows_v5.14.32.3
Omada_SDN_Controller_v5.14.32.3_linux_x64.tar
Omada_SDN_Controller_v5.14.32.3_linux_x64.deb
OC200(UN)_V1_1.32.6 (pre-release version) > Built-in Omada SDN Controller 5.14.32.56
OC200(UN)_V2_2.17.6 (pre-release version) > Built-in Omada SDN Controller 5.14.32.56
OC300(UN)_V1_1.26.6 (pre-release version) > Built-in Omada SDN Controller 5.14.32.56
OC400(UN)_V1_1.4.6 (pre-release version) > Built-in Omada SDN Controller 5.14.32.56
Omada_Controller_Windows_v5.14.32.2 (Pre-release version)
Omada_Controller_Windows_v5.14.32.2
Omada_SDN_Controller_v5.14.32.2_linux_x64_20240920174215.tar
Omada_SDN_Controller_v5.14.32.2_linux_x64.tar.gz
Omada_SDN_Controller_v5.14.32.2_linux_x64_20240920174223.deb
Omada_SDN_Controller_v5.14.32.2_linux_x64.deb
OC200(UN)_V1_1.32.5 (pre-release version) > Built-in Omada SDN Controller 5.14.32
OC200(UN)_V2_2.17.5 (pre-release version) > Built-in Omada SDN Controller 5.14.32
OC300(UN)_V1_1.26.5 (pre-release version) > Built-in Omada SDN Controller 5.14.32
OC400(UN)_V1_1.4.5 (pre-release version) > Built-in Omada SDN Controller 5.14.32
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 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.
-
Update Log
Nov 8th, 2024:
Add the following controller firmware for early access.
- OC200(UN)_V1_1.32.6 (pre-release version) > Built-in Omada SDN Controller 5.14.32.56
- OC200(UN)_V2_2.17.6 (pre-release version) > Built-in Omada SDN Controller 5.14.32.56
- OC300(UN)_V1_1.26.6 (pre-release version) > Built-in Omada SDN Controller 5.14.32.56
- OC400(UN)_V1_1.4.6 (pre-release version) > Built-in Omada SDN Controller 5.14.32.56
Update the Omada Software Controller pre-release version to the official release.
Oct 30th, 2024:
Remove download links for all the controllers 5.14.32.
Oct 28th, 2024:
Add the following controller firmware for early access.
- OC200(UN)_V1_1.32.5 (pre-release version) > Built-in Omada SDN Controller 5.14.32
- OC200(UN)_V2_2.17.5 (pre-release version) > Built-in Omada SDN Controller 5.14.32
- OC300(UN)_V1_1.26.5 (pre-release version) > Built-in Omada SDN Controller 5.14.32
- OC400(UN)_V1_1.4.5 (pre-release version) > Built-in Omada SDN Controller 5.14.32
Update the Omada Software Controller pre-release version to the official release.
Sep 26th, 2024:
Provide the following controller firmware for early access.
- Omada_Controller_Windows_v5.14.32.2 (Pre-release version)
- Omada_SDN_Controller_v5.14.32.2_linux_x64_20240920174215.tar
- Omada_SDN_Controller_v5.14.32.2_linux_x64_20240920174223.deb
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
Thank you so much for your love of our product. Your support means a great deal to us.
We can store logs or other files on USB sticks.
The configuration options should be on under Global View, Settings > Maintenance.
As for the TCP SYN attack concern, you may learn something from the following posts:
https://community.tp-link.com/en/business/forum/topic/649386
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
@Vincent-TP
I'm running
Your version numbers have me a little confused. Why is the pre-release a lower version minor number 14 and updated on nov 8th? So what is this 5.15 im running? What exactly is going on here lol.
I am running on debian very happy to be running it on my proxmox virtual environment behiond my my PFSense VM. on a debian production homelab vm
- Copy Link
- Report Inappropriate Content
Hi @n0izee
You are running software controller, which has a beta version 5.15.6.4.
This post is mainly discussing beta software for hardware controllers. Hardware controller updates are a little slower than software controllers.
- Copy Link
- Report Inappropriate Content
This latest version on OC200 v1 left my ER8411 in a "Disconnected" state and requiring a power cycle.
All other switches and EAPs were re-adopted normally.
No WAN settings being wiped this time.
- Copy Link
- Report Inappropriate Content
@GRL Happens to me for the remote ERs each time there is an update. Seems to be a problem with this router, read many posts on this. Operating a SW controller, had an OC 300 before.
- Copy Link
- Report Inappropriate Content
OK, thank you. I did have a HW controller however.... in the world of hypervisors, containers docker docker-compose VM's etc. and of course TP Links releasing a software version of the controller, it's just easier to use the SW version. Although I might've kept the HW controller if it didn't give me so much trouble with losing access to the management interface. Mind you, I am using a Jetstream l2 managed switch. I have opted not to use the cloud SDN features on the switch, I am managing my EAPS with the SDN though.
I do all this in my home lab and I have deployed a couple of these setups to clients. I don't know whose in charge of what over there, but if you guys could kinda tech illiterate proof the hotspot manager so that it's easier for the employees at sites where I deploy setups for them to give out Wi-Fi access codes. That'd be so great.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Eg64 wrote
@GRL Happens to me for the remote ERs each time there is an update. Seems to be a problem with this router, read many posts on this. Operating a SW controller, had an OC 300 before.
@Eg64
I wanted an OC300 but ended up with the OC200, which is fine for a home lab. It's great to have a built-in backup boot mode with a recovery management interface and process for the HW controller. Honestly, a RESET button would have been much nicer. It is a huge PAIN to have to go through that process on anything other than a rare occasion for a true failed firmware update. With the SW I do this.
Yes, not best practices being logged into as root I know. But it's my home lab production mock up, still no excuse. don't sudo passwd on as fresh install, it's bad security hygiene.
I included the version info but anyway ssh has its benefits and convenience, and I'd been ok with a hard RESET button on the OC200, I wonder why they left it out? From a security standpoint, physical access is supposed to be locked in a secure area for a production network stack, so I can't imagine they were preventing malicious or mischievous pushes of said button. But still I wonder.
- Copy Link
- Report Inappropriate Content
I have my OC 200 on its very own, basic TPlink "easy smart" poe switch (SG105PE) with POE recovery set so that if the switch cant ping the IP of the controller on its port, it waits a minute then power cycles the POE on that port. I havent actually had any issues with being unable to access the controller, but i have tested my solution by temporarily changing my controller IP address and it works as i expected it to by hard resetting the controller. The other benefit is that if the controller is still responding to pings, but otherwise inaccessible for some reason, i can just reboot that switch from its web gui completely independantly of omada and therefore the controller would reboot too.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 1
Views: 7048
Replies: 53
Voters 1
