Early Access Hardware Controllers Omada SDN Controller 6.1 Pre-Release Firmware (Released on 22nd Dec, 2025)
Early Access Hardware Controllers Omada SDN Controller 6.1 Pre-Release Firmware (Released on 22nd Dec, 2025)
This Article Applies to
OC200(UN)_V1_1.38.7_pre-release (Built-in Omada SDN Controller 6.1.0)
OC200(UN)_V2_2.23.7_pre-release (Built-in Omada SDN Controller 6.1.0)
OC220(UN)_V1_1.3.7_pre-release (Built-in Omada SDN Controller 6.1.0)
OC220(UN)_V2_2.2.3_pre-release (Built-in Omada SDN Controller 6.1.0)
OC300(UN)_V1_1.32.7_pre-release (Built-in Omada SDN Controller 6.1.0)
OC400(UN)_V1_1.10.7_pre-release (Built-in Omada SDN Controller 6.1.0)
Overview
We hope to offer you the opportunity to experience the new features added in Controller v6.1.0.10 in advance, and to allow TP-Link to thoroughly test the firmware in your real network environment and across scenarios before the official release. All feedback is welcome, including reports of successful upgrades.
Release Notes
Version Info
This version of the Controller is fully compatible with the Omada App version 5.0.x or later.
Supported Device Models
For device models Omada Software Controller supports, refer to the Omada Cloud SDN Platform Compatibility List.
Added support for Access Points: EAP 725-Outdoor v1.0.
New Features
- Added support for automatic RF optimization through spectrum scanning and RRM: APs continuously report interference, the Controller applies user-defined optimization settings, and all changes are logged in History in Site > Network Config > WLAN > WLAN Optimization > Auto WLAN Optimization > Adaptive Mode.
- Added support for RadSec (RADIUS over TLS) to secure SSID, MAC-Based, and 802.1X authentications on both APs and Switches in Site > Network Config >Profile > RADIUS Profile (requires the latest AP/Switch firmware; not yet available for Built-in RADIUS, RADIUS Proxy, Portal, or SSL-VPN).
- Added support for expiration and bandwidth controls on PPSK-without-RADIUS profiles, letting administrators set time-based validity (permanent, calendar range, post-creation interval, or daily window) and rate-limit or custom-speed restrictions in Site > Network Config > Profile > PPSK (requires compatible AP firmware).
- Added support for Auto VLAN assignment when bulk-generating PPSKs, automatically allocating VLANs across a user-defined range and step in Site > Network Config > Profile > PPSK.
- Added support for EAP 802.1X authentication (moved from Pro), establishing port-based 802.1X between clients and switches in Site > Network Config > Authentication > 802.1X (requires updated firmware).
- Added support for DHCP Option 82 configuration on SSIDs (moved from Pro), allowing relay-agent information to be inserted in DHCP packets in Site > Network Config > WLAN > SSID (requires updated firmware).
- Added support for Bluetooth Console, enabling APP-based Bluetooth serial access and unifying Aging Time & Transmit Power settings in a new Radio Setting page, while extending IoT Transport Stream with WebSocket/MQTT/AMQP and SSL/TLS security in Site > Device Config > EAP > Bluetooth(requires updated firmware).
- Added support for 802.11r fast roaming under WPA3-Enterprise encryption on SSIDs in Site > Network Config > WLAN > SSID (requires updated firmware).
- Added support for automatic IP refresh on switches after a gateway change: when enabled in DHCP-client mode, switches periodically probe the gateway and re-request an IP if the probe fails, eliminating the wait for lease expiry after a gateway replacement or subnet modification in Site > Network Config > Site Settings > General Config > Automatic Gateway Detection. (requires updated firmware).
- Added support for domain-name input in switch ping and traceroute troubleshooting tools in Site > Network Tools > Network Check and in Device > Switch Details > Tools > Network Check (requires updated firmware).
- Added support for switch diagnostic tools—Packet Capture, ARP Table, and DNS Lookup—in Site > Network Tools and in Device > Switch Details > Tools > Network Check (requires updated firmware).
- Added support for VRF (Virtual Routing and Forwarding) on L3 switches, allowing multiple isolated routing instances with overlapping IP addresses in Device Details > Config > VRF (requires device firmware upgrade).
- Added support for FEC (Forward Error Correction) on switches, allowing users to turn error-recovery on or off to balance signal quality and latency in Device > Ports > FEC.
- Added support for displaying LLDP and OSPF neighbor tables directly on the switch detail page to speed up troubleshooting in Device > Switch Details > Network View.
- Added support for a global LLDP toggle that controls advertisement on gateways, switches, and APs to improve topology accuracy in Site > Network Config > Site Settings > General Config.
- Added support for a new UI that sets Network, Port, and Custom QoS policies on any managed switch to mitigate congestion in Site > Network Config > Transmission > Switch QoS.
- Added support for redundant RADIUS servers in Switch 802.1X: if the primary server times out, the switch automatically falls back to the configured backup servers in Site > Network Config > Authentication > Switch 802.1X > RADIUS Profile.
- Added support for domain-name-based RADIUS servers for both authentication and accounting in Switch 802.1X in Site > Network Config > Authentication > Switch 802.1X > RADIUS Profile.
- Added support for RADIUS CoA & DM in Switch 802.1X, enabling re-authentication and forced disconnect in Site > Network Config > Authentication > Switch 802.1X > RADIUS Profile.
- Added support for preserving management VLAN, port, and static-route settings when adopting Agile Series switches through a user-defined management VLAN in Device > Switch Details > Port Config and Device > Switch Details > Management VLAN.
- Added support for dynamic SDM templates that re-allocate hardware resources per feature (e.g., enlarge ACL scale) and a single-port mode for higher ACL utilization in Device > Config > General > Advanced.
- Added support for DHCP Snooping in Controller mode, classifying interfaces as trusted or untrusted to ensure clients receive IP addresses only from authorized DHCP servers and to block DHCP-based attacks in Network Config > Security > IMPB.
- Added support for an untagged Voice Network mode on switch ports with configurable DSCP priority to maintain voice-packet precedence across the network in Device > Switch Details > Port > Voice Network.
- Added support for bulk license-unbind on Omada CBC controllers, allowing multiple devices to be released at once in Devices > Device List > Batch Action Batch Unbind.
- Added support for simultaneous firmware upgrades on multiple stack groups that share the same master model in Devices > Device Group > Stack Group (multi-select) > Config.
- Added support for simultaneous reboot of multiple stack groups in Devices > Device Group > Stack Group (multi-select) > Config.
- Added support for model-based CLI configuration, letting administrators push different command sets per switch model in Site > CLI Configuration > Model CLI.
- Added support for a free-text Description field on device and stack detail pages so users can record location or other notes in Device/Stack Details > General > Description.
- Added support for pre-configuring Ethernet port settings on offline-added EAPs in Devices > EAP Details > Port.
- Added support for user-selectable MAC-address delimiters (colon, hyphen, or none) and case formatting throughout the Controller UI in Global/MSP view > UI- Interaction > MAC Display Format.
- Added support for persistent user preferences—chart filters, table page size, and similar settings are saved and restored automatically across visits to Dashboard, Reports, and other core pages.
- Added support for a dedicated HTTPS port for firmware upgrades, separate from the main Controller web port, configurable in Global System Setting > Access Config > HTTPS Port for Upgrade.
- Added support for Disable NAT on a per-WAN basis while allowing multiple WANs to share the same LAN subnet, available in Site > Network Config > Transmission > NAT > Disable NAT (requires new device firmware).
- Added support for IP-Group-based ACLs on gateways: when direction is LAN→LAN, source and destination types can now be IP group, IP-port group, IPv6 group, or IPv6-port group in Site > Network Config > ACL.
- Added support for client identification in Global Settings > Controller Settings > Services on switches. After enabling the feature, opening TCP port 29817, and enabling Cloud Access, it can display Type, Vendor, Model, OS, and Version on the Clients list and detail pages. You can view results on the Clients list/detail pages (requires firmware 6.1).
- Added support for rapid client online/offline notifications from switches to the Controller, cutting detection delay to 0–5 seconds, enabled automatically when switches run firmware 6.1, and TCP port 29817 is open.
Enhancements
- Optimized the PPSK Open API by adding endpoints that allow individual PPSK entries within a profile to be created or deleted in Site > Network Config > Profile > PPSK.
- Optimized MAC Group scaling for switches: after a firmware upgrade, a single group can now deliver up to 2,000 MAC addresses instead of being truncated at 500 in Site > Network Config > Groups.
- Optimized DHCP Server setup on switches by enabling multi-range address pools under each gateway/subnet when DHCP Server mode is selected in Switch Details > Config > VLAN Interface and Site > Network Config > LAN.
- Optimized DHCP Reservation by letting users choose which DHCP server (gateway or switch) will honor each reservation in Site > Network Config > DHCP Reservation.
- Optimized the locate function in Site > Devices > Device List, Site > Clients, Switch/Stack Details> port, and Site > Device Config > Switch Ports: a. When Locate Switch or AP, all ports of the current device will flash, and the peer port of the Switch connected to it will also flash. b. Clients connected to the Switch via a wired connection support locating. When locating a client, the peer port of the Switch connected to it will flash. c. Ports and lags of Switch and Stack support locating.
- Optimized CLI feedback: erroneous commands issued via Site, Device, or Model CLI return immediate, highlighted error details in the configuration-result page in Site > Devices > Configuration Result.
- Optimized the Map-Heatmap page by coloring APs according to their connection status.
- Optimized stack-member ordering by sorting devices alphabetically by name in Device > Device Group > Stack Group.
- Optimized bulk operations by allowing simultaneous configuration of General Config and Loopback Control across multiple switches in Site > Devices > Device List > Batch Action > Batch Config.
- Optimized default chart behavior: the first online WAN port auto-expands in Gateway > port, the routing table defaults to the IPv6 tab when no IPv4 data exists in OLT Network View, and the Interference table defaults to the first populated band in Report > Top 5 Aps > Interference.
- Optimized multicast UI by adding per-device exceptions for Unknown Multicast and Report Suppression in Network Config > LAN > Multicast Snooping.
- Optimized IntelliRecover with configurable initial-reboot and retry-interval timers and relocated the feature to Site > Network Tools > IntelliRecover.
- Optimized air-interface usage by adding SSID management-frame rate controls in Site > Network Config > WLAN > SSID > 802.11 Rate Control.
- Optimized offline stack adoption by automatically onboarding all members instead of only the master in Devices > Device Group > Stack Group.
Bug Fixed
1. Fixed bug where broadcast MAC addresses could not be added to MAC Groups in Controller mode.
Notes
- Please note that Controllers on different platforms may vary in features, even if their first three digits of the version code are the same. For example, the Linux Controller currently supports Cluster Mode, but the Windows Controller doesn't support it yet.
- The Omada SDN Controller can only manage specific devices running the supported firmware. Please confirm that your device is compatible with the SDN Controller.
- Since version 5.14.32, the Omada Software Controller no longer supports upgrading from Controller v4.
- To strengthen overall security, we recommend upgrading all devices to the latest firmware.
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
OC200(UN)_V1_1.38.7_pre-release > Built-in Omada SDN Controller 6.1.0
OC200(UN)_V2_2.23.7_pre-release > Built-in Omada SDN Controller 6.1.0
OC220(UN)_V1_1.3.7_pre-release > Built-in Omada SDN Controller 6.1.0
OC220(UN)_V2_2.2.3_pre-release > Built-in Omada SDN Controller 6.1.0
OC300(UN)_V1_1.32.7_pre-release > Built-in Omada SDN Controller 6.1.0
OC400(UN)_V1_1.10.7_pre-release > Built-in Omada SDN Controller 6.1.0
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 recommended to save a copy of the current Log file and Backup Config file, which could help TP-Link investigate and address the problem quickly.
>> How to get the Log file and Backup Config file for Omada SDN Controller:
-
If your Windows software controller failed to launch, 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 to 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 to Export for Support, then click Export Running Logs to download the 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 to Export for Support, then click Export Running Logs to download the desensitized Log file.
-
For Omada Controller v5.5 or a 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
Dec 22nd, 2025
Provide the following firmware:
OC200(UN)_V1_1.38.7_pre-release > Built-in Omada SDN Controller 6.1.0
OC200(UN)_V2_2.23.7_pre-release > Built-in Omada SDN Controller 6.1.0
OC220(UN)_V1_1.3.7_pre-release > Built-in Omada SDN Controller 6.1.0
OC220(UN)_V2_2.2.3_pre-release > Built-in Omada SDN Controller 6.1.0
OC300(UN)_V1_1.32.7_pre-release > Built-in Omada SDN Controller 6.1.0
OC400(UN)_V1_1.10.7_pre-release > Built-in Omada SDN Controller 6.1.0
Recommended Threads
Omada Switch Pre-Release Firmware Adapting to Omada SDNC 6.1. (Released on December 18th, 2025)
EAP7xx v1.4.0 Fully Adapted to Omada 6.1 Pre-release Firmware (Update on 11th Dec, 2025)
EAP6xx Pre-release Firmware Adapted to Omada Controller v6.1 (Release on 12 Nov, 2025)
Wish you a happy life and smooth network usage! >Omada US Enterprise Beta Program Launch< >Get the Latest Omada SDN Controller Releases Here< >Experience the Latest Omada EAP Firmware<
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
@Vincent-TP That's great to hear!
I also noticed something eles, my SG3428X-M2 supports 802.1ab (LLDP/ LLDP-Med), at least what the german website says same for my SG2210P-V5.20. In the controller it says LLDP - The device does not support that functionality, not sure if it is a firmware bug or a controller bug (in the way of what the software outputs me) or not supported by the switch's firmware.
Not sure what the option above means "client detection".. at least what I think it supports that since the switch can say what clients are online/ availible but I don't know.
The VLAN thinggy is correct, not just completely translated, what means the switch does not support DHCP reservation, which he does not indeed since it is only L2+ and not fully L3.
- Copy Link
- Report Inappropriate Content
@Julian2111 And something I noticed as well, both switches should support 802.1p though, the controller tells me it is unsupported (ignore the green ticked one).
That is the configuration profile used on all ports (the 802.1p setting is the same for all 28 ports on the SG3428X-M2 and the 10 ports the SG2210p has) the same, besides for both on the uplink port.
Here as well not sure if it is a bug or a thing that is not supported by the switch or whatever it just tells me that, not sure if that came with that specific controller update (the issues mentioned upper came definetly with the controller update).
- Copy Link
- Report Inappropriate Content
GRL wrote
I had a lengthy back and forth with support on the "some devices on management vlan not being highlighted" issue
It is their design intention. Omada controller isnt vlan aware and therefore only ever exists on the management vlan. For EAPs, if it has a SSID associated with the management vlan, it will be highlighted, if it does not it will not be highlighted. This is likely why some are and some are not on your topology. Although i somewhat disagree in principal on those choices, its also somewhat logical so its just how it is
After some long, hard thought on this issue I must say that the support team is wrong on their decision to not highlight the controller and some EAPs when selecting the management VLAN. On a side note, I tested my EAP610 with a default SSID (no VLAN assigned) and it did highlight, so that part is OK if you follow their reasoning.
Why do I say that they are wrong? I firmly believe that any device that has an IP address on the management VLAN should be highlighted in any topology map, independently of the device (or client) being VLAN aware or not. The key is the IP address. All my EAPs have an IP address in the management VLAN and should be highlighted and not dependent on an SSID or being VLAN aware. An administrator needs to be able to see (and be aware of) all devices.
I hope that support may reconsider this at a later date.
- Copy Link
- Report Inappropriate Content
@GRL Thanks, I ran into same problem, was thinking what my options were. This is a nice stop gap, Appreciate the workaround
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 1050
Replies: 14
Voters 0
No one has voted for it yet.