TP-Link WireGuard Setup Guide
Select TP-Link models support WireGuard in stock firmware (Archer AX55 V1/V2, AX20/AX21 V3, AX53, Deco X/BE series). The firmware handles NAT automatically — PostUp lines are stripped and should be removed before importing.
Check your router is supported
WireGuard is available in stock firmware on: Archer AX55, AX20, AX21 V3, AX53, AX3000, and Deco X/BE series (varies by region and firmware version).
Update to the latest firmware at tp-link.com/support/download.
Create a tunnel in ProxyLink
Go to Devices → + Add → Router / LAN site, select Router / Gateway, enter your LAN subnet, and download your .conf file. On the gateway page, switch the download picker to 🌐 Router (MikroTik / pfSense / OpenWRT) before clicking Activate, otherwise you get a RouterOS .rsc script instead of a .conf file.
Edit the config before importing
TP-Link stock firmware strips unsupported fields. Open the .conf in a text editor and remove these lines:
# Remove these lines: PostUp = ... PostDown = ... DNS = ...
Only keep: PrivateKey, Address, PublicKey, AllowedIPs, Endpoint, PersistentKeepalive.
Import in TP-Link admin panel
Open your router admin panel → Advanced → VPN → VPN Client.
Enable VPN Client, click Add, select WireGuard, and import your edited .conf file.
Enable and test
Toggle the VPN client ON. TP-Link handles NAT automatically — no manual iptables rules needed. Your LAN devices are now reachable via ProxyLink proxy links.
Good to know
Reaching more than one VLAN
One LAN needs nothing beyond this guide. If the site has several VLANs (a camera VLAN, a PBX VLAN, a guest network), there is one more thing to know.
ProxyLink gives every gateway its own private address range and translates between that
range and your real LAN addresses. That is what lets two different clients both use
192.168.1.0/24
without colliding. The translation rules live in the
PostUp and
PostDown
lines of the config we generate.
TP-Link cannot run those rules for itself, so extra VLANs are routed directly instead of being translated. Two consequences worth knowing:
- Add the VLAN under your gateway → VLAN subnets as normal, then add the equivalent forwarding rules for that VLAN on the device yourself.
- Because the range is not translated, ProxyLink checks it does not collide with another customer's. A very common range that is already in use elsewhere may be refused.
If a site has several VLANs and you would rather not maintain that by hand, put a small Linux box (a Raspberry Pi is plenty) or a MikroTik beside the router and use it as the gateway. Both are managed, so every VLAN is handled automatically and the existing router is left alone. See the Linux and MikroTik guides.
What you get once the tunnel is up
- Browser RDP, VNC, and SSH — open a terminal or remote desktop to any device behind the tunnel straight from the ProxyLink dashboard. No client software, no open ports on your side.
- Proxy links — share an HTTPS URL that forwards to any internal web interface (NAS, NVR cameras, PBX admin panels, router UIs) with ProxyLink login in front of it.
- No public exposure — the device keeps zero open ports and needs no static IP. The tunnel is outbound-only WireGuard to EU-hosted infrastructure. Read more about agentless remote access and NIS2 compliance.
Ready to connect?
Create a free account and set up your first tunnel in minutes. Free during early access — no card required.