juanfont/headscale

[Feature] List client versions in node list.

Open

#2,356 建立於 2025年1月20日

在 GitHub 查看
 (3 留言) (0 反應) (0 負責人)Go (38,374 star) (2,104 fork)batch import
CLIenhancementgood first issuehelp wantedno-stale-bot

描述

Use case

After upgrading to 0.24 I see the following in the log unsupported client connected client_version=65 min_version=82, now this could have been there a while ago from 0.23 as well and the lack of support for an older tailscale client itself is not really a problem.

However, it seems neither the error message nor the node list show the tail scale client version, so I have no idea which client is causing this. Given that tailscale.com can show it I presume it's communicated to the control plane by the client.

Description

Please add the ability to find out the connected (or last seen) client version from headscale, ideally in the node list.

Contribution

  • I can write the design doc for this feature
  • I can contribute this feature

How can it be implemented?

No response

貢獻者指南

技術棧
gorest api
領域
backendapi
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-2 days
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
fresh
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
mostly clear
前置要求
GoDatabase schemaREST API design
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
50
研究方向
Start by examining the current node model in the database schema (e.g., headscale/db/nodes.go). Understand how client version information is communicated from the Tailscale client (look at the handshake or status messages). Then propose adding a field to store the client version in the node model, update the API endpoints that return node lists (likely in headscale/api/v1/), and ensure the field is populated when nodes connect. Review existing comments on this issue for any discussion about implementation approach.