Quick answer

Choose raw kernel WireGuard when at least one endpoint has a public IPv4 or IPv6 UDP port forward and you want maximum multi-gigabit efficiency with zero coordination server dependency. Choose Tailscale when endpoints sit behind CGNAT, cellular, or hotel NAT, pairing userspace WireGuard with STUN hole-punching, encrypted DERP TCP relays, subnet routers, and MagicDNS.

Contents

At a glance

Class
Comparison

Provenance

  • Jul 1, 2026Published
  • Nov 14, 2026Last substantive update

Most “Tailscale vs WireGuard” articles treat them like rival encryption protocols and wave away performance as identical. Both claims miss the mark.

Tailscale uses the WireGuard protocol for its encrypted data plane (Tailscale’s technical comparison). What differs is how packets cross hostile NATs and whether WireGuard runs inside your OS kernel with static peer endpoints or inside tailscaled userspace with STUN hole-punching and TCP relays. Topology decides the winner. In my own homelab, I map the WAN path between client and server first. For hands-on setup commands, see our guides to Tailscale remote access and self-hosted WireGuard on Proxmox.

Topology & NAT-traversal decision table

Before comparing setup screens, find your network path in the left column. Network topology dictates whether raw WireGuard can connect at all, and whether Tailscale runs at direct UDP speed or drops down to a TCP relay:

Network topology between client & homelabRaw Kernel WireGuard (wireguard.ko)Tailscale (tailscaled + Control Plane)Recommended pick
Home has public IPv4 (static or DDNS) + 51820/udp forwarded (client on LTE or home Wi-Fi)Direct UDP. Lowest CPU overhead, 1420 MTU, instant roaming handoff, zero third-party server.Direct UDP after coordination check-in (1280 MTU userspace wireguard-go).Raw WireGuard for 1–5 devices & total independence; Tailscale for 10+ devices or family sharing.
Home behind IPv4 CGNAT, client has reachable IPv6Direct UDP over IPv6 if every client network (including cellular/coffee-shop Wi-Fi) provides working IPv6. Fails immediately on IPv4-only guest Wi-Fi!Direct UDP over IPv6 or hole-punched IPv4 automatically.Tailscale (unless you control both networks and guarantee dual-stack IPv6 everywhere).
Home behind IPv4 CGNAT (Starlink, 5G Home, apartment fiber) + client on standard cone NATCannot connect without renting a public VPS and building a hub-and-spoke WireGuard bounce tunnel yourself.Direct P2P UDP via STUN + coordinated UDP hole-punching across NAT state tables (zero open router ports).Tailscale wins decisively.
Both sides behind strict symmetric NAT, or hotel / corporate firewall blocking all UDPCompletely blocked (UDP 51820 dropped; WireGuard intentionally has no TCP transport mode).Automatic fallback to DERP TCP-443 relay. Connects reliably over TLS 443, with added relay hop latency and lower throughput.Tailscale (only option that connects without external TCP-tunnel wrappers).
Site-to-site LAN bridge between two routers with public IPsLine-rate kernel tunnel directly on OPNsense / Linux routers; survives SaaS outages indefinitely.Works via subnet routers (--advertise-routes), adds userspace daemon and account dependency.Raw WireGuard on the routers.

Kernel WireGuard vs tailscaled userspace + DERP: why speeds diverge

Saying “Tailscale is WireGuard so speed is identical” hides three real transport differences you can measure on your own hardware:

  1. In-kernel wireguard.ko vs userspace wireguard-go: Since Linux 5.6, native WireGuard lives inside the kernel networking stack. Packets move from NIC ring buffers through ChaCha20-Poly1305 encryption with zero userspace context switches and a standard 1420 byte MTU. Tailscale runs tailscaled in userspace (1280 byte MTU) so it can handle per-packet ACLs, MagicDNS (100.100.100.100), and dynamic path switching. On modern Linux kernels (6.2+), Tailscale leverages UDP Generic Segmentation Offload (GSO) and Generic Receive Offload (GRO) to push multi-gigabit direct speeds, though raw kernel WireGuard still uses measurably less CPU and mobile battery per gigabyte moved.
  2. Direct UDP vs DERP TCP-443 relays: When a hotel firewall blocks UDP or both sides sit behind port-randomizing symmetric NATs (for example certain cellular carriers talking to certain enterprise firewalls), Tailscale wraps encrypted WireGuard packets inside HTTPS-like streams over TCP port 443 through regional DERP relay servers. DERP saves the day for SSH, Home Assistant, and web dashboards when raw WireGuard is dead in the water, yet TCP-over-tunnel congestion + an out-of-state relay hop cuts SMB file-copy and 4K Jellyfin streaming throughput sharply compared with a direct link.
  3. Verify your active path in two seconds: Never guess why a Tailscale transfer feels slow. Run two built-in commands from your terminal:
# Check every peer's active transport ('direct <ip>:<port>' vs 'relay "ord"')
tailscale status

# Watch real-time UDP hole-punch upgrade from DERP to direct P2P latency
tailscale ping homelab-nas

If tailscale ping stays stuck on via DERP(...) across ten packets when you control the home router, enabling UPnP / NAT-PMP on your gateway or opening UDP port 41641 to your primary subnet router lets Tailscale upgrade stubborn symmetric-NAT peers back to direct WireGuard speed.

Subnet routers, MagicDNS, and exit nodes vs manual wg0.conf

Raw WireGuard deliberately stops at Layer 3 point-to-point packet crypto. Adding a new phone means running wg genkey | tee privkey | wg pubkey, assigning the next /32 IP by hand, appending a [Peer] block on the server, and scanning a QR code on the client. To reach twenty LAN devices that cannot install VPN software (IPMI BMC ports, network printers, NAS shares, Apple TV), you enable net.ipv4.ip_forward=1 and maintain PostUp / PostDown nftables or iptables NAT/forwarding rules yourself.

Tailscale turns those exact chores into single commands:

  • Subnet Routers (tailscale up --advertise-routes=192.168.1.0/24): One tiny Linux VM or Proxmox LXC bridges your entire home subnet onto your tailnet without installing Tailscale on every appliance.
  • MagicDNS (100.100.100.100): Automatically resolves stable 100.x.y.z tailnet names (proxmox.tail-scale.ts.net) identically on home Wi-Fi, LTE, or airport Wi-Fi, and integrates split-DNS forwarding to internal Pi-hole or AdGuard Home servers.
  • Declarative ACLs & Tailscale SSH: Replace per-host iptables chains and static SSH key distribution with one audited JSON/HuJSON policy file.

For public Wi-Fi protection when traveling, check whether routing through your own home fiber makes more sense than paying a third party. Tailscale’s exit-node feature and WireGuard’s 0.0.0.0/0 full-tunnel peer config both send DNS and web traffic through your chosen server. Configure full-tunnel routing deliberately when you want it rather than leaving it on permanently. The encrypted tunnel protects packets only as far as that exit, whose operator and internet provider remain part of the trust decision; websites beyond that exit simply see your home or VPS public IP.

Trust boundary, control-plane independence, and Headscale

Encryption strength does not separate them because both run WireGuard cryptography end to end. What separates them is control-plane sovereignty.

With self-hosted WireGuard, zero external infrastructure participates. No SaaS outage, OAuth identity-provider lock, or coordination-server policy change can ever touch your tunnel. Your public keys, peer IP mappings, and connection timestamps exist strictly inside /etc/wireguard/wg0.conf on machines you own.

With standard Tailscale, your payload traffic remains end-to-end encrypted between your devices, while Tailscale Inc.’s proprietary coordination plane distributes public keys, pushes ACL rules, and logs which devices belong to your tailnet. Existing direct tunnels usually stay up through brief control-plane hiccups, yet onboarding a new machine or rotating expired node keys requires reaching controlplane.tailscale.com.

If you want Tailscale’s NAT traversal, MagicDNS, and polished iOS/Android clients without relying on Tailscale’s cloud control plane, self-host Headscale (or compare NetBird and ZeroTier) on a small VPS you control.

Practical homelab verdict: pick one or layer both

  • Deploy raw kernel WireGuard when your home router has a public IPv4 address (static or DDNS) where you can forward one UDP port, you manage a handful of personal devices, and you want peak multi-gigabit kernel efficiency with zero external account dependencies.
  • Deploy Tailscale when your ISP puts you behind CGNAT (Starlink, T-Mobile/Verizon 5G Home, apartment fiber), you roam across UDP-hostile hotel or campus networks where DERP TCP-443 fallback keeps you connected, or you share specific services (Jellyfin, Immich) with family members without opening router ports.
  • Run the hybrid homelab setup I recommend most: Terminate raw kernel WireGuard on your OPNsense or router firewall as your primary zero-dependency tunnel, and keep one lightweight Tailscale subnet-router container running inside your lab as a zero-port backup door. When a hotel network blocks UDP 51820 or your residential WAN IP changes mid-trip, your backup door still opens in one click.

Frequently asked questions

Is Tailscale based on WireGuard?
Yes. Tailscale encrypts every data packet with the WireGuard protocol (Noise_IK handshake and ChaCha20-Poly1305 encryption) via its userspace tailscaled daemon. On top of WireGuard, Tailscale adds automatic public-key distribution, STUN/UDP NAT traversal, encrypted DERP TCP-443 fallback relays, stable 100.x.y.z addresses, MagicDNS, and centralized access policies.
Why is kernel WireGuard faster than Tailscale on multi-gigabit links?
On Linux, raw WireGuard runs inside kernel space (wireguard.ko) with zero context switches between kernel NIC buffers and userspace, typically using a 1420-byte MTU. Tailscale runs wireguard-go in userspace (1280-byte default MTU) so it can intercept packets for NAT hole-punching, MagicDNS, and ACLs. Recent tailscaled builds narrow the gap substantially on Linux using UDP GSO/GRO offload, while DERP TCP relays remain much slower than direct UDP.
Which works behind CGNAT: Tailscale or raw WireGuard?
Tailscale works automatically behind Carrier-Grade NAT (Starlink, 5G home internet, apartment fiber) with zero inbound ports opened. It uses STUN and coordinated UDP hole-punching to establish direct peer-to-peer links across cone NATs, and falls back to encrypted DERP relays over TCP port 443 when both sides sit behind strict symmetric NATs. Raw WireGuard behind CGNAT requires either end-to-end IPv6 or renting an external VPS with a public IPv4 address as a hub.
Can Tailscale read my traffic when it falls back to a DERP relay?
No. DERP (Designated Encrypted Relay for Packets) forwards already-encrypted WireGuard packets keyed strictly between your endpoint private keys. However, Tailscale’s coordination plane sees device metadata, public keys, IP endpoints, and connection graph state unless you self-host the coordination server with Headscale.
How do I check whether Tailscale is direct or relayed through DERP?
Run tailscale status or tailscale ping from either machine. Output showing direct : confirms a peer-to-peer UDP WireGuard tunnel; output showing via DERP(ord) or another three-letter airport code means UDP hole-punching was blocked and packets are traversing a TCP relay.
Can I run both WireGuard and Tailscale in the same homelab?
Yes, and many homelabs do. Terminate raw kernel WireGuard on your OPNsense or Linux router for zero-dependency daily access when UDP 51820 works, and keep Tailscale running as a subnet router in a lightweight VM or LXC as an instant fallback from UDP-blocked hotels, airports, or CGNAT links.

Corrections

Last updated
Methodology
See our methodology for research and review standards.
Corrections
Spotted an error? Email a correction with the affected line and what you found. The draft includes this page’s address. Verified changes are recorded here. Contact details.

About the author

Written by Lowell K. Wood IV, who builds and runs TechFuelHQ from St. Louis, Missouri.