juanfont/headscale

Support for WireGuard only peers

Open

#1,545 建立於 2023年9月7日

在 GitHub 查看
 (51 留言) (141 反應) (0 負責人)Go (38,374 star) (2,104 fork)batch import
enhancementhelp wantedneeds design docneeds investigationno-stale-bottailscale-feature-gap

描述

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.

貢獻者指南

技術棧
go
領域
backendinfrastructurecloud
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
5
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
over 1 week
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
active
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
needs investigation
前置要求
GoWireGuardTailscale architecture
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
10
研究方向
Review the referenced Tailscale PR #7821 to understand the WireGuard only peer concept. Examine the Headscale codebase to identify where peer synchronization and control server logic is handled. Participate in the discussions on this issue to clarify the scope and acceptance criteria, as many comments detail potential approaches and challenges.