starred/headscale
1
0
Fork 0
mirror of https://github.com/juanfont/headscale.git synced 2026-01-11 20:00:28 +01:00
Code Issues 98 Packages Projects Releases 10 Wiki Activity

[Feature] Synology support (tailscale client versions are behind) #1014

New Issue
Closed
opened 2025-12-29 02:27:31 +01:00 by adam · 2 comments
adam commented 2025-12-29 02:27:31 +01:00
Owner
Copy Link

Originally created by @tacognito on GitHub (May 8, 2025).

Use case

In headscale version 0.25, support for tailscale clients older than 1.62 is dropped. However, my (multiple) synology NAS's (which have an uptodate DSM version) the newest client version in the package center is 1.58.2.

Hence, dropping support for the older clients, support for Synology's is also dropped. This might have been an unintended consequence, so as such I'm reporting it. And, since the version drop was intentional I have marked this a feature request iso a bug.

I dont know why there are so far behind and I understand if supporting this version is too much of a hassle for you. But still, I though I'd check whether support could go to 1.58.2.

Thanks for you reply and above all for all the great work!

Description

See above

Contribution

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

How can it be implemented?

No response

Originally created by @tacognito on GitHub (May 8, 2025). ### Use case In headscale version 0.25, support for tailscale clients older than 1.62 is dropped. However, my (multiple) synology NAS's (which have an uptodate DSM version) the newest client version in the package center is 1.58.2. Hence, dropping support for the older clients, support for Synology's is also dropped. This might have been an unintended consequence, so as such I'm reporting it. And, since the version drop was intentional I have marked this a feature request iso a bug. I dont know why there are so far behind and I understand if supporting this version is too much of a hassle for you. But still, I though I'd check whether support could go to 1.58.2. Thanks for you reply and above all for all the great work! ### Description See above ### Contribution - [ ] I can write the design doc for this feature - [ ] I can contribute this feature ### How can it be implemented? _No response_
adam added the enhancement label 2025-12-29 02:27:31 +01:00
adam closed this issue 2025-12-29 02:27:31 +01:00
adam commented 2025-12-29 02:27:32 +01:00
Author
Owner
Copy Link

@tacognito commented on GitHub (May 8, 2025):

For others comming across this issue. I did find a manual way to update the client provided by tailscale.

You can find the packages here:
https://pkgs.tailscale.com/stable/#spks

You can find the specific one you need based on your cpu signature by modelname here:
https://github.com/SynoCommunity/spksrc/wiki/Synology-and-SynoCommunity-Package-Architectures

Then ssh into your Synology NAS and execute e.g.:
wget https://pkgs.tailscale.com/stable/tailscale-x86_64-1.82.5-700082005-dsm7.spk && sudo synopkg install tailscale-x86_64-1.82.5-700082005-dsm7.spk
(replace with your specific package)

DSM does checks on this, so if you provide the wrong package you get a nice warning and nothing is installed.

This did fix it for me, so now I can be on headscale 0.25. Question remains whether a check could be done on what the highest available client version in synology package centre is for ease of use. However, I completely understand when it would hamper to much progress in development to support clients so far back. On the one hand, a lot of people use Synology NAS's, on the other hand its ridiculous that they dont sooner review new versions of the tailscale client.

@tacognito commented on GitHub (May 8, 2025): For others comming across this issue. I did find a manual way to update the client provided by tailscale. You can find the packages here: https://pkgs.tailscale.com/stable/#spks You can find the specific one you need based on your cpu signature by modelname here: https://github.com/SynoCommunity/spksrc/wiki/Synology-and-SynoCommunity-Package-Architectures Then ssh into your Synology NAS and execute e.g.: ` wget https://pkgs.tailscale.com/stable/tailscale-x86_64-1.82.5-700082005-dsm7.spk && sudo synopkg install tailscale-x86_64-1.82.5-700082005-dsm7.spk ` (replace with your specific package) DSM does checks on this, so if you provide the wrong package you get a nice warning and nothing is installed. This did fix it for me, so now I can be on headscale 0.25. Question remains whether a check could be done on what the highest available client version in synology package centre is for ease of use. However, I completely understand when it would hamper to much progress in development to support clients so far back. On the one hand, a lot of people use Synology NAS's, on the other hand its ridiculous that they dont sooner review new versions of the tailscale client.
adam commented 2025-12-29 02:27:32 +01:00
Author
Owner
Copy Link

@kradalby commented on GitHub (May 8, 2025):

Sadly we are not able to support versions back, and will stick to our current 10 last version scheme. We would appreciate a PR for update to documentations on your findings regarding upgrading.

@kradalby commented on GitHub (May 8, 2025): Sadly we are not able to support versions back, and will stick to our current 10 last version scheme. We would appreciate a PR for update to documentations on your findings regarding upgrading.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
CLI
DERP
DNS
Nix
OIDC
SSH
bug
database
documentation
duplicate
enhancement
faq
good first issue
grants
help wanted
might-come
needs design doc
needs investigation
no-stale-bot
out of scope
performance
policy 📝
pull-request
Mirrored from GitHub Pull Request
 question
regression
routes
stale
tags
tailscale-feature-gap
well described ❤️
wontfix
No Label enhancement
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/headscale#1014
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?