October 31, 2026 · James Meadlock & Milo (Milo, on session model claude-opus-5-5 via anthropic; reasoning setting not recorded) · plan, nothing deployed yet

Leaving Tailscale for plain WireGuard: one hub, one DNS name, help only on request

Created · Updated

In plain English. Tailscale has been doing three jobs for us: building encrypted tunnels, finding each machine wherever it is, and keeping a list of names. Plain WireGuard only does the first job. So moving off Tailscale means picking a replacement for the other two.

Bottom line: it is doable with gear we already own. Run it side by side with Tailscale for two weeks before switching anything off.

RECOMMENDATION Hub and spoke on the UniFi gateway's built-in WireGuard server. Dynamic DNS for the hub only. Every remote device dials out with a 25-second keepalive. Run it next to Tailscale until each node has a proven WireGuard path. Use one WireGuard server per trust group (us, people we help, each collaborator group), each in its own firewall zone. UniFi's default lets every VPN client reach the whole LAN.
Tailnet today18 nodes8 online at check time
Hubs1UniFi Dream Machine Pro
Names that need DDNS1the hub
Always-listening helped Macs0tunnel on only on request
Hub and spoke: only the hub needs a DNS name vpn.(infra domain) DDNS → hub's current IP funland gateway (hub) WireGuard server · UDP 51820 James: phone + laptop on-demand, off home Wi-Fi funland2 site site-to-site tunnel Outside collaborators own server · one door each Help-on-request Macs tunnel off until they ask Arrows = who starts the tunnel. Helped Macs are reachable only while their owner has it on.

Figure 1. Target shape. The dashed box is the only name that has to follow a changing IP address.

What we have today

Checked from the M4 Max on October 31, 2026. The tailnet has 18 nodes and 8 were online: workstations, the GB300 Station, a NetBox/agent box, family Macs, phones and tablets. The lab machines and the family Mac Minis all sit on the home LAN with the gateway, so they need no tunnel at all; they stay reachable on the LAN exactly as today. Tailscale only mattered when James was away from home.

Both of our sites run UniFi gateways on UniFi OS 5.1.132. The main gateway holds a real public IPv4 address. We checked that the address on its WAN port is the same one the internet sees, so there is no carrier-grade NAT in front of it. That matters, because a WireGuard server behind CGNAT cannot take incoming connections at all. The address is assigned by DHCP, so it can change.

The dynamic DNS problem

A WireGuard peer can point at a hostname, but WireGuard looks that name up once and then never again (ArchWiki). DDNS only helps if two things happen. The name has to stay current. And clients have to look it up again when the address changes.

Keeping the name current

Making clients look the name up again

Remote help, only when they ask

Some of the people we look after want occasional admin help on their Macs, with their permission, and nothing more. Their Macs should not accept connections the rest of the time. Plain WireGuard fits that well, because the person being helped decides when the door exists.

Outside collaborators: one door each

Two groups of outside people need in. One group needs shell access to the GB300 Station and the DGX Sparks. The other needs the Forge server. The trap is UniFi's default. In its zone-based firewall, every WireGuard client lands in the built-in VPN zone, which is Allow All to the internal LAN, the gateway and other VPN clients. A collaborator on the default setup could reach the vault, the NAS and the Macs of people we help.

WireGuard serverWhoFirewall zoneMay reach
admin · UDP 51820 · 10.66.0.0/24James's devicesbuilt-in VPNEverything, like being home
help · UDP 51821 · 10.66.1.0/24People we help, on requestcustom "Help"Nothing (reply only), plus a lab server for anyone who also works on one; reachable on 5900/22 from admin while their tunnel is on
gpu · UDP 51822 · 10.66.2.0/24GPU collaboratorscustom "Guests-GPU"SSH (TCP 22) to the Station and the eight Sparks; nothing else
forge · UDP 51823 · 10.66.3.0/24Forge collaboratorscustom "Guests-Forge"Forge on the ports they actually need; nothing else

Retiring third-party remote-desktop apps

Once the tunnels work, nothing needs a vendor's cloud relay to reach our machines. Macs get built-in Screen Sharing over WireGuard. Linux machines get SSH. A Windows machine, if one turns up, gets RDP over WireGuard. For each machine with a third-party remote-desktop app: prove the replacement path, turn off the app's unattended access, wait two weeks, then uninstall. Unattended access through a vendor relay is an internet-facing way in, so removing it is a security gain as well as one less subscription.

What we give up

CapabilityTailscalePlain WireGuard hub
Path between two remote machinesDirect, via NAT traversalThrough the hub, both ways
Networks that block UDP (some hotels)DERP relay over HTTPSTunnel fails; keep a fallback
NamesMagicDNSGateway local DNS, pushed as the tunnel's DNS server
Who can reach whatCentral ACL policy + identityGateway firewall rules per tunnel IP
KeysRotated and expired by the serviceOurs: generate on device, vault any config that holds a private key
Extras (Taildrop, Tailscale SSH)Built inGone; plain SSH and AirDrop instead
Third-party coordination serviceRequiredNone

Middle path. If the main goal is getting off Tailscale's cloud rather than off any coordinator, Headscale self-hosts the control plane. It keeps the Tailscale clients, NAT traversal and MagicDNS. It needs a public HTTPS host. The trade is one more server to run against everything in the table above.

Hermes: docs and plugins

Our Hermes Desktop clients already connect to the dashboard by LAN address, behind password sign-in. Over a WireGuard tunnel that routes the home LAN, the URL works unchanged. The Desktop docs describe a remote gateway as something to reach over "Tailscale or another trusted VPN". They say to keep a password-protected backend off the open internet and never forward its port from the router. A WireGuard tunnel meets that bar. Hermes' SSRF guard already treats RFC 1918 and 100.64.0.0/10 as private, so a 10.x tunnel subnet gets the same protection as the tailnet did.

Catalog pluginWhat it doesFit here
wireguardRead-only wg show status and peer listWindows only. Not usable on our Macs or UniFi gateway, but it's a good pattern to copy.
netplaneInstalls and runs a Headscale control plane, with join keys and a node listOnly for the Headscale middle path. Needs a fresh Debian/Ubuntu host.
hermes-tailscaleDesktop roster of tailnet machinesRetires with Tailscale.
hermes-vpnPicks a VPN exit country for the agent's browserDifferent problem. Not needed.

No catalog plugin manages a UniFi WireGuard server. We plan to build two small, read-only pieces of our own. One is the DDNS-drift watchdog above. The other is a skill that reads handshake age per peer, so "is anyone's help tunnel up right now?" gets a real answer. Adding or removing peers stays a human decision in the UniFi UI, the same line the wireguard plugin draws.

Rollout

Tailscale stays up through every phase. Rollback at any step means using the tailnet as we do today.

#StepGate before moving on
0Infra domain on Cloudflare, scoped token, gateway DDNS, LAN updater, watchdog cronName matches the public IP; watchdog fires on a forced mismatch
1WireGuard server on the live WAN, tunnel subnet outside 192.168.x and 100.64/10Handshake from a phone on cellular
2James's phone and laptop, on-demand away from home Wi-Fi, DNS = gatewayHermes Desktop sign-in and SSH to the lab over cellular
3Second site, site-to-siteTraffic both directions
4First helped Mac: help server + zone, App Store tunnel, Get help / Done shortcutScreen Sharing works while they have it on; nothing answers when it's off; they cannot reach our LAN
4bCollaborator servers, zones and host accounts, one person firstTheir target works; every other LAN host, the gateway UI and the help zone time out from their tunnel
6Two weeks with tailscale down and remote-desktop unattended access off, then log out and uninstall bothNo path left that only Tailscale provides

Still open