Early Access ER605 V2_2.1.4_Build 20230727 Beta Firmware For Trial (Released on Aug 2nd, 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 v2 / v2.6_2.1.4_20230720 (Beta) | Fully adapted to Omada SDN Controller v5.11
Update as of Aug 2, 2023:
Thank you all for your valuable feedback on the ER605 2.1.4_20230720(Beta)!
Update the Beta firmware of ER605, which now includes the issue fixed that the ER605 V2 as an OpenVPN client failed to make all the Internet traffic be routed through the VPN tunnel.
ER605_V2_2.1.4_Build20230727 (Beta)
Notes:
(1) The above firmware is applied to ER605 V2 and V2.60.
(2) Your device’s configuration won’t be lost after upgrading.
(3) The above firmware is fully adapted to Omada SDN Controller 5.11.
Hello Everyone,
This release is mainly to fix some issues based on the ER605 V2 2.2.0 official firmware. Please check the following release notes for more about the fixes.
The Purpose of the Beta Firmware
We hope to offer you with a chance to experience the new features added in the Controller v5.11 in advance, and also give us TP-Link the opportunity to fully test the firmware in your real network environment and scenarios before the official release.
Release Notes
New Feature/Enhancement
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 or unique 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. Fixed the issue that the Router might become “DISCONNECTED” in the controller after upgrading to firmware 2.2.0. Reported Here.
11. Fixed the issue that new clients might lose Internet when bandwidth control is configured.
12. Fixed the issue that OpenVPN Server no longer works after upgrading to firmware 2.2.0. Reported Here.
13. Fixed the issue that Internet/DNS resolving might not work when using OpenVPN Connect App/Software to connect to the Router’s OpenVPN Server.
14. Fixed the issue that the ER605 V2 as an OpenVPN client failed to make all the Internet traffic be routed through the VPN tunnel.
Beta Firmware Download
Please be sure you have read the Beta Test Agreement before upgrading the Beta firmware!
ER605_v2_2.1.4_Build 20230720 (Beta)
Notes:
(1) The above firmware is applied to ER605 V2 and V2.60.
(2) Your device’s configuration won’t be lost after upgrading.
(3) The above firmware is fully adapted to Omada SDN Controller 5.11.
Update as of Aug 2, 2023:
Update the Beta firmware of ER605, which now includes the issue fixed that the ER605 V2 as an OpenVPN client failed to make all the Internet traffic be routed through the VPN tunnel.
ER605_V2_2.1.4_Build20230727 (Beta)
Notes:
(1) The above firmware is applied to ER605 V2 and V2.60.
(2) Your device’s configuration won’t be lost after upgrading.
(3) The above firmware is fully adapted to Omada SDN Controller 5.11.
Feedback
Any further feedback on the new firmware, please feel free to comment below or start a new thread from HERE.
To get better assistance, you may check Tips For Efficiently Reporting an Issue In The Community.
When reporting an issue, especially it's about firmware upgrade, it's suggested to include the following info:
- Management mode (Controller or Standalone)
- Device Model(s) and Hardware
- Device Firmware (previous and current)
Thank you in advance for your great cooperation and support.
Recommended Threads
Get the Latest Firmware Releases for Omada Routers Here - Subscribe for Updates
Current Available Solutions to Omada Router Related Issues [Actively Updated, Post for Subscription]
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
In fact, I would like to know that myself.
I see TP-Link's competitor being more agile in this sense.
Look, I don't want to compromise TP-Link's analysts, who may be few and involved in many demands that end up making it impossible to release good firmware in a better time. Companies today are stuck in this model of misery of doing more with less. My intention is to draw attention to TP-Link regarding the better viability of firmwares and the evolution of Omada solutions, given that the competitor's movements are more fluid.
In this regard, managers are more concerned about investing in products that can better condition the security of their environments, even if this has a higher cost. I am a person who thinks like this. Although, I chose TP-Link because of the accessibility that its products can generate and because there is a range of comprehensive solutions. However, if problem solving in products is carried out over long periods of time, providing inadequate environment management for those responsible for IT, then it is a huge problem to maintain the decision for TP-Link and its products.
I was looking for solutions that would help me better understand networks and which solutions could provide security, but in a very user-friendly way. I remember that my thoughts were against Ubiquit because I had an interesting experience. However, its cost made things more difficult for my decision. Through a video from a man who worked with Ubiquiti, PFSense and other decentralized products, where he explained his experience with Omada and how, in addition to saving a lot, it also added enormous value, that's what made me make the decision to invest in Omada. I'm still getting to know it and really enjoying it, but I confess that the most discouraging thing has been this very slow development of firmwares with problem solving, security issues and the addition of features that further encompass these strong features that we find in Omada. But, nevertheless, and yet, we continue at a lower-than-expected pace of resolutions.
I say these words because I believe in TP-Link's potential with Omada. However, they need to make strategic changes in order to provide better agility, clearly within the time necessary for the development to mature in the application of solutions and corrections. Even if this means raising the salaries of those responsible for development today.
I really hope TP-Link listens to us.
- Copy Link
- Report Inappropriate Content
ER605(UN)_V2_2.2.2 Build 20231017 is on https://www.tp-link.com/de/support/download/er605/v2/#Firmware
Greetings ;-)
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
@SzymonN I'm having the same exact issue! If I set the /24 prefix (in my case 10.66.66.0/24) I cannot ping other devices in the VPN network - which the Omada gateway is just a client, NOT the server. And, if I change the Allowed Address to 0.0.0.0/0 now everything works as expected: The devices connected on the ER605 V2 can reach every device in the VPN network, BUT, all the gateway traffic is tunneled to the VPN, which I don't want, just the 10.66.66.0/24 traffic is supposed to go thru it. Can TP-Link help us out here?
- Copy Link
- Report Inappropriate Content
Information
Helpful: 3
Views: 29252
Replies: 134
Voters 2
