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
@Hank21 Windows DHCP can, I have had routers before that could....... as shown below!
- Copy Link
- Report Inappropriate Content
Hi @MrHC1983
Thanks for posting in our business forum.
You can either turn off the log
Or disable the firewall.
If you want to find out which IP is constantly triggering this, you can use Wireshark to find it out.
- Copy Link
- Report Inappropriate Content
MrHC1983 wrote
I want the ability to add custom DNS for FIXED IP's....... Most DHCP servers are capable of this function, this would be useful to direct certain people out parental filters, the router itself or google/cloud-dns, pi holes, lan cache...... whatever it may be!
Realistically, this is never going to happen when the current DHCP implementation doesn't even allow for simple hostname resolution which has been of the feature request list for years. However, this is trivial to do with a simple custom DNS service like pihole or AdGuard.
- Copy Link
- Report Inappropriate Content
Thanks for your valuable feedback and post here. We don't have any specific date or ETA to offer. My apology.
You can subscribe to the firmware release thread which is pinned on the related page. Or pay attention to our official website where most releases will show up there very soon.
- Copy Link
- Report Inappropriate Content
@Tescophil Trivial .......... no it's not as I want to use custom DNS for different devices..... so not one fits all mould......
The entire point of a static IP is it gets the same IP details, atleast Microsoft understands this notion. It just seems Linux is lazy....... which essentially is what 99% of all these devices are run off.....
Mmmmm I could just turn off the DNS on this as it simply can't do the job....... and go back to having Windows Server handle it. Sad but may be the only solution for me.
- Copy Link
- Report Inappropriate Content
MrHC1983 wrote
@Tescophil Trivial .......... no it's not as I want to use custom DNS for different devices..... so not one fits all mould......
It is trivial, you just need to RTFM.
https://github.com/AdguardTeam/AdGuardHome/wiki/Clients
- Copy Link
- Report Inappropriate Content
@Clive_A on er605 we run both ovpn and l2tp server, PC1 in local LAN, PC2 as ovpn client and PC3 as l2tp client. With firmware 2.1.2 and older, all PCs can see each other, but from 2.1.3 PC2 and PC3 are isolated, only PC1 can see both PC2 and PC3.
- Copy Link
- Report Inappropriate Content
Hi @phongtom
The router is not intended to be used like that. If that feature is removed now or on other models in the future firmware update, then it is normal.
- Copy Link
- Report Inappropriate Content
@Clive_A I think you didn't understand the topology what I said, I don't think the er605 can not handle this to establish connection between PC2 and PC3
- Copy Link
- Report Inappropriate Content
MY FEEDBACK:
I updated on July 21st. The performance is okay, CPU usage is stable, and WAN IPv6 is giving me /64 instead of a /56 of my ISP (which it did in v2.1.2), I don't know why? It's like the WAN IPv6 in this firmware version is now behind a NAT.
But my main problem with this firmware is the router randomly freezes and then reboots. It's random that I can't really pinpoint what day/time it will freeze and reboot.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 3
Views: 32625
Replies: 134