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
If you run into any issues with this firmware, please export your running log and back up the config. @ me and I'll follow up on your issue.
- Copy Link
- Report Inappropriate Content
@Hank21 Hi mate, looks like the QOS->bandwidth control in the transmission section never works. I had plenty of configurations added for all classes of traffic, but everything goes into others buckets/queues. No traffic is seen with classification of class 1/2/3 even after configuring various services and assigning classes to them. Only thing that works is VOIP port 4500 which is shown in the voip classification. Is there anything that I am missing?
- Copy Link
- Report Inappropriate Content
For anyone following the thread (an no not you TP Link Support).
TP Link created a support ticket for me, I sent them what they wanted and explained the issues only for them to come back and say "our engineer rejected your case" and then they went on to gaslight me saying maybe if you had explained essentially how I got to replicating these issues (WHICH IS WHAT I DID). And for the record I never ASKED for a Support Ticket...... a forum is for feedback on your firmware! You only do that when you don't like when people arn't saying what TP Link wants! Quick get him off the forums....
Look it's pretty clear basic things which have not been fixed will not be fixed. And until TP Link perhaps sacks x engineers and stops covering for them who are not moving the firmware forward in a stable and ontime manner none of these products will improve. I would not deem the ER605 a Business Router now, it lacks alot of features that are properly built into standard home routers. VPN is not special and adding the word VPN does not make it BETTER. VPN has made its way into alot of home routers now as well.
I had an ASUS AX3000 before this, it had random kernal panics and wasn't stable......... but feature wise it walked all over this ER605. It had proper adaptive bandwidth control and QoS. So when it was running it was I would say PERFECT in terms of managing traffic.
I regret investing money into realistically stuff not fit for purpose. The Omada great idea, not excuted properly. The ER605..... yeah. The wireless stuff GREAT.... EAP610/615 etc....... no issues.
But you can't have one without the other if you want it seemless....... and the point of origin being Omada and Routers....... is the point of failure for me. Omada is great to roll out one config for all......... but only if it functions as the INTENDED IDEA which it has continously fallen short on and still has not caught up. Your team is focusing on adding all these extra things.... before fixing the basic things that need FIXING.
Gaslighting me to cover for your lazy/rude engineer is where I draw the line. Again I never asked for support.
So again in summary:
ER605/OC200 - Firmware....S!
1. Slow to boot. I timed it just under 5 minutes if you do a reboot! Takes longer if it messes up! TAKES FOREVER to get back online.
2. Adding/Editing/Removing Port Forwards (Cuts Internet within 60 seconds)...... Go sit in a online game, make a change watch it disconnect.
3. Bandwidth Control - sometimes it works, sometimes not depends on firmware....... can cause random reboots.... and again not consistent.
4. QoS. Look how it works on other devices, Windows etc. It's a minimum reserve guarantee, not something you divide up and limit into four segments. On that note also I don't think their packet flagging words...... as in EF etc.
5. Random reboots....... various firmwares. or you make a change when applied causes it to randomly reboot.
6. The Static IP lack of custom DNS......... more of a feature but again claiming to be BUSINESS. Look at Windows Server DHCP (Business).
7. Lack of information for logs when firewall detects issues (which they are working on).
8. LAG....... Really this should be my number one issue. I wouldn't even use the term latency in a sense..... I feel like the stateful packet inspection on the ER605 causes CPU TIME type lag on the device. An example is Apex Legends and online games that expose the issue when the router is doing ANYTHING else but that one thing.
Don't get me wrong the router is fast in terms of if you do a speed test etc. But yeah. We had that adopting loop and the configuring getting stuck having to wipe it and reset it up.....
On my end I also don't use the 192.168.x.x, I use a 172.16.x.x type scope which on initial setup is annoying as you have to edit the base device to change it so it can even be adopted....
So either way I am done adding my input. I am likely doing to remove the TP Link gear and go back to an ASUS and just buy a bigger model of the previous one I had. We'll see. I'm frustrated daily running under the ER605 having to adjust everything I can on the network and services just to MANAGE ITS FAILURE to manage the bandwidth.
I've gone as far as to thinking maybe I'll just up the net speed to combat it's failure to control it..... We have limits on systems and everything..... because it's just no good.
If anyone can be bothered ........ test adding/removing port forwards see if your net drops....... and report back since TP Link calls BS on that..... "Business Router"..... lol RIGHT
- Copy Link
- Report Inappropriate Content
Hi @MrHC1983
Thanks for posting in our business forum.
This "rejected" means the case was assigned back due to this case's lack of replicate methodology - how do you replicate these issues and how do you determine and monitor them and give a conclusion that it fails to perform its job?
Our senior support member will follow up on your case.
- Copy Link
- Report Inappropriate Content
Confirmed that this firmware doesn't fix the random reboot issue.
I just bought a ER605 v2 two days ago. Connected the cables then fired it up and everything worked. The firmware came with it was from last year so I just updated it to 2.1.2.
I work from home so I didn't mind paying a little more for something stable or business grade when I only need a basic router. I didn't really change any settings beside setting a few static IP and port forwarding. It random rebooted on me like 4 times in two days. It takes 5 minutes to reboot and like 10 15 min to get back online. This thing is going back to Amazon...
- Copy Link
- Report Inappropriate Content
Will there be a version of this for V1 hardware?
- Copy Link
- Report Inappropriate Content
Hi everyone !
I changed my ER605 v1 for a v2 and tha's so horrible... The mDNS function don't working anymore in the v2 but it works on v1...
I need mDNS function for my Google's smart devices. I tried the 2.1.4 beta firmware, but no mDNS service actually working. I'm going back to the 2.1.2 firmware and it's the same.
The boot time of the ER605 v2 is just insane like I see on the others posts.. The router tooks 15 minutes to get online with the official AND beta firmware, it's not normal for BUSINNES CLASS router...
I think firmware needs some serious improvments. If I can help with my logs, I'm enjoy to share with the community.
Sorry for my bad english, I'm French :D
- Copy Link
- Report Inappropriate Content
Hi @jwaltrip
Thanks for posting in our business forum.
V1 is regarded as EOL: TP-Link End of Life Products
- Copy Link
- Report Inappropriate Content
Hi @DNA1010
If you have not returned it yet, please export your files for me and I'll help you escalate it.
Make sure you reply to my message and @ me so I can be informed and follow it up timely.
- Copy Link
- Report Inappropriate Content
Hi @ElMajor76
Thanks for posting in our business forum.
Do you have any URL filter rules? Do you use Omada Controller?
How do you set up your mDNS? Are you certain that your mDNS rules are correct? Do you manually set your ER605 up again and there is an issue with it?
- Copy Link
- Report Inappropriate Content
Information
Helpful: 3
Views: 32352
Replies: 134