Skip to content

refactor(network): remove Tailscale #347

Closed as not planned
Closed as not planned

Description

@PiquelChips

Problem

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.

Dependencies


Written with Claude Opus 5.5 in Claude Code (via T3 Code).

Activity

  1. PiquelChips commented on Oct 29, 2026

    @PiquelChips
    MemberAuthor

    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.

  2. moved this from Needs Triage to Done in origin-src.devon Oct 29, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions