January 13, 2026

VPN burrito or network lasagna?

Ask HN: Vxlan over WireGuard or WireGuard over Vxlan?

Tunnel-ception: WireGuard outside, VXLAN inside—or are we all overthinking this

TLDR: Debate rages over whether WireGuard (secure tunnels) should wrap VXLAN (virtual networks), with many citing docs that say VXLAN belongs in trusted zones. Skeptics ask what problem this solves and why link private networks over the public internet, while an “WireGuard for every NFS client” idea sparks memes.

The original poster kicked off a classic nerd brawl by insisting WireGuard—a secure tunnel that connects networks across untrusted spaces—should always be the outer wrapper, with VXLAN—basically a way to stretch a local network across distance—stuffed inside. They waved off Tailscale (a friendly plug‑and‑play VPN) as “cool but not always needed,” then tossed in a spicy twist: NFS (file sharing) is painful, Kerberos (the security add‑on) is worse, so why not give every NFS client its own WireGuard tunnel? Cue the comment section lighting up. pjd7 asked for receipts, wmf demanded: “What problem is being solved here?”, and DiabloD3 dropped Big Tech lore: this layered “tunnel cake” is how Google routes internally, to keep any one layer from knowing too much.

Security hawks pointed to OpenBSD’s docs, saying VXLAN is for trusted zones, so putting it inside WireGuard tracks. Pragmatists like mbreese side‑eyed the whole thing: why are we even linking private networks across the public internet? Meanwhile, the NFS plan became a meme: “wrap everything in a WireGuard burrito” with “Kerberos really sucks” sprinkled on top. The room split between defense‑in‑depth true believers and “don’t build network lasagna” minimalists. It’s spicy, it’s nerdy, and it’s somehow about tunnels arguing with tunnels.

Key Points

  • WireGuard is recommended as the outermost secure overlay for site-to-site networks.
  • If VXLAN is used, it should be encapsulated inside a WireGuard tunnel.
  • When WireGuard is not available, use alternative secure overlays like IPsec, OpenVPN, or SoftEther.
  • The recommendation focuses on WireGuard’s architectural role in crossing untrusted boundaries, not just its security properties.
  • A proposal suggests per-client WireGuard tunnels for NFS traffic to simplify security and firewall traversal.

Hottest takes

"ultimately, thats how Google routes internally." — DiabloD3
"What problem is being solved here?" — wmf
"Why are you trying to link networks across the public internet?" — mbreese
Made with <3 by @siedrix and @shesho from CDMX. Powered by Forge&Hive.