Beta Software ER605 V2_2.1.5 Build 20231024 Beta Firmware for Omada Controller V5.11 (Released on Oct 26th, 2023)
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
This Article Applies to
ER605(UN) V2 2.1.5_Build 20231024 (Beta)
Release Notes:
New Features & Enhancements:
1. Add ACL support for IPv6 data.
2. Add support for IPv6 RA (Router Advertisement) configuration for LAN.
3. Add support for configuring multiple IP addresses on the WAN port.
4. Add support for monitoring session limits in controller mode.
5. Add support for configuring the MSS (Maximum Segment Size) of WAN port.
6. Add support for Gateway Tools in Controller mode.
- Ping.
- Traceroute.
- Terminal.
7. Add support for the ability to download device info of Gateway in Controller mode.
8. Add support for Location Group in Gateway ACL.
9. Add support for white list of MAC filtering in Controller mode.
10. Add support for tagging same VLAN ID on different WAN port.
11. Increased security of communication between Gateway and Controller.
12. Add support for DNS cache, which can improve domain name resolution speed by handling recent address resolutions locally before sending request to Internet .
13. Add support for DH 14 and DH 15 for PFS.
14. Add support for 0.0.0.0/0 IP range of local network when using IPsec IKEv2 for Client-to Site VPN.
15. Add support for DDNS custom intervals (1~60 minutes).
16. Add support for link-local addresses of IPv6 DNS on the LAN side.
17. Log Enhancements.
- Show the source IP address of TCP no-Flag /ping of death attacks.
- Show the log of link backup switching.
- Show the log of DDNS update.
- Logs can be saved when the device is down. You need to short-press the reset button within 5s, and after releasing the reset button, the sys light will be on for 3 seconds to indicate that the downtime log is saved successfully.
Bug Fixed:
1. Fix the bug that ICMP type 13 packets cannot be intercepted.
2. Fix the bug that VPN Client cannot access the other side through IPsec when the device act as a PPTP/L2TP/OpenVPN Server and also establishes IPsec VPN with other devices.
3. Fix the bug that VPN client cannot proxy Internet access when VPN IP Pool and LAN IP are in the same network segment.
4. Fix the bug of CPU abnormality caused by enabling more VLAN Interface.
5. Fix the bug of high latency in ISP Load in Controller mode.
6. Fix the bug of frequent reconnection with Omada Controller.
7. Fix the bug that the VLAN configuration of IPTV is affected by the VLAN configuration of WAN port in Controller mode.
8. Fix the bug that the device does not support proxy internet access as Wireguard VPN client.
9. Fix the bug that Port Forwarding does not take effect under multiple WAN ports.
10. Fix the bug that new clients might lose Internet when bandwidth control is configured.
11. Fix the bug that Internet/DNS resolving might not work when using OpenVPN Connect App/Software to connect to the Router’s OpenVPN Server.
12. Fix the bug that the device as an OpenVPN client failed to make all the Internet traffic be routed through the VPN tunnel.
13. Fix the bug that remote IP error displayed in the OpenVPN Tunnel interface when the device connects successfully as an OpenVPN Client.
14. Fix the bug that after the device connects to the Server as a WireGuard VPN Client, the peer cannot access the device via WireGuard Interface IP.
15. Fix the bug of command injection vulnerability in the login page.
16. Fix the bug that the device may not start.
17. Fix the bug that when DOH/DOT used with DNS cache, modifying the TTL value of DNS cache will cause the client to be unable to access the Internet.
18. Fix the bug that port forwarding probabilistically did not work.
19. Fix the bug that when the device is used as an OpenVPN client, the VPN tunnel cannot be reconnected automatically when it times out.
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
ER605(UN) V2_2.1.5_Build 20231024 (Beta)
Notes:
(1) The above firmware is applied to ER605 V2/2.6.
(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 ER605 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 ER605 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
Nov. 20th, 2023:
Update the format and incorrect description in the release note.
Oct. 26th, 2023:
Post the ER605 V2 2.1.5_Build 20231024 (Beta) firmware for early access.
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
Are the Ipv6 LAN prefixes other than 0 supported in this release? I see this not working in 2.2.2
Lets say,
WAN:
If I enable IPV6 in WAN and select Dynamic IP (SLAAC + DHCPV6) via DHCPV6 -> Enable Prefix Delegation -> Size of 64
LAN:
In LAN -> WLAN -> Enable V6 -> IPV6 Prefix ID = 0 ---> All works well. Tested by --> tracert -6 google.com ---> I get the expected result. Also the ipv6 test website says i got V6 assigned and same with google V6 test website. All good.
But,
WAN:
If i select Prefix Delegation -> Size of 59
LAN:
IPV6 Prefix ID = 5 (within in the range of 1-31) -> I see IPV6 prefix is assigned -> However IPv6 routes to WAN are broken. Meaning ---> tracert -6 google.com completely fails. Here the IPV6 test, google V6 test website fails
Why is this?
- Copy Link
- Report Inappropriate Content
Hi @vnan1829
Thanks for posting in our business forum.
vnan1829 wrote
Are the Ipv6 LAN prefixes other than 0 supported in this release? I see this not working in 2.2.2
Lets say,
WAN:
If I enable IPV6 in WAN and select Dynamic IP (SLAAC + DHCPV6) via DHCPV6 -> Enable Prefix Delegation -> Size of 64
LAN:
In LAN -> WLAN -> Enable V6 -> IPV6 Prefix ID = 0 ---> All works well. Tested by --> tracert -6 google.com ---> I get the expected result. Also the ipv6 test website says i got V6 assigned and same with google V6 test website. All good.
But,
WAN:
If i select Prefix Delegation -> Size of 59
LAN:
IPV6 Prefix ID = 5 (within in the range of 1-31) -> I see IPV6 prefix is assigned -> However IPv6 routes to WAN are broken. Meaning ---> tracert -6 google.com completely fails. Here the IPV6 test, google V6 test website fails
Why is this?
Give me the screenshots of your config for the second setup. WAN, LAN, and tracert result. Partially mosaic your sensitive information.
Is your ISP allowing you to use PD 59? Is PD 64 your ISP told you?
- Copy Link
- Report Inappropriate Content
Thank you for the response. I have figured this out by discussing with my ISP. They support only 56, 64 Prefix Size. So after reconfiguring it, now it works. So, this is no longer an issue.
- Copy Link
- Report Inappropriate Content
why is this release called ER605 V2_2.1.5 Build 20231024 Beta Firmware, released on 10.24
and the official release ER605 V2_2.2.2 Build 20231017 Official Firmware (Released on Oct 18th, 2023), before the beta above.
If a beta is released after an official release, should it not be that same version or higher? i.e. V2_2.1.5 BETA should be called V2_2.2.3 BETA instead?
If find TP Link's naming convention hugely confusing as to features and bugs as they relate to official releases.
To me it looks more like this firmware is forked into 2 paths (is this normal), rather than take a logical "release", then "beta", then the next release will have the bugs o the beta resolved, etc, etc.
There was a comment you made in another post "don't use the official 2.2.2 release, instead beta 2.1.4"...
Thanks,
- Copy Link
- Report Inappropriate Content
Hello,
Anyone has any idea if ER605 V2 will have DPI as in the latest Omada Controller Release 5.13.22? As of now, when I go to the DPI section I get the message: Gateway does not support DPI.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
What do you mean by that? If you mean the controller? Well, the controller is in a Docker Container (mbentley), I do not have a HW Controller like the OC200 or OC300.
- Copy Link
- Report Inappropriate Content
Hi @Adandu
Thanks for posting in our business forum.
Adandu wrote
What do you mean by that? If you mean the controller? Well, the controller is in a Docker Container (mbentley), I do not have a HW Controller like the OC200 or OC300.
He means that the hardware capacity of the ER605 might not support DPI. So the very first model is ER7206, added with DPI. Then other flagship models. I am not sure that DPI will be implemented in the ER605. If the hardware allows this, it should stay consistent like the other models to have the DPI.
Please wait for the future firmware update.
- Copy Link
- Report Inappropriate Content
Hi @words
Thanks for posting in our business forum.
words wrote
why is this release called ER605 V2_2.1.5 Build 20231024 Beta Firmware, released on 10.24
and the official release ER605 V2_2.2.2 Build 20231017 Official Firmware (Released on Oct 18th, 2023), before the beta above.
If a beta is released after an official release, should it not be that same version or higher? i.e. V2_2.1.5 BETA should be called V2_2.2.3 BETA instead?
If find TP Link's naming convention hugely confusing as to features and bugs as they relate to official releases.
To me it looks more like this firmware is forked into 2 paths (is this normal), rather than take a logical "release", then "beta", then the next release will have the bugs o the beta resolved, etc, etc.
There was a comment you made in another post "don't use the official 2.2.2 release, instead beta 2.1.4"...
Thanks,
2.1.4 is the one on track. 2.2.2 is a specially made one for security reasons. That's why I made the comment.
So, I don't think you should be worried about the version thing. It does not affect anything. Both firmware can be considered okay to use. But if you wanna stay on the track, use the 2.1.5.
- Copy Link
- Report Inappropriate Content
This Beta version is working well on both IP4 and IP6
However, the test site https://ipv6-test.com/ tells me that ICMPv6 packets are being filtered by the firewall on my ER605. I have created no additional ACL rules for IPv6 so this must be the default rule.
As you may know, ICMPv6 is described as an important part of of IPv6 and this RFC suggests ICMPv6 packets should be allowed through
https://datatracker.ietf.org/doc/html/rfc4890
I have tried to create a specific IPv6 ACL rule to allow IPv6 ICMP to work as required but can't see how.
Please advise on TP-Link's advice as to what ICMPv6 rules should be created and how this can be achieved in this Beta version
Alternatively, assuming your developers are well aware of the relevant RFCs, should the default IPv6 Defaults coded into the Firmware be amended?
Thanks
mhoam
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 13433
Replies: 59
Voters 0
No one has voted for it yet.