9
Votes

ER605 V2

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
 
9
Votes

ER605 V2

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
ER605 V2
ER605 V2
2023-06-22 11:48:11 - last edited 2023-10-19 06:08:14


I would like to report several shortcomings regarding the WireGuard VPN support on the TP-Link ER605 v2 router. Despite purchasing this equipment based on its purported strong support for WireGuard, I have encountered significant issues that hinder its functionality. It is crucial that these problems are addressed to ensure an optimal user experience.

 

1. Inability to Define an FQDN on the Endpoint:
One major drawback is the router's inability to define a Fully Qualified Domain Name (FQDN) on the WireGuard endpoint. This limitation restricts the flexibility and ease of use for those who rely on domain names rather than static IP addresses.

 

2. Limited Allowed Addresses in Standalone Mode:
When operating in standalone mode, the TP-Link ER605 v2 router only allows the definition of a single allowed address. This limitation is problematic for users who require multiple allowed addresses for their WireGuard setup. The ability to configure multiple allowed addresses should be implemented to enhance the router's compatibility and versatility.

 

3. Lack of Routing Between Allowed Addresses and Static Route Configuration:
Currently, the router does not support routing between the allowed addresses within the WireGuard configuration. This restriction undermines the potential for more complex networking scenarios that may require such functionality. Additionally, the absence of the option to define a static route through the WireGuard interface limits users' ability to customize their network setup as desired.

 

4. Absence of IPv6 Support:
Another critical issue is the lack of support for IPv6 within the WireGuard VPN implementation on the TP-Link ER605 v2 router. As IPv6 adoption continues to grow, the router's inability to handle IPv6 traffic over WireGuard connections puts users at a disadvantage and limits their ability to fully utilize this modern networking protocol.

5. Inability to Mark WireGuard VPN Traffic in the Firewall:
Currently, the router lacks the functionality to mark packets that traverse the WireGuard VPN connection within the firewall. This omission prevents users from applying granular firewall rules specifically tailored to the WireGuard traffic, potentially compromising their network security and management capabilities.

 

Given the significant issues outlined above, it is crucial for TP-Link to address the shortcomings in the WireGuard VPN support on the ER605 v2 router. Users rely on accurate product information and robust feature sets when making purchasing decisions, and the current state of WireGuard support on this router does not align with those expectations. Resolving these problems will not only enhance the router's capabilities but also provide a more satisfying user experience for those who rely on WireGuard VPN functionality.

#1
Options
1 Reply
RE:ER605 V2
2023-09-28 19:30:14
I have ER605's connecting 2 different locations. We're dependent on FQDN's to reach each site, as opposed to static IP's. Currently, the OSS Wireguard implementation supports FQDN's as well as IP's for endpoints. Would you please consider adding this to the Controller? It would save us from having to constantly monitor our IP's. Thank you!
#2
Options

Information

Helpful: 9

Views: 686

Replies: 1

Voters 8

voter's avatar
voter's avatar
voter's avatar
voter's avatar
+ 4 Voters