Solution Solution to ER605 V2 as WireGuard VPN “Client” Failed to Support Proxy Internet
This Article Applies to: ER605(UN)_V2_2.1.X (adapted to Omada SDN Controller 5.8)
Background:
ER605 v2 2.1.1 and later firmware has added WireGuard VPN support.
By setting 0.0.0.0/0 as Allowed Address in Peers, the ER605 v2 should be able to work as a WireGuard VPN "Client" to connect a remote WireGuard VPN service and support proxy Internet (make all the Internet traffic be routed through the VPN tunnel).
Topology Example:
WireGuard VPN "Client" Setup Example on ER605 v2:
Note: the following setup is just an example, please configure with the info obtained from your WireGuard VPN Service Provider.
Issue Description/Phenomenon:
Recently we received feedback that after setting 0.0.0.0/0 as Allowed Address in Peers, the ER605 v2 as a WireGuard VPN "Client" failed to make all the Internet traffic be routed through the VPN tunnel after the VPN tunnel is established. The phenomenon is that the end clients such as the PC cannot access the Internet.
Available Solutions:
Here is the current available solution to resolve the issue described in this thread.
Beta Firmware Download:
ER605(UN)_V2_2.1.2 Build 202303313 (Beta)
Please be sure you have read the Beta Test Agreement before proceeding!
Beta Release Note:
The above beta firmware is based on the official firmware 2.1.2_Build 20230210.
Feedback:
If this was helpful, welcome to give us Kudos by clicking the upward triangle below.
If there is anything unclear in this solution post, please feel free to comment below.
To submit a new different issue, please Start a New Thread for better assistance.
Thank you for your support and contribution in TP-Link Community!