Early Access Omada Switch Pre-Release FW Preview for SDN Controller 6.2.X.X (Update on Apr, 1st, 2026)
Release Notes
New Features:
1. Added support for NAT Traversal.
2. Added compatibility with Omada Config Tools V2.0.
3. Added support for Private VLAN.
4. Added support for Lightweight DHCPv6 Relay Agent (LDRA).
5. Added IGMP Snooping VLAN SSDP Flood to ensure that packets destined for multicast group 239.255.255.250 (commonly used for SSDP service discovery) are always flooded.
6. Added Extend Mode for non-PoE models.
7. Added support for configuring VLAN Isolation via SNMP.
8. Added a CLI command to display Spanning Tree Topology Change Notification (STP TCN) statistics for each port.
Enhancement:
1. Supported common MAC address formats for MAC address input fields.
2. Supported configuring 802.1X authentication in MAB-only mode.
3. Supported disabling DNS Adoption to meet specific network management requirements.
4. Optimized the fan status log reporting frequency.
5. Improved LLDP protocol compatibility.
6. Added system self-healing recovery capability to enhance long-term device stability.
7. Improved management link reliability.
8. Improved STP module reliability and optimize the stability of Spanning Tree operation.
Bug Fixes:
1. Fixed the issue where SNMP nodes Q-BRIDGE-MIB and BRIDGE-MIB did not comply with protocol specifications.
2. Fixed the issue of wired client loss in abnormal scenarios.
3. Fixed an issue where MAC address table entries for ports other than a specific port could not be displayed via CLI.
Firmware Download
Before the Upgrade
(1) Please be sure you have read the Beta Test Agreement before upgrading the Beta firmware!
(2) You may follow the following guide to upgrade your Omada devices. How to Upgrade/Downgrade Omada Switches
Firmware Download Link
You can download the TP-Linkmibs to work with your switch to experience more features.
Notes:
(1) We recommend using Find in Page (Ctrl/Command+F) to locate the exact model you have to ensure the correct firmware is installed.
(2) Your device’s configuration won’t be lost after upgrading.
Additional Information
All feedback is welcome, including letting us know about successful device upgrades.
If somehow you encounter an issue during or after the upgrade, it's suggested to contact us with the following info:
- Omada Controller version if you have any.
- Device Firmware version with Build number (previous and current)
If your model gets bricked during the firmware upgrade, you may follow the guide below to recover the firmware.
Configuration Guide How to Upgrade/Downgrade Omada Switches
Update Log
April, 1st, 2026
Add the following firmware versions:
March, 27th, 2026
Release of this article.
Recommended Threads
Omada_Network_Application_V6.2.x.x Pre-Release Firmware (Released on 11th Feb, 2026)
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
I see your point. This is the first time I have seen a firmware update change the hardware version but I have only been using Omada products for less than two years. That update occurred when there was a name change from Jetstream to Omada and I would guess that the hardware in the initial Omada model was the same hardware as the Jetstream model and only the outer case was changed. The version number change was probably done to eliminate confusion between the two models.
If the device's web interface now displays v3.20, then that is what you should always use to upgrade the unit.
- Copy Link
- Report Inappropriate Content
Hi @msankowski
If you have SG2008P V3.20 and SG2008 V4.20, then please try to update the firmware in this pre-release post with the same hardware versions which point to 3.20.20 and 4.20.20 respectively.
- Copy Link
- Report Inappropriate Content
@Vincent-TP For the new pre release 1.20.21 on my SG3428X-M2 V1.2 I noticed it fixes the issue of airplay being longer possible across VLANs but now my devices like my server that is running 24/7 or many IoT devices just appear offline if they are online.
And happy easter!
- Copy Link
- Report Inappropriate Content
@Julian2111 Not sure if it is the switch or the new firmware for the windows controller [6.2.0.17] because after around 2 days uptime the switch starts to disconnect from the controller and readopt, then the controller says adopt failed, then it works. But weridly I can not find any log in the controller that says "device disconnected" or anything similar.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 2
Views: 2592
Replies: 24
Voters 1
