| Family | TP-Link Archer |
| Firmware floor for WireGuard | Archer AX73 firmware 1.2.0 or later (late 2022) |
| WireGuard throughput (single tunnel) | ~250 Mbps single tunnel |
| Maximum peers per tunnel | 10 |
| CPU | Quad-core 1 GHz ARM |
| Approx Indian retail (2026) | ~₹10,000 |
| WireGuard menu path | Advanced → VPN Server → WireGuard |
Who the TP-Link Archer AX73 is for
Volume-shipping consumer Wi-Fi 6 router with WireGuard server and client. The Archer AX73 sits in TP-Link's Archer family — alongside other models that share the same firmware UI and configuration patterns but differ in CPU, throughput, and peer caps.
Setting up WireGuard on the Archer AX73
The six steps below match what the dashboard's vendor-template picker generates for the Archer AX73:
- Confirm firmware. Log in to the admin interface (typically
http://192.168.0.1) and verify the installed firmware is Archer AX73 firmware 1.2.0 or later (late 2022) or later. Update via Advanced → System → Firmware Upgrade if needed. - Open the WireGuard page. Navigate to
Advanced → VPN Server → WireGuard. - Create a tunnel. Click Add. Generate a keypair. Set Listen Port to
51820. Set Tunnel IP to 10.100.0.1/24 for a hub or 10.100.0.2/32 for a spoke. - Add a peer. Paste the remote public key. Set Allowed IPs to the remote tunnel /32 plus the remote LAN subnet. Set Endpoint Host and Endpoint Port if the remote has a stable public address. Persistent Keepalive:
21 if behind NAT. - Enable and save. Toggle Enable and Save.
- Verify. The peer row should show a recent handshake timestamp within seconds of the remote side being configured.
Archer AX73-specific gotchas
- Allowed IPs field on older firmware doesn't always accept comma-separated CIDRs — update firmware before configuring multi-LAN peers.
- 10 peers per tunnel; sufficient for a small team or 3-4-branch mesh.
- AX73 saturates ~200 Mbps WAN with WireGuard. For 500+ Mbps fibre, step up to AX90 or use Omada ER instead.
What changes at multi-branch scale
The Archer AX73 handles 1-5 sites cleanly. Past that, the configuration burden grows quadratically — five sites in a full mesh = ten peer relationships, each configured on both ends. The practical pattern past 3 sites is hub-and-spoke (every branch peers with one central router) plus a managed mesh layer that generates the per-router peer lists. MeshWG generates paste-ready configuration in the exact format the TP-Link UI accepts, including for the Archer AX73 specifically.
Frequently asked questions
Does the TP-Link Archer AX73 support WireGuard?
Yes, on firmware Archer AX73 firmware 1.2.0 or later (late 2022) or later. The Archer AX73 runs on Quad-core 1 GHz ARM and achieves ~250 Mbps single tunnel on a single WireGuard tunnel. WireGuard is configured under Advanced → VPN Server → WireGuard in the admin interface, with up to 10 peers per tunnel on current firmware.
How fast is WireGuard on the TP-Link Archer AX73?
~250 Mbps single tunnel single-tunnel on the stock firmware, measured iperf3 over a stable LAN. The Archer AX73's Quad-core 1 GHz ARM runs WireGuard without hardware acceleration, so the CPU is the binding constraint. For typical Indian SMB fibre uplinks (100-300 Mbps) the router is well above the WAN limit.
What is the firmware version with WireGuard on the TP-Link Archer AX73?
Firmware Archer AX73 firmware 1.2.0 or later (late 2022) is the minimum that includes WireGuard. Confirm by visiting Advanced → System → Firmware Upgrade in the admin interface; if your installed version is below this floor, update via the same page first. Most Archer AX73 units shipped after the firmware floor date arrive with WireGuard available out of the box.
How do I find WireGuard in the TP-Link Archer AX73 admin UI?
Advanced → VPN Server → WireGuard. If the option isn't visible, the most likely cause is firmware below Archer AX73 firmware 1.2.0 or later (late 2022) — update first, then revisit. On Deco devices specifically, the WireGuard configuration lives in the Deco mobile app, not the web admin.
How many WireGuard peers can the TP-Link Archer AX73 support?
10 peers per tunnel on current firmware. This is the cap on devices connecting into this router as a WireGuard server (or peers this router has configured outbound). For deployments larger than this cap, the practical pattern is hub-and-spoke with a higher-capacity device (Omada ER7206 or ER8411) at HQ.
Can I run WireGuard between the TP-Link Archer AX73 and a different router brand?
Yes. WireGuard is the same protocol on every implementation — your Archer AX73 interoperates with WireGuard on MikroTik, OpenWrt, OPNsense, pfSense, Ubiquiti, Asus, GL.iNet, and the official Linux/Mac/Windows/iOS/Android clients. Configuration is the same set of fields (public key, endpoint, allowed IPs); only the UI for entering them differs per vendor.
Next steps
Add your Archer AX73 to MeshWG's free tier and have the configuration generated, paste-ready into the Archer admin UI.