juanfont/headscale

[Feature] List client versions in node list.

Open

#2356 opened on Jan 20, 2025

View on GitHub
 (3 comments) (0 reactions) (0 assignees)Go (38,374 stars) (2,104 forks)batch import
CLIenhancementgood first issuehelp wantedno-stale-bot

Description

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

Contributor guide

Tech stack
gorest api
Domain
backendapi
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.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
GoDatabase schemaREST API design
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50
Research direction
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.