Beta Software ER605 V2_2.1.4_Build 20230727 Beta Firmware For Trial (Released on Aug 2nd, 2023)
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
Hi everyone !
After exploring this beta firmware, I found a new bug. Port Forwarding didn't work.
I self hosted some services behind a reverse proxy on a spare PC and I need ports 80 & 443 for HTTPS to my services. Any of this port I have opened never works.
But if I use UPnP for my Xbox and PlayStation consoles, the port forwarding working ONLY for ports opened via UPnP. The port forwarding defined by user didn't work.
Also, I have found that the loopback didn't work anymore. For my self-hosted services, I have an error 404 when I want to connect to it.
For the stability and the WAF (Wife Acceptance Factor) ;) I need to go back to the 2.1.2 firmware and everything is working properly.
If you need more details, I'm glad to help you ! :)
- Copy Link
- Report Inappropriate Content
FWIW... I'm on 2.1.4 and using port forwarding successfully. I'm in stand-alone mode (no controller). I'm using Transmission->NAT->Virtual Servers for the forward and I opened the corresponding hole in Firewall->Access Control and it's working well. I'm not using 80 or 443 for my forward, so you may be running into some sort of conflict there. Just 1 data point :-)
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
@Clive_A I didn't touch anything but a few static IPs and port forwarding.
Clive_A wrote
Hi @DNA1010 @JCUK @ceejaybassist
Can I know did you enable DMZ(NAT) and Block TCP Scan with RST(Attack Defense) at the same time when you were running into the "random reboot" issue previously?
Please let me know if you enabled both when you were having trouble with the stability.
@ceejaybassist Please let me know your result when you test this beta firmware. ER605_V2_2.1.4_Build20230727 (Beta) Is the reboot issue fixed?
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Hi @DNA1010
80 and 443 are used by the router for http and https access. They have been occupied and that's why you cannot use them.
- Copy Link
- Report Inappropriate Content
Is it a New feature ? Because for me it's working with the previous firmware 2.1.2 but nothing IS working with the 2.1.4 firmware.
- Copy Link
- Report Inappropriate Content
Hi @ElMajor76
Do you move the HTTP and HTTPS to other numbers? No. It's not. The router is accessible from WAN IP with HTTP or HTTPS. If you want to use 80 and 443 for your hosted server or something, you gotta move the router web to another port.
- Copy Link
- Report Inappropriate Content
I directly move to another port and everyrhing runs great.
The only thing works abnormally is mDNS.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 3
Views: 32338
Replies: 134