Early Access ER605 V2 2.3.0 Build 20250410 Pre-Release Firmware (Released on Apr 25th, 2025)
Early Access ER605 V2 2.3.0 Build 20250410 Pre-Release Firmware (Released on Apr 25th, 2025)
This Article Applies to
ER605 V2.X
Release Notes
Version Info:
Firmware for ER605(UN) 2.0 and 2.6. This firmware is fully adapted to Omada Controller V5.15.20.X.
Minimum FW Version for Update: 2.2.3 Build 20231201 Rel.32918 and above.
New Features:
1. SD-WAN
2. Domain name supported for OpenVPN and Wireguard VPN
3. Virtual WAN
4. Disable NAT
5. Google LDAP
6. LAN DNS
7. FQDN/Wildcards WAN DHCP Option
Enhancements:
1. Optimized CPU utilization.
2. Optimized the time to enable the backup link.
3. Optimized booting time.
4. Optimized the time to dial up the WAN link.
5. Optimized the time to upgrade FW.
6. Optimized the time to generate the OpenVPN profile.
Bug Fixed:
1. Fixed the HTTPS redirection exception in standalone mode.
2. Fixed the issue where the static route for L2TP VPN doesn’t take effect after re-enabling L2TP VPN.
3. Fixed the WOL exception when dropping some unknown unicast packets.
4. Fixed the issue where the PPTP VPN would occasionally disconnect.
5. Fixed the issue where the manual ISP profile for USB modem cannot be saved.
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.
(4) Content Filter is not available for certain models due to storage.
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 25th, 2025:
Release of this post.
Recommended Threads
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!
Current Available Solutions to Omada Router Related Issues [Actively Updated, Post for Subscription]
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
7206 v1 and 605v2 are quite comparable in terms of throughput, concurrent sessions etc for home use.
- Copy Link
- Report Inappropriate Content
This firmware doesnt have the new categorised version of URL filtering, its still just the old style manual list one. Is that planned for the 605 v2 at all ?
- Copy Link
- Report Inappropriate Content
@KimcheeGUN is there any difference between tl-er7206 and er7206 v1
- Copy Link
- Report Inappropriate Content
tl-er7206 is the earlier earlier version
er7206 v1 is the model the came out after the one above.
The the V2 hit the market recently.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
or possibly the storage space, i would imagine the list under-the-hood is enormous
Yeah, i noticed the lack of IPS too (which is there in standalone though, isnt it?) - but it still does have full DPI which is pretty CPU intensive, so im not sure if this is intentional or this is just a very early version.
- but -
It is still very much the baby router in the family, its reasonable they cant add everything to it
edit:
Its also possible that we need firther controller adaptations, this firmware build is later than the most recent official controller builds, guess we will find out eventually
- Copy Link
- Report Inappropriate Content
@Clive_A Very grateful for the new release including LAN DNS. I've been able to add A records (IP option) and CNAME records for devices with a fixed IP address.
Is there any way to automatically map the client name of devices (as seen in the Clients section) to DNS names? That way I can use the names of devices that have a dynamic IP address assigned by DHCP.
Thank you!
- Copy Link
- Report Inappropriate Content
I've been using a Docker image that's basically a DNS server pulling from the Omada controller's client list just as you're talking about. I then have my Piholes setup for conditional forwarding to it so that I get actual friendly names (as I've set in Omada) showing in the stats for Pihole.
https://github.com/dougbw/coredns_omada
I really wish this was just baked in to the Omada system and was hoping where I heard they were finally adding DNS that this would be the case. It sounds like that's not the case from what you're saying:(
- Copy Link
- Report Inappropriate Content
I'm not sure if there's something I'm missing and that's why it doesn't propagate names from DHCP to DNS, or this is just something that hasn't been implemented.
I tried using that docker image, but for some reason, even if I can see it connects to Omada, when I test it with nslookup or dig, it won't resolve the names. I think it returns something like NXDOMAIN or similar. Very frustrating.
I'm hoping at some point I'll be able to get Omada's DNS to resolve DHCP names, seems like such a basic function.
Thank you
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Information
Helpful: 1
Views: 427
Replies: 20
Voters 1
