Early Access ER605 V2 2.4.0 Build 20260417 Pre-Release Firmware (Released on Apr 24th, 2026)
This Article Applies to
a) ER605(UN) v2.0
b) ER605(UN) v2.6
c) ER605(IN) v2.8
d) ER605(UN) v2.20
e) ER605(UN) v2.26
f) ER605(IN) v2.28
g) ER605(UN) v2.30
h) ER605(UN) v2.36
i) ER605(IN) v2.38
j) ER605(BR) v2.36
Release Notes
Version Info:
Firmware for ER605(UN) 2.x. This firmware is fully adapted to Omada Controller V6.2.0.17
Minimum FW Version for Update: 2.3.2 Build 20251029 Rel. 12727 and above.
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
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.
Bug Fixed:
- Fixed the problem that DHCP Option 2 does not allow negative values to be entered.
- Fixed the problem that the 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 the 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 an 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 is online 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 periodic CPU utilization spike on ER605v2.
- Fixed the problem that Wireguard VPN throughput drops after upgrading to 2.3.1 version.
- Fixed the problem that a 15-20 seconds delay is presented before ACL and policy routing take effect after a VPN disconnection.
- Fixed the problem of OpenVPN occasionally fails to connect and toggling the VPN server/client off and on is required to restore connectivity.
- Fixed the problem of IPsec VPN failed to establish with error code NO_PROPOSAL_CHOSEN returning.
- Fixed the problem of IP Statistics occasionally shows many duplicated entries.
- Fixed the problem of device adoption loop while multi-WAN configured.
- Fixed the problem that device adding VPN virtual subnet into Remote Management allow address.
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
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
Apr 24th, 2026:
Update the release note:
remove the following entries:
Apr 24th, 2026:
Release of this post.
Recommended Threads
Omada_Network_Application_V6.2.10.x Pre-Release Firmware (Updated on 17th Apr, 2026)
Hardware Controllers Omada SDN Controller 6.2.10 Pre-Release Firmware (Update on 21st Apr, 2026)
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!
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
@Vincent-TP OK . Found it in site to site as you said. The only thing missing is the names of the peers. Moreover if I add a name to a peer, it is not being saved.
- Copy Link
- Report Inappropriate Content
Hi @fesarli
Thanks for the feedback. What's showing on the peers' name column, is it "-", or blank? Could you please share a screenshot? Thanks.
fesarli wrote
@Vincent-TP OK . Found it in site to site as you said. The only thing missing is the names of the peers. Moreover if I add a name to a peer, it is not being saved.
- Copy Link
- Report Inappropriate Content
@Vincent-TP just upgraded my ER605 v2 to this pre-release firmware in a production-like home lab environment and the experience was very positive so far.
Current setup:
-
ER605 v2
-
Dual WAN (same ISP on both WANs)
-
Omada Software Controller (cloud-managed)
-
EAP650
-
Load balancing enabled
Upgrade process was smooth:
-
no adoption loop
-
no configuration loss
-
DHCP reservations preserved correctly
-
AP reprovisioning completed normally
-
cloud reconnection was fast
One important improvement I noticed:
traffic statistics/reporting seems significantly better now.
Before this build, many wired/wireless clients frequently showed:
"Download Traffic = 0"
After upgrading, client traffic reporting appears to be working much more accurately.
Dual WAN behavior also appears stable after reboot and reprovisioning.
So far this build feels much more mature and stable compared to earlier beta releases.
Thanks to the TP-Link team for the continued work on the ER605 platform.
- Copy Link
- Report Inappropriate Content
@Vincent-TP Shows dashes. One more comment. It is not straightforward having to click EDIT in the VPN connection (in page "site-to-site vpn settings") to see the peers. they should be appearing in the same level as before.
- Copy Link
- Report Inappropriate Content
Hi @gustavoIAT
Thank you so much for your positive feedback. We appreciate it!
gustavoIAT wrote
@Vincent-TP just upgraded my ER605 v2 to this pre-release firmware in a production-like home lab environment and the experience was very positive so far.
Current setup:
ER605 v2
Dual WAN (same ISP on both WANs)
Omada Software Controller (cloud-managed)
EAP650
Load balancing enabled
Upgrade process was smooth:
no adoption loop
no configuration loss
DHCP reservations preserved correctly
AP reprovisioning completed normally
cloud reconnection was fast
One important improvement I noticed:
traffic statistics/reporting seems significantly better now.
Before this build, many wired/wireless clients frequently showed:
"Download Traffic = 0"
After upgrading, client traffic reporting appears to be working much more accurately.
Dual WAN behavior also appears stable after reboot and reprovisioning.
So far this build feels much more mature and stable compared to earlier beta releases.
Thanks to the TP-Link team for the continued work on the ER605 platform.
- Copy Link
- Report Inappropriate Content
@Vincent-TP, I was trying to update the firmware, but it is showing an error. My HW version is ER605(IN) v2.8.
- Copy Link
- Report Inappropriate Content
@Subhrajit_P hi
plesse first update to 2.3.2 see the relase note you can find old FW on official website
https://support.omadanetworks.com/en/download/firmware/er605/v2.20/
- Copy Link
- Report Inappropriate Content
@Subhrajit_P Minimum FW Version for Update: 2.3.2 Build 20251029 Rel. 12727 and above.
You are on 2.3.1.
gotta update to at least 2.3.2 build 20251029 before applying this FW.
- Copy Link
- Report Inappropriate Content
@fesarli
Im also having this issue. I noted when i updated the firmware my peer names vanished and then would not save once i tried to add them back.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 2
Views: 3911
Replies: 29
Voters 1
