Beta Software 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
I have nothing of value to add here except laughing real hard at the response you gave:
"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."
So your official position as a TP Link employee here is that you cannot port forward port 80 or 443 because the routers using them? So your suggesting your business class devices can't host websites or anything secure......... :D ....
Maybe I read that wrong? *sorry just passing by*
- Copy Link
- Report Inappropriate Content
Hi @MrHC1983
Being a bully and negative isn't helping anywhere you go. Do you read what was said next? 
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Any new updates for the lack of the mDNS settings didn't work with this new firmware ?
After all of that, I switch back to my ER605 v1 for the mDNS which working well with the 1.3.0 firmware. I have the mDNS, Port Forwarding with port 80 & 443 not working since I'm moved to the ER605 v2. The CPU of the ER605 v2 is so busy compared to the v1 (around 8-50% for the v2 and the v1 still around 5%).
The next firmware update need serious improuvments for the stability and for the mDNS, Port Forwarding and so on...
I excepted to consider my requests.
ElMajor76.
- Copy Link
- Report Inappropriate Content
Hallo,
still replying from my other post (https://community.tp-link.com/en/business/forum/topic/618938?replyId=1240254) for ER605 as. @Clive_A mentioned in this thread.
ER605 still having big problems with non functionsl mDNS in FW 2.1.1 till 2.1.4 beta.
Can´t get my IoT stuff not working. Tried all sulutions found in this thread without success.
Also disconnet problem exits in my case for ER605 with FW 2.1.1 till 2.1.4.
I've spent hours trying to get mDNS up and running, to no avail.
Hopyfully ther will be an fixed FW for this issues.
Standalone mode isn´t an opinion in my case for this network (cause in Standalone mode mDNS isn´t working, too).
Regads
yavin
- Copy Link
- Report Inappropriate Content
Hi @ElMajor76
ElMajor76 wrote
Any new updates for the lack of the mDNS settings didn't work with this new firmware ?
After all of that, I switch back to my ER605 v1 for the mDNS which working well with the 1.3.0 firmware. I have the mDNS, Port Forwarding with port 80 & 443 not working since I'm moved to the ER605 v2. The CPU of the ER605 v2 is so busy compared to the v1 (around 8-50% for the v2 and the v1 still around 5%).
The next firmware update need serious improuvments for the stability and for the mDNS, Port Forwarding and so on...
I excepted to consider my requests.
ElMajor76.
Above all the issues you reported, have you done tests yet and ruled out all possible causes?
1. mDNS, what is your mDNS type? How do you configure it? Are you certain that you copy the exact parameters from the ER605 V1 which can work?
2. Have you changed 80 and 443 which are used by the router externally(WAN) and internally(LAN) to a non-occupied port? And port forward after freeing up the 80 and 443 and test it not working?
By what methodology do you test it?
3. I am not gonna explain why CPU usage is higher than the previous one. If you can understand, then try to understand it in the CPU chipset, with more functionalities on V2.
It's not me considering your request or report. I am reporting what you said with details and reproducing steps so that the test team and reproduce it and pinpoint the cause and fix it. Like I have tried to explain this multiple times.
If I am hard getting information from you, that would be hard for the test and dev team. I can simply escalate your case but the same steps would still be done by others. Just waste some more time waiting.
- Copy Link
- Report Inappropriate Content
Hi @Clive_A and thank you for your reply !and thak you for your reply !
First of all I double checked my installation and everything is good! :) Actually, my network works with an ER605 v1 gateway due to the roll back, an TL-SG3428 switch and an EAP660HD as access point. Normally I have an ER605 v2 to replace the ER605 v1. My ER605 v1 runs with the 1.3.0 firmware and the ER605 v2 runs with 2.1.4 beta firmware.
I'm enjoying to reply all of your requests!
1. For mDNS type, I use Gateway type but I also tried AP type. For the configuration method, I proceed as follows: Creating the Bonjour Service for Chromecast devices, and creating the mDNS rule on the Gateway type with my service network as my IoT VLAN and my client network as my Main VLAN. Once Bonjour service and mDNS rule created, I restarted my Omada equipments (gateway/switch/AP) and tried if the mDNS works, but nothing works. I try the same settings but with the AP type but it's the same. With mDNS on my ER605 v1, I use the same setting I created for the ER605 v2, and after a reboot mDNS works on my ER605 v1. I tried downgrading to firmware 2.1.2 on ER605 v2 to see if mDNS works. SURPRISE! The mDNS setting works, BUT, it works abnormally. For example, I have 2 Nest Hub + 1 Lenovo Smart Clock + 1 Nest Mini + 2 Chromecast with Google TV, when I want to stream music or video, I can't see all my Chromecast devices. I can see 1 of 2 Nest Hubs or just my Chromecast with Google TV, but only 1 at a time. If I pick up my phone I can see 1 Nest Hub and my Smart Clock + 1 Chromecast, with my wife's phone I can't see any of my Chromecast devices and with my laptop I can see about 60% of my devices . All of this things are present when my ER605 v2 runs as gateway in my network. Like I said for the ER605 v1, if I put back my ER605 v1 as my gateway, I can see 100% of my Chromecast devices and stream music and videos and my printers works pretty well.
2. For port forwarding, I moved to a free port like the port 41443 and my self hosted services works only IF I'm outside of the network, but when I'm into the network nothing works like if the loopback function is not present on the ER605 v2. On the ER605 v1, the loopback function and ports 80 and 443 works normally. On my server which hosted my reverse proxy, I changed the exposed port back to the 443 and my services works. The problem is only on the ER605 v2 with beta and stable firmware. For the methodology, I launch a welcome page on my web browser starting, and this page is hosted on my local server behind a reverse proxy to have an HTTPS connection. If I put the ER605 v2 with beta firmware as gateway, the loopback function didn't work but if i took my phone and connected to the same welcome page via an LTE connection, the page loads normally.
With the ER605 v1, I haven't any problems with loopback and port forwarding. For the port part, I need the port 80 to generate my certificate via Let's Encrypt and the port 443 is to established a secure connection via HTTPS to my self hosted services.
3. For the CPU usage, IMO it's just a firmware improuvements needed. Between the ER605 v1 and the ER605 v2, I don't practice any changes in my network that increase the CPU usage. I have the same amount of data with upload every 4 hours to backup my NAS server to the cloud, I'm working remotely 4 bussiness days of 5 and so on, my usages aren't change and I'm sure I don't modify my network apart my gateway. If you need, I can paste here a graph with the CPU usage on the ER605 v1 vs the ER605 v2. But for firmware improuvments, it's an engineer role and not a customer role.
I think I give some details to reproduced those things but if you need more details, talk back to me.
Cheers, ElMajor76.
- Copy Link
- Report Inappropriate Content
Hi @ElMajor76
Thanks for posting in our business forum.
Regarding the two issues you reported, for the mDNS on Chromecast, in your reply, it seems to happen only on certain devices and its mDNS service type, I have reported it to the team. If you are willing to provide the backup of your controller, for the mDNS issue, I will be glad to send it to the test team and senior engineers for tests.
If reluctant, no worries, you can screenshot the Bonjour Service you created for your devices and will try to verify if they are correct.
About the NAT loopback/hairpin, I also got a reply from the team that we are aware of this issue and will work on it. As for the details, I am not informed any further. But it's exposed to the team and they'll work on fixing it.
- Copy Link
- Report Inappropriate Content
Hi @Clive_A !
Thanks for your reply !
If you want, I can upload to you my config directly.
How can I proceed to export my controller configuration to this forum ?
Cheers, ElMajor76.
- Copy Link
- Report Inappropriate Content
Hi @ElMajor76
Thank you so much for taking the time to post the issue on TP-Link community!
To better assist you, I've created a support ticket via your registered email address, and escalated it to our support engineer to look into the issue. The ticket ID is TKID230841904, please check your email box and ensure the support email is well received. Thanks!
Once the issue is addressed or resolved, welcome to update this topic thread with your solution to help others who may encounter the same issue as you did.
Many thanks for your great cooperation and patience!
- Copy Link
- Report Inappropriate Content
Information
Helpful: 3
Views: 32479
Replies: 134
Voters 2
