juanfont/headscale

Support for WireGuard only peers

Open

#1,545 opened on Sep 7, 2023

View on GitHub
 (51 comments) (145 reactions) (0 assignees)Go (2,104 forks)batch import
enhancementhelp wantedneeds design docneeds investigationno-stale-bottailscale-feature-gap

Repository metrics

Stars
 (38,374 stars)
PR merge metrics
 (Avg merge 1d 11h) (33 merged PRs in 30d)

Description

Why

Tailscale just announced their support for integrated Mullvad exit nodes. Being able to configure a similar setup via Headscale and an independent Mullvad account (or other wireguard VPN provider) would be useful for those of us without a Tailscale account.

Description

I haven't looked deeply into the details, but it's my understanding that this is implemented via a "WireGuard only peer" feature, and then support in the Tailscale coordination server to synchronize these peers with Mullvad. I assume it would be possible for Headscale to allow manually configuring these peer types.

Contributor guide

Research direction
Study the WireGuard only peer implementation in Tailscale PR #7821 and identify the corresponding changes needed in the Headscale codebase.
Tech stack
go
Domain
backend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
GoWireGuardTailscale
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50