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] Compatibility with Tailout #784

New Issue
Closed
opened 2025-12-29 02:23:59 +01:00 by adam · 7 comments
adam commented 2025-12-29 02:23:59 +01:00
Owner
Copy Link

Originally created by @plittlefield on GitHub (Sep 5, 2024).

Use case

Make Headscale work with the Tailout project.

Description

The project Tailout is very promising but has hit a snag working with a Headscale server instead of the Tailscale server.

Here is the issue I opened.

I hope you can help.

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 @plittlefield on GitHub (Sep 5, 2024). ### Use case Make Headscale work with the Tailout project. ### Description The project [Tailout](https://github.com/cterence/tailout) is very promising but has hit a snag working with a Headscale server instead of the Tailscale server. Here is the [issue](https://github.com/cterence/tailout/issues/15) I opened. I hope you can help. ### 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 enhancementstale labels 2025-12-29 02:23:59 +01:00
adam closed this issue 2025-12-29 02:23:59 +01:00
adam commented 2025-12-29 02:23:59 +01:00
Author
Owner
Copy Link

@kradalby commented on GitHub (Sep 5, 2024):

hmm, looks like it depends on being compatible with the Tailscale SaaS API, this is likely a huge undertaking, it comes up from time to time.

It looks like it only uses API keys and not oauth, making it less impossible. But it is likely more productive, or at least faster, to have tailout implement our new Policy API endpoint than us trying to copy the other one.

@kradalby commented on GitHub (Sep 5, 2024): hmm, looks like it depends on being compatible with the Tailscale SaaS API, this is likely a huge undertaking, it comes up from time to time. It looks like it _only_ uses API keys and not oauth, making it _less impossible_. But it is likely more productive, or at least faster, to have tailout implement our new Policy API endpoint than us trying to copy the other one.
adam commented 2025-12-29 02:23:59 +01:00
Author
Owner
Copy Link

@cterence commented on GitHub (Sep 5, 2024):

Thanks for your quick response @kradalby.
Would you therefore recommend for Tailout to support Headscale by reimplementing the specific API calls without using the Tailscale GO client ?

@cterence commented on GitHub (Sep 5, 2024): Thanks for your quick response @kradalby. Would you therefore recommend for Tailout to support Headscale by reimplementing the specific API calls without using the [Tailscale GO client](https://github.com/tailscale/tailscale-client-go) ?
adam commented 2025-12-29 02:24:00 +01:00
Author
Owner
Copy Link

@kradalby commented on GitHub (Sep 5, 2024):

That should allow you to set it up right now at least, we have a gRPC client, so it should be fairly straightforward to add it and use that as an alternative to the Tailscale go client, at least if we support the equivalent to all the endpoints you need.

The available funcs are here https://github.com/juanfont/headscale/blob/main/hscontrol/grpcv1.go, so you can give it a quick skim to see if all you need is there.

@kradalby commented on GitHub (Sep 5, 2024): That should allow you to set it up right now at least, we have a gRPC client, so it should be fairly straightforward to add it and use that as an alternative to the Tailscale go client, at least if we support the equivalent to all the endpoints you need. The available funcs are here https://github.com/juanfont/headscale/blob/main/hscontrol/grpcv1.go, so you can give it a quick skim to see if all you need is there.
adam commented 2025-12-29 02:24:00 +01:00
Author
Owner
Copy Link

@plittlefield commented on GitHub (Sep 5, 2024):

Wow, quick response - thanks everyone! :-)

@plittlefield commented on GitHub (Sep 5, 2024): Wow, quick response - thanks everyone! :-)
adam commented 2025-12-29 02:24:00 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Dec 25, 2024):

This issue is stale because it has been open for 90 days with no activity.

@github-actions[bot] commented on GitHub (Dec 25, 2024): This issue is stale because it has been open for 90 days with no activity.
adam commented 2025-12-29 02:24:00 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jan 1, 2025):

This issue was closed because it has been inactive for 14 days since being marked as stale.

@github-actions[bot] commented on GitHub (Jan 1, 2025): This issue was closed because it has been inactive for 14 days since being marked as stale.
adam commented 2025-12-29 02:24:00 +01:00
Author
Owner
Copy Link

@plittlefield commented on GitHub (May 7, 2025):

Any update?

@plittlefield commented on GitHub (May 7, 2025): Any update?
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 stale
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#784
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?