Beta Software ER605 V2_2.1.0 Beta Firmware Release (Jan 18th, 2023)- [Thread Closed]
Updated on Jan 30th 2023:
The official firmware 2.1.1 has just been released!
ER605 V2_2.1.1 Official Firmware (Released on Jan 30th, 2023)
Any further feedback, please feel free to Start a New Thread from HERE.
To get better assistance, you may check Tips For Efficiently Reporting an Issue In The Community.
This Article Applies to:
ER605(UN)_v2_2.1.0_Build 20230117 (Beta)
Release Notes:
-
New Feature/Enhancement
1. Add support GRE function in Standalone mode.
2. Add stateful ACL.
3. Add mDNS Repeater .
4. Add support for setting port speed and duplex mode in Controller mode.
5. Add support for setting port mirroring in Controller mode.
6. Optimized the logic of judging Me in ACL. If you need to use ACL to restrict the connection to VPN client, please select Me in Destination. Please note that if Me is included before the upgrade, the client may not be able to access the Web UI after the upgrade.
7. Add support for displaying the Source IP address of large Ping attack packets.
8. Add Non-Address mode for IPv6.
9. Optimized the DNS settings on the WAN side, the WAN side cannot set the DNS Server of the same network segment as the LAN.
10. Add IP-MAC binding in Controller mode.
11. Add One-to-One NAT in Controller mode.
12. DHCP Server's DNS support for adding network addresses.
13. Add "Certificate + Account" mode for OpenVPN.
14. Add support to customize DNS server for VPN servers in Controller mode.
15. Add "Custom IP" type for Local Networks in Controller mode.
16. Add "IP Address Range" type to VPN IP Pool in Controller mode.
17. Add support for custom Local IP Address for L2TP/PPTP VPN Users in Controller mode.
18. Add RIP and OSPF dynamic routing function in Standalone mode.
19. Add support for CLI configuration in Standalone mode.
20. Add the function of USB port storage in Standalone mode. It is used to backup the configuration and log of the device.
21. Add Reboot Schedule in Standalone mode.
22. Add DHCPv6 PD Server in Standalone mode.
23. Add support for DHCP Option field.
- Option 2: Time Offset
- Option 42: NTP Server Network Boot,
- Option 67: TFTP Server
- Option 252: WPAD URL
- DHCP Options Customization
24. Add MRU Configuration for PPPoE.
25. Add Full mode for OpenVPN.
26. Add IPsec Failover function.
27. Add SHA2-384 and SHA2-512 for IPsec.
28. Add WireGuard VPN.
29. Add import DHCP Reservation Entry and export to IP-MAC Binding Entry.
30. Add Keywords mode for URL Filtering in Controller mode.
31. Add modification to port PVID in Controller mode.
32. Add Bonjour Service, Service, and Client Network options for mDNS.
33. Add Quality of Service function.
34. Add DDNS Customization.
35. Add DNS Proxy, with DNSSEC, DoH, and DoT supported.
36. Add LDAP Authentication for PPTP/L2TP/OpenVPN and Web Authentication. Web Authentication only support in Standalone mode.
37. Add Bridge VLAN: you can bind multiple VLANs with one LAN interface.
38. Add VoIP data only goes from a certain WAN port, and that WAN port only allows VoIP to pass through.
-
Bug Fixed
1. Fix the bug that DHCP address reservation does not take effect.
2. Fix the bug that DHCP Server cannot assign an IP address.
3. Fix the bug that when an IPsec VPN tunnel is established, connections unrelated to
the tunnel are deleted.
4. Fix the bug that shield! Up port scan security risks.
5. Fix the bug that after UPNP is enabled, the Loopback function does not take effect.
6. Fix the bug that the device reported abnormal information to the controller.
7. Fix the bug that failed to connect to Server as L2TP Client for the second time.
8. Fix the bug that IKEv2 IPsec VPN, device as responder side does not clear the old SA.
9. Fix the bug that Controller adoption failure or circular adoption.
10. Fix the bug that Policy Routing would affect Port Forwarding.
11. Fix the ACL related issues.
12. Fix the bug that abnormal port forwarding after WAN up.
13. Fix the bug of loop adoption in 5.7controller or below. Mentioned Here.
Direct Download:
ER605(UN)_v2_2.1.0_Build 20230117 (Beta)
Notes:
1. For ER605 v2.0 and v2.6 only.
2. The above beta firmware is adapted to Omada Controller v5.8.
3.Please be sure you have read the Beta Test Agreement before proceeding!
The official firmware 2.1.1 has been released!
ER605 V2_2.1.1 Official Firmware (Released on Jan 30th, 2023)
Feedback:
Any further feedback on the Beta firmware, please feel free to start a new thread from HERE.
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!
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
@infinitytec They won't issue an answer. It's been asked repeatedly and complete silence. Not a good look.
- Copy Link
- Report Inappropriate Content
This beta 2.1.0 firmware is built on Jan 17th, and the newest official 2.1.1 is built on Jan 15th. A bit weird.
- Copy Link
- Report Inappropriate Content
unhappycust0mer wrote
@phongtom lol, the v1 is now two releases behind v2 and asking about it doesn't seem to get any answers. I think it's safe to say that TP-Link has decided we are not getting support anymore. Terrible practices.
Dear @unhappycust0mer
ER605 V1 does not have an update yet, but it doesn't mean there is no update anymore. We are still working on it.
From what I know, ER605 V1 will receive the update with other gateway once the next version be available.
Please bookmark this thread so you can see the update in time.
Current ER605 / ER7206 / ER8411 Firmware Releases - [Constantly Updated]
- Copy Link
- Report Inappropriate Content
Thank you for acknowledging the question. I really hope this is true because we are all still waiting for that December update which we have yet to see. With V2 now having two additional updates it really appears that V1 is receiving a smaller dev effort, which is disturbing because it is still being widely sold. Why wasn't the V2 hardware just given a different model number to make it easier to know what is being purchased? I realize you probably can't answer that but it's still just a huge frustration.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
unhappycust0mer wrote
Thank you for acknowledging the question. I really hope this is true because we are all still waiting for that December update which we have yet to see. With V2 now having two additional updates it really appears that V1 is receiving a smaller dev effort, which is disturbing because it is still being widely sold. Why wasn't the V2 hardware just given a different model number to make it easier to know what is being purchased? I realize you probably can't answer that but it's still just a huge frustration.
Agree with you, I ordered 3 time before I get v2 device.
even when I marked the order with v2 only. I also called the distributor to ask specifically for the v2 but got the v1 device anyway, finally after the third order I finally got the right one.
it's not the way it should be
- Copy Link
- Report Inappropriate Content
@shberge I'd like to agree with this completely. Why on earth - given these devices have different hardware capabilities and obviously diverging software stacks - was a different model number not chosen? TPL manage to do this with the (many) EAP variants, it's not like there's a shortage of numbers :)
And when will the V1 get any of the features long promised? I gave up counting in "October" (of which year?)
- Copy Link
- Report Inappropriate Content
Information
Helpful: 4
Views: 7559
Replies: 27
Voters 3
