Editorial desk
WireGuardLab Editorial
The editorial desk that publishes WireGuardLab. It is a byline for the site's editorial process, not a person, and this page carries no author biography because there is no individual author to describe.
How this desk works
- Articles are researched from primary sources: vendor and project documentation, published standards and specifications, release notes, advisories, and measurements published by the people who took them.
- Drafts are produced with AI assistance and then edited against those same sources before publication.
- Nothing published here claims hands-on lab testing, benchmarking, or first-hand measurement. Where a figure comes from a datasheet or someone else's test, the article names the source.
- Corrections go to hello@wireguardlab.com and are made on the affected page. Funding is set out on the disclosure page.
Posts (4)
- comparisons
WireGuard vs Tailscale: Which One to Run
Tailscale runs on WireGuard, so the real choice is about the control plane: key distribution, NAT traversal, relays, identity, and what fails without them.
- troubleshooting
WireGuard MTU Calculator and Fragmentation Fix
Work out the right WireGuard MTU from your path MTU, understand the 60 and 80 byte overhead, measure the real ceiling, and clamp TCP MSS correctly.
- deployment-guides
WireGuard Setup on Ubuntu: Server and Client
A config-first WireGuard install on Ubuntu: key generation, wg0.conf for server and client, forwarding, firewall rules, and adding peers without downtime.
- protocol-fundamentals
WireGuard Explained: Keys, AllowedIPs, and NAT Traversal
How WireGuard really works: the static key handshake, what AllowedIPs controls, PersistentKeepalive and NAT, MTU math, and how it compares to OpenVPN.