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 @pkordolian
Thanks for posting in our business forum.
pkordolian wrote
Hi @Clive_A and thank you for answering!
I guess the problem is not only the web browser (cache cookies etc) - as I have already mentioned in my post I did cleared all and also used another browser (old habit) for new version of firmware. Anyway, Beta was not for me this time. And since it is not working right from the box, let me aks what you think about below mentioned procedure ((beside old habits I'm also old fashion one) for a such firmware upgrade. Your comments and suggestions are most welcome as Beta will become soon the new version and it will be good to move forward (and secure more complicated networks)
1. Backup old version
2. Upgrade to new firmware
3. Log-in to new firmware and in case it is not possible (password issue) reset to default and start with new password
4. Change web idle settings
5. Upload backup (I hope it is still possible otherwise why should we do backup :))
6. Reboot (if not already rebooted few times)
Done
I have to mention that the main reason for me to go to new firmware was a problem with USB network. And since neither 2.1.2 nor new Beta could make it I've deployed Omada software locally (docker) and setup networks with no issue.
Once again thank you for reply!
Best regards P.
You can wait for the public release but for this issue, I did not replicate it after clearing the browser cache and rebooting the browser in my test environment. I indeed faced the wrong password after the update but as stated previously, it was because we have changed the mechanism behind the scene. But fixed after doing what I said.
The other day, I tried to replicate what you said about the wrong password even after you downgraded to 2.1.2, I imported the backup and downgraded, the password is the Chrome auto-fill and I did not clear the cache after the downgrade, and I did not face the "wrong password" you described after the downgrade.
I'll see what I can do. Will notify the dev team see if they can add a line in the release note to remind people to clear the cache after the update.
- Copy Link
- Report Inappropriate Content
Hi @DNA1010
Thanks for posting in our business forum.
In regard to your questions last week. I am testing 80 and 443 port forwarding.
#1
#2
#3
#4
- Copy Link
- Report Inappropriate Content
Hi @jg1212
Thanks for posting in our business forum.
jg1212 wrote
** EDIT **
Nevermind, it appears to be working suddenly. I'll post back if anything changes.
NAT Loopback (Hairpinning) is no longer working for me with ER605 V2_2.1.4_Build 20230727 Beta Firmware. (using Omada Controller 5.12.6)
From inside my LAN, I can not access any of my NAT port forwarded servers using my External IP address. The only thing I can access is my router's login page at EXT-IP:80.
Can you verify on your end? Let me know if you need anything from me to help fix this.
Thanks,
JG
Well it looks like working perfectly.
- Copy Link
- Report Inappropriate Content
Thanks for posting in our business forum.
Artur.Aragao wrote
Great week for everyone!
I'm using the Beta firmware and noticed something really annoying here.
I blocked a MAC that I wasn't recognizing yesterday. Today I noticed that my wife was trying to access her computer and she couldn't. The problem was the block I performed.
I undo the blocking and she manages to authenticate on the network, but does not get internet like the others. What is that?
As I'm in a bit of a hurry to fix this, also due to the urgency that she needs to use the PC, I'm returning to the release version. This did not happen in the previous version.
The tricky part is that it establishes the connection now but fails to assign an IP. VERY crazy that, friends.
First, this is not a beta issue. It gets 169.254 IP addresses because of your block.
Second, Microsoft and Windows are advertising their so-called privacy and masking your real MAC address when joining any new network. So, you probably should double-check the MAC address on all of your Android, Apple, and Microsoft Windows OS devices for this.
Rejoin your WIFI should fix this quickly. Either reboot EAP or your wife's computer will also fix it. Lease time is not over, so you will not get a new IP address unless you reconnect the WIFI.
- Copy Link
- Report Inappropriate Content
Oops!
Show! So I can continue on beta firmware. What a fright.
I don't have the same experience as my friends. I'm developing this with Omada products.
I even accept indications to better learn the resources of the equipment, because I see that there are many advanced resources and I really want to achieve better knowledge and use these resources well.
Returning to the topic, I had already restarted the EAP670 and it had not worked. It was returning to the firmware release that took almost nothing for the equipment to carry out the release.
I'm going to reapply the beta firmware and test this again, because with it I felt that there was an improvement in the processing of resources for the 2.4 GHz antennas.
Thank you very much for your usual kindness.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
@Hank21 Any update for this? It's been a month since the last beta release.
- Copy Link
- Report Inappropriate Content
Aqui tentei atualizar pra resolver o problema de que a WAN secundaria no failover fica toda hora como principal, independente da configuração, esse problema ainda não resolveu
ER605 V2.0 em 3 locais diferentes
- Copy Link
- Report Inappropriate Content
Hi @informc
informc wrote
Aqui tentei atualizar pra resolver o problema de que a WAN secundaria no failover fica toda hora como principal, independente da configuração, esse problema ainda não resolveu
ER605 V2.0 em 3 locais diferentes
Thanks for posting in our business forum.
I translated your description. I gotta confirm with you. Do you run into issues with the failover and cannot switch back to the primary after the primary WAN is up again?
What kind of mode do you use? Standalone or Controller? Controller mode, you can use that if you enable the option to switch back. Yet, in standalone, I think you can do this as well.
Refer to the test I did earlier and if you'd like to provide more details with screenshots and traceroute, start a new thread then. I'll follow it up.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Information
Helpful: 3
Views: 32264
Replies: 134