Early Access ER7412-M2 V1 1.2.0 Adapted to Omada 6.2.14 Pre-Release Firmware (Closed)
This Article Applies to
a) ER7412-M2(UN) v1.0
b) ER7412-M2(UN) v1.6
c) ER7412-M2(UN) v1.20
d) ER7412-M2(UN) v1.26
e) ER7412-M2(UN) v1.30
f) ER7412-M2(UN) v1.36
Release Notes
Version Info:
This firmware is fully adapted to Omada Controller V6.2.14. To update to this pre-release version, please make sure your device version is not lower than the version listed below:
a) UN v1.0: 1.1.0 Build 20251015 Rel.63594
b) UN v1.6: 1.1.0 Build 20251015 Rel.63594
c) UN v1.20: 1.1.0 Build 20251015 Rel.63594
d) UN v1.26: 1.1.0 Build 20251015 Rel.63594
e) UN v1.30: 1.1.1 Build 20251112 Rel.54883
f) UN v1.36: 1.1.1 Build 20251112 Rel.54883
New Features:
- Add support for V6plus/DS-Lite Dial-up.
- Add support for configuring multiple segments of the DHCP IP pool when acting as a DHCP server.
- Add support for showing a list of clients obtaining IP addresses via DHCP when adopted on the controller.
- Add support for multi-channel configuration, currently supports entering standalone UI to configure while disconnected from the controller.
- Add support for SpeedTest.
- Add support for configuring ports of SIP ALG.
- Add support for NAT Traversal.
Enhancements:
- Optimized boot-up time
- Optimized system stability
- Optimized menu layout
- Optimized the efficiency of the network configuration deployment
- Optimized the resource consumption of the traffic statistic
- Optimized the configuration of Load Balance
- Optimized the configuration logic of the VPN
- SD-WAN capacity expanded.
- Enhanced device security.
Bug Fixed:
- Fixed the problem that DHCP Option 2 does not allow negative values to be entered.
- Fixed the problem that gateway does not report the serial number (S/N) information to the controller.
- Fixed the problem that ACL rules do not take effect for VPN users.
- Fixed the problem that when DHCP address pool still has available addresses, no log is generated when the DHCP server reaches the device specification limit.
- Fixed the problem that when invalid LAN name is configured on the controller, the rules are lost during a full configuration push, and the associated LAN DNS configuration becomes ineffective.。
- Fixed the problem that The mDNS Repeater feature cannot process mDNS packets containing the NSEC record type.
- Fixed the problem that Manrope font is displayed incorrectly across the router web UI.
- Fixed the problem that traceroute traffic may go out via backup WAN while primary WAN isonline with link backup configured.
- Fixed the problem that IPv6 dial-up affects IPv4 Online Check detection.
- Fixed the problem that after a switch upgrade, the switch disconnects and cannot obtain an IP address from the gateway via DHCP.
- Fixed the problem that the built-in L2TP client on Windows PCs automatically disconnects one minute after connecting to the gateway’s L2TP server.
- Fixed the problem that the USB modem dial-up status is not displayed in System Status page after reboot when the USB modem is in 3G dial-up mode.
- Fixed the problem that blocking a specific client does not take effect after rebooting the device when multiple clients are connected.
- Fixed the problem that PADI Timeout when customer configured PPPoE Profile on Cloud-Based Controller.
- Fixed the problem of LLDP packet abnormalities.
- Fixed the problem of wired clients reporting issue.
- Fixed the problem that some LAN IPs randomly cannot access HTTPS websites (TCP/443 unreachable) after multiple WAN failovers.
- Fixed the problem of SD-WAN disconnection caused by WAN Alias configuration.
- Fixed the problem of all config wiped on gateway caused by incomplete configuration pushed from Controller.
- Fixed the problem that device cannot access server IP when gateway acting as OpenVPN server in full mode, causing the device unable to be adopted by Controller on server side.
- Fixed the problem of port forwarding rules not taking effect occasionally after device reboot.
- Fixed the problem of part of the logs were lost while link backup enabled.
- Fixed the problem of device reporting neighbors with similar MAC address as itself through LLDP.
- Fixed the problem of occasional high CPU utilization under IPv6 Dial-up scenario.
- Fixed the problem of device adding the virtual subnet of SSL VPN and OpenVPN to device Remote Management.
- Fixed the problem of unable to auto re-connect occasionally after PPPoE Dial-Up failure.
- Fixed the problem of Internet access abnormal when WAN MTU is set smaller than 1500.
- Fixed the problem of Policy Routing rules not taking effect to part of the traffic.
- Fixed the problem of occasional IPsec tunnel establishment failure when same Phase1 parameters configured on both ends.
- Fixed the problem of ACL unable to take effect on IPsec VPN traffic.
- Fixed the problem of reporting unknown clients occasionally.
- Fixed the problem of DHCP Relay not taking effect.
- Fixed the problem of OpenVPN Client unable to connect occasionally after device reboot.
- Fixed the problem that when device is acting as OpenVPN Client, OpenVPN Server cannot actively access the device via SNMP.
- Fixed the problem of more than 7 simultaneous SIP calls would fail in certain scenarios.
- Fixed the problem of the contents of the Recv-Q queue in the DHCPv6 server were not being read.
- Fixed the problem of the region associated with certain IP addresses was inaccurate.
- Fixed some security vulnerabilities.
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 Gateways
Firmware Download Link
ER7412-M2_1.2.0 Build 20260630 Rel. 82947
Notes:
(1) The above firmware applies to the described models.
(2) Your device’s configuration won’t be lost after upgrading.
(3) If you have disabled the HTTPS port, please enable the HTTPS port before upgrading the firmware.
Additional Information
All feedback is welcome, including letting us know about successful device upgrades.
If somehow you encounter an issue during or after the router upgrade, it's suggested to contact us with the following info:
- Omada Controller version
- Device Firmware version with Build number (previous and current)
If your router gets bricked during the firmware upgrade, you may follow the guide below to recover the firmware.
How to use the Emergency Mode to recover the firmware for Omada Gateways
Update Log
July 27th, 2026:
Closed this trail. To download the latest firmware, please go to TP-Link official website.
July 6th, 2026:
Release of this post.
Recommended Threads
Hardware Omada SDN Controllers V6.2.14.x Pre-Release Firmware
Omada_Network_Application_V6.2.14.x Pre-Release Firmware
Get the Latest Firmware Releases for Omada Routers Here - Subscribe for Updates
Get the Latest Omada SDN Controller Releases Here - Subscribe for Updates
Experience the Latest Omada EAP Firmware - Trial Available Here, Subscribe for Updates!

