Early Access Omada_Network_Application_V6.2.x.x Pre-Release Firmware (Updated on 10th Mar, 2026)
This Article Applies to
Omada_Network_Application_v6.2.0.x_Windows (Windows 10/11/Server, 64-bit Recommended)
Omada_Network_Application_v6.2.0.x_linux_x64.tar.gz
Omada_Network_Application_v6.2.0.x_linux_x64.deb
Overview
We hope to offer you the opportunity to experience the new features added in Controller vv6.2.0.x 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.3 or above.
Supported Device Models
For device models Omada Software Controller supports, refer to the Omada Cloud SDN Platform Compatibility List.
Added support for Access Points: Flex Bridge 5.
New Features
- Added support for configurable WAN-port PVID on gateways running firmware 6.2 in Devices > Gateway Details > Ports.
- Added support for FTP and SIP ALG settings, including editable FTP/SIP signaling ports, protocol type, peer-to-peer restriction, inactivity timers, and media timeout, for gateways on firmware 6.2 in Network Config > Transmission > NAT > ALG.
- Added support for e-mail alerts when new firmware is available in Firmware > Overview > Upgrade Settings: users can subscribe to any channel (default Stable) and receive automatic notifications whenever subscribed channels release new firmware images for devices on the controller, provided the mail server is configured
- Added support for a reorganized VPN management page in Network Config > VPN that unifies the entry workflow, maps legacy SSL VPN Server/User and WireGuard pages into the new structure, and expands WireGuard to server, client and auto site-to-site scenarios (requires firmware upgrade).
- Added support for configuring multiple DHCP address ranges within a single VLAN in site - Network Config > LAN > VLAN (requires Gateway 6.2 firmware).
- Added support for allowing the number of local and remote subnets in VPN tunnels to scale to the limit advertised by the device firmware in Network Config > VPN > VPN (requires Gateway 6.2 firmware).
- Added support for IPv4-over-IPv6 dial-up modes of MAP-E and DS-Lite on WAN interfaces, including optional custom DS-Lite domain names, in Network Config > Network Settings > Internet. Enabling these modes automatically activates IPv6. Some functions are not supported for DS-Lite and MAP-E dialing, including VPN, SD-WAN, IGMP, DDNS, UPnP, Disable NAT, Port Forwarding, and NAT ALG. (requires Gateway 6.2 firmware).
- Added support for a new DHCP User List page on the gateway that displays all active DHCP clients when the gateway operates as the DHCP server in Gateway Details > Network View > DHCP User List (requires Gateway 6.2 firmware).
- Added support for one-click creation of DHCP reservations from the DHCP User List, allowing administrators to import existing leases directly into the reservation table in Network Config > Transmission > DHCP Reservation > Add From DHCP User List.
- Optimized the SD-WAN wizard to auto-generate group names and automatically assign SD-WAN IPs to each member device, removing the manual IP Pool step in Global view > SD-WAN.
- Added support for SD-WAN scale expansion: increases site-capacity limits based on gateway model, offers both manual and auto LAN-segment conflict resolution when creating or editing groups, and introduces a new SD-WAN Map view in Global view > SD-WAN (requires Gateway 6.2 firmware).
- Added support for Hotspot Viewer accounts to print voucher codes directly from the voucher list in Hotspot > Vouchers > Voucher Groups.
- Added support for configurable DNS cache lifetime by adding a TTL setting to LAN DNS in Network Config > Network Settings > LAN - LAN DNS (requires Gateway 6.2 firmware).
- Added support for remote packet capture on gateway WAN ports or VLANs to aid network diagnostics in Network Tools > Packet Capture (requires gateway 6.2 firmware).
- Added support for rogue-DHCP-server detection: the gateway raises an alert whenever an unexpected DHCP server is detected on the LAN in Logs > Alerts (requires gateway 6.2 firmware).
- Added support for on-device DNS resolution to query domain-to-IP mappings directly from the gateway in Network Tools > Network Check > DNS Lookup (requires gateway 6.2 firmware).
- Added support for LAN-side IP-conflict detection; the gateway logs an alert whenever multiple MACs are detected using the same IP in Logs > Alerts (requires gateway 6.2 firmware).
- Added support for Timing-based link-back (failover): users can configure a time range after which traffic automatically fails back to the standby WAN, supplementing the existing failover modes in Site > Network Config > Network Settings > Internet (requires gateway 6.2 firmware).
- Added support for on-demand Speedtest in Site > Dashboard and scheduled Speedtest in Site > Network Config > Network Settings > Internet: initiate a test on any WAN or set daily/weekly/monthly schedules; results are graphed and stored historically (requires gateway 6.2 firmware).
- Added support for extending configurable VLANs up to 4094 on gateways, covering WAN, LAN, virtual-WAN and IPTV interfaces in Site > Network Config > Network Settings > Internet/LAN/IPTV (requires gateway 6.2 firmware).
- Added support for displaying the last-edit timestamp on each portal entry in Network Config > Authentication > Portal.
- Added support for showing voucher balance and quota-limit reminders on the portal post-auth success page, along with remaining session time and, if rate-limiting is enabled, remaining data for both voucher and local-user logins on the client success page after authentication.
- Added support for uploading separate background images for mobile and PC endpoints when creating or editing a portal in Network Config > Authentication > Portal > Add/Edit Portal > Design > Background > Unified Picture.
- Added support for using a hostname instead of an IP address for the RADIUS server in portal authentication in Network Config > Authentication > Portal.
- Added support for voucher statistics grouped by voucher group, letting administrators view usage totals per group in Hotspot > Vouchers > Statistics.
- Added support for LAN Network/VLAN columns in user tables and added export options for Top 5/10/20 Users, showing the network and VLAN where each client resides in Dashboard > Traffic > Clients and Insights > Application Analytics > Users.
- Added support for managing Pro/Campus devices within Omada Controller, enabling discovery, adoption, offline provisioning, site templates and mixed-mesh deployment, while health metrics, anomaly events and Heat-Map Pro models remain unavailable in Site > Device.
- Added support for displaying the timestamp and status of the latest GPS fix (manual or automatic) on EAP772-Outdoor in AP Details > Config > General (requires EAP772-Outdoor firmware 6.2).
- Added support for configuring a NAS-ID in switch 802.1X authentication in Network Config > Authentication > 802.1X (requires switch firmware 6.2).
- Added support for VLAN assignment when MAC-based authentication is selected in switch 802.1X in Network Config > Authentication > 802.1X (requires switch firmware 6.2).
- Added support for transparent SSDP forwarding when both IGMP Snooping and unknown-multicast discard are active by introducing the "Flood Known Protocols" option in Network Config > Network Settings > LAN > Multicast Snooping (requires Switch 6.2 firmware).
- Added support for real-time LACP member-status indication: LAG list now shows green for successfully negotiated, up members and red for failed members, with failure logs sent by the switch and stored in the Controller in Switch Details > Ports > LAG List (requires Switch 6.2 firmware).
- Added support for in-place toggling between Active and Passive LACP modes without deleting and recreating the LAG; Static LAG mode remains unchanged in Switch Details > Ports > LAG Detail (requires Switch 6.2 firmware).
- Added support for displaying the last-known uplink device and uplink port columns in the device list, preserving this information even after the device goes offline in Devices > Device List.
- Added support for configuring multiple DHCP-relay server addresses on a Switch VLAN interface (quantity limited by hardware) in Switch Details > Config > VLAN Interface > DHCP Relay (requires Switch 6.2 firmware).
- Added support for VLAN-aware topology highlighting: links in the VLAN topology diagram now change color to indicate whether the selected VLAN’s traffic can traverse each connection in Network Config > Network Settings > LAN and Dashboard > Topology.
- Added support for SDM template integration, allowing administrators to view and modify SDM template options directly within switch device templates in Site Template > Device Template (switch) > Config > General > Others > SDM Template (requires Switch 6.2 firmware; supported models listed).
- Added support for cloud-based remote access (NAT traversal) that lets administrators reach HTTP/HTTPS/SSH/Telnet services on private-LAN devices through a cloud-connected jump host, available for gateway 6.2 firmware and select switch/AP 6.2 builds in Network Tools > Remote Access and Client Details > Toolbox > Remote Access (Cloud Access must be enabled for Local Controller).
Enhancements
- Optimized the Internet page by moving Virtual WAN under Port Config and merging the separate Port Config and Load Balancing submit buttons into a single bottom action in Site > Network Config > Network Settings > Internet.
- Optimized Load Balancing logic to apply device-side settings when WAN Settings Overrides is disabled and added real-time port-status indicators under each WAN weight field to prevent user confusion in Site > Network Config > Network Settings > Internet > Load Balancing (requires gateway 6.2 firmware).
- Optimized Portal creation/editing with a rebuilt layout that groups settings more intuitively and exposes additional component-customization options in Network Config > Authentication > Portal.
- Optimized IP-input fields throughout the UI to accept a copied IP address pasted as a single string.
- Optimized Cloud Access with a redesigned connection flow that reduces cloud-request latency and improves overall user experience in Settings > Cloud Access.
- Optimized the DPI Rules Management page by replacing the single QoS toggle with a type selector that lets users choose between ACL and QoS rule types in Site > Network Config > Security > Application Control > Rules Management.
- Optimized controller security with built-in brute-force protection that locks login attempts after repeated password failures on "managed by other" devices in Controller (available now for AP & Gateway; Switch & OLT support planned for firmware 6.3).
- Optimized public OpenAPI documentation by completing deprecated-interface descriptions and correcting the categorization of site-template endpoints.
Bug Fixed
- Fixed bug where RADIUS Message-Authenticator was not forcibly validated, which could lead to RADIUS protocol security vulnerability (CVE-2024-3596), by adding support for enforcing Message-Authenticator verification when the “Require Message-Authenticator” option is enabled, in Site > Network Config > Profile > RADIUS Profile and Global/MSP > Settings > Server Settings > RADIUS Server.
- Fixed bug where RADIUS packets containing the Proxy-State attribute did not enforce Message-Authenticator validation, potentially exposing the system to RADIUS protocol security vulnerability (CVE-2024-3596), by adding support for limiting Proxy-State and enforcing Message-Authenticator verification when the “Limit Proxy-State” option is enabled, in Site > Network Config > Profile > RADIUS Profile and Global/MSP > Settings > Server Settings > RADIUS Server.
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
Omada_Network_Application_v6.2.0.15 Windows (Windows 10/11/Server, 64-bit Recommended)
Omada_Network_Application_v6.2.0.15 _linux_x64.tar.gz
Omada_Network_Application_v6.2.0.15 _linux_x64.deb
Omada_Network_Application_v6.2.0.12 Windows (Windows 10/11/Server, 64-bit Recommended)
Omada_Network_Application_v6.2.0.12 _linux_x64.tar.gz
Omada_Network_Application_v6.2.0.12 _linux_x64.deb
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
Mar 10th, 2026
Update the pre-release firmware as follows:
Omada_Network_Application_v6.2.0.15 Windows (Windows 10/11/Server, 64-bit Recommended)
Omada_Network_Application_v6.2.0.15 _linux_x64.tar.gz
Omada_Network_Application_v6.2.0.15 _linux_x64.deb
Update Note:
Add one new feature: Point 38.
Feb 11th, 2026
Provide the following firmware:
Omada_Network_Application_v6.2.0.12 Windows (Windows 10/11/Server, 64-bit Recommended)
Omada_Network_Application_v6.2.0.12 _linux_x64.tar.gz
Omada_Network_Application_v6.2.0.12 _linux_x64.deb
Recommended Threads
EAP7xx Fully Adapted to Omada 6.2 Pre-release Firmware (Released on 23rd Jan, 2026)
Hardware Controllers Omada SDN Controller 6.2 Pre-Release Firmware (Released on 4th Mar, 2026)
ER7206 V2 Pre-Release Firmware for SDN Controller 6.2.X.X (Released on February 12th, 2026)
ER707-M2 V1 Pre-Release Firmware for SDN Controller 6.2.X.X (Released on February 12th, 2026)
ER7406 V1 Pre-Release Firmware for SDN Controller 6.2.X.X (Released on February 12th, 2026)
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 - a few people were reporting to me (https://github.com/mbentley/docker-omada-controller/issues/740) that after upgrading to the 6.2.0.12 beta, they experienced a lot higher memory usage than normal. Since they were running it in a container with resource limits, their container was getting OOM killed due to the increase in memory utilization. I tried to replicate it on a test environment but I only have a few old EAPs to test with and not full environment. One person said they have a router (er605), switch(SG2008), two APs(EAP660HDs) and ~100 wireless clients.
What information can I have them provide that might help share info if debugging is required?
- Copy Link
- Report Inappropriate Content
@Vincent-TP For this version 6.2 support Omada Pro Switch and AP, But in normally Omada pro devices require license for manage i would like to know it still need license or not?
- Copy Link
- Report Inappropriate Content
@Vincent-TP I'm seeing the following error every 10 seconds, wondering if it's related to my memory issues:
03-02-2026 13:44:08.072 WARN [quartzScheduler_Worker-2] [] c.t.s.c.s.c.TaskExecutorService(): receive scheduled event with identity (omada_cloud, proxy_conn_manage) but did not execute because corresponding handler omada_cloud doesn't exist
I turned off Cloud Access and this continues anyway. I seem to be accumulating and maxing out on sessions as well.
- Copy Link
- Report Inappropriate Content
Hi @mbentley
Thanks for the feedback. I have forwarded your case to the support team, and you will receive an email from them soon. Please pay attention and continue troubleshooting with them. Thanks.
mbentley wrote
@Vincent-TP - a few people were reporting to me (https://github.com/mbentley/docker-omada-controller/issues/740) that after upgrading to the 6.2.0.12 beta, they experienced a lot higher memory usage than normal. Since they were running it in a container with resource limits, their container was getting OOM killed due to the increase in memory utilization. I tried to replicate it on a test environment but I only have a few old EAPs to test with and not full environment. One person said they have a router (er605), switch(SG2008), two APs(EAP660HDs) and ~100 wireless clients.
What information can I have them provide that might help share info if debugging is required?
- Copy Link
- Report Inappropriate Content
@Vincent-TP Is there any fix planned for random devices spawning on Switch Ports with AP attached? Delete them will bring them back after some time
SG3210XHP-M2 v3.0 with
- EAP655-Wall(EU) v1.0 (Port 4,6,7) with Firmwareversion 1.6.3
- EAP653(EU) v1.0 (Port 3) with Firmwareversion 1.3.5
The MAC Adresses are Part of the Mac-Adress of the AP.
AP: XX-XX-4A-84-DB-F4
Spawned MAC-Adresses 4A-84-DB-F4-XX-XX
- Copy Link
- Report Inappropriate Content
Hi @MattH001
Thanks for getting this to our attention. This will not affect normal use, and we are planning to fix it in the next release.
MattH001 wrote
@Vincent-TP I'm seeing the following error every 10 seconds, wondering if it's related to my memory issues:
03-02-2026 13:44:08.072 WARN [quartzScheduler_Worker-2] [] c.t.s.c.s.c.TaskExecutorService(): receive scheduled event with identity (omada_cloud, proxy_conn_manage) but did not execute because corresponding handler omada_cloud doesn't exist
I turned off Cloud Access and this continues anyway. I seem to be accumulating and maxing out on sessions as well.
- Copy Link
- Report Inappropriate Content
Hi @Tlezeed
Tlezeed wrote
@Vincent-TP For this version 6.2 support Omada Pro Switch and AP, But in normally Omada pro devices require license for manage i would like to know it still need license or not?
Thanks for asking, the answer is No.
- Copy Link
- Report Inappropriate Content
@Vincent-TP
Do you know if more gateways are going to receive pre-release firmware adapted for Omada Controller 6.2 anytime soon? I would love to test some of the new features, but on the network where I'm using beta firmware, I only have ER605 and ER706W gateways.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Hi @Vincent-TP ,
I was testing some gateways in the omada controller 6.2.0.15 and I found that with ER7602 V1 we are having this issue. We have connected a SG2218P in LAN/WAN2 port 4, SG2210P in LAN1 port 5 and a SG2008p in LAN2 port 6.
If you see topology it shows that all of them are connected between theyself, that is not correct, cause they are connected directy to the gateway.
This is not happening with ER707-M2, ER8411 or ER7412
Versions
ER7206 V1 - 1.4.3
SG2008p - 1.0.27
SG2210p - 3.20.28
SG2218 - 1.20.19
LLDP is enabled in general config for gateways, switchs and APs.
Regards
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 5295
Replies: 30
Voters 0
No one has voted for it yet.