You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Once private access runs on wg-access (#346) and callers are identified by their device (#345), Tailscale is only a second network and a second identity system to maintain, document and test.
Proposed solution
Remove Tailscale entirely, rather than keeping it as an option.
Daemon: the tailnet node and its piqueld-tailscale container, the tailnet listen modes and shared tailscaled, tailnet-bound tokens, the whois lookups, and the tailnet range check on private routes.
DNS: route DNS records point at the gateway's wg-access address instead of tailnet addresses.
Configuration: the removed keys fail validation with a message pointing to [access].
NixOS module: the tailnet options are removed.
Docs: installation, configuration, ingress, observability and backups (tailnet state).
This is a breaking change for any installation that uses the tailnet. It needs a release note.
🤖 Claude Opus 5.5 responding on behalf of PiquelChips
Closing as not planned: Tailscale integration stays. The access plan now runs the tailnet on a self-hosted Headscale control server (sourceorigin-dev/infra#9) instead of replacing it with a piqueld-managed WireGuard network. piqueld's part of that change is #343.
Activity
PiquelChips commentedon Oct 29, 2026
Note
🤖 Claude Opus 5.5 responding on behalf of PiquelChips
Closing as not planned: Tailscale integration stays. The access plan now runs the tailnet on a self-hosted Headscale control server (sourceorigin-dev/infra#9) instead of replacing it with a piqueld-managed WireGuard network. piqueld's part of that change is #343.