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

Can mobile clients use the WireGuard app? #113

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

Originally created by @kennyparsons on GitHub (Jan 29, 2022).

I really love Tailscale, except that the control server is not open source and that the iOS app is a huge battery drain. It does not implement on demand capabilities.

Is it possible for a solution like this to generate the proper WireGuard config file to use with the WireGuard native iOS app?

So I have a finite amount of clients, say 10. I only have 2-3 that are truly mobile. Is a control server "check in" required to make it work? I'm unfamiliar with exactly how the mesh overlay is created and continuously updated for all other clients. I'm assuming a static WireGuard config would not be able to know if/when another client changes networks (dynamic ip, roaming, etc.)

As a consolation, I wonder if a static WireGuard config file could be downloaded, but options added to just connect to one "relay" server all the time and get its "mesh connectivity" from the relay, since it won't have constant updates from the control plane.

Originally created by @kennyparsons on GitHub (Jan 29, 2022). I really love Tailscale, except that the control server is not open source and that the iOS app is a huge battery drain. It does not implement on demand capabilities. Is it possible for a solution like this to generate the proper WireGuard config file to use with the WireGuard native iOS app? So I have a finite amount of clients, say 10. I only have 2-3 that are truly mobile. Is a control server "check in" required to make it work? I'm unfamiliar with exactly how the mesh overlay is created and continuously updated for all other clients. I'm assuming a static WireGuard config would not be able to know if/when another client changes networks (dynamic ip, roaming, etc.) As a consolation, I wonder if a static WireGuard config file could be downloaded, but options added to just connect to one "relay" server all the time and get its "mesh connectivity" from the relay, since it won't have constant updates from the control plane.
adam added the tailscale-feature-gapwontfix labels 2025-12-29 01:23:26 +01:00
adam closed this issue 2025-12-29 01:23:26 +01:00
adam commented 2025-12-29 01:23:27 +01:00
Author
Owner
Copy Link

@kennyparsons commented on GitHub (Jan 29, 2022):

Sorry for the bug label. I meant this only as a question of capabilities.

@kennyparsons commented on GitHub (Jan 29, 2022): Sorry for the bug label. I meant this only as a question of capabilities.
adam commented 2025-12-29 01:23:27 +01:00
Author
Owner
Copy Link

@madjam002 commented on GitHub (Jan 30, 2022):

Relay servers in Tailscale are implemented as DERP servers which are over TCP, plus there is a question of network policies, NAT traversal/magicsock, MagicDNS, the list grows longer with every Tailscale feature release.

So it's unlikely this is possible but I might be wrong.

If you've only got 10 clients I'd recommend just sticking with vanilla Wireguard to be honest as once you strip out all of the above that's basically what you're left with in terms of feature set.

@madjam002 commented on GitHub (Jan 30, 2022): Relay servers in Tailscale are implemented as DERP servers which are over TCP, plus there is a question of network policies, NAT traversal/magicsock, MagicDNS, the list grows longer with every Tailscale feature release. So it's unlikely this is possible but I might be wrong. If you've only got 10 clients I'd recommend just sticking with vanilla Wireguard to be honest as once you strip out all of the above that's basically what you're left with in terms of feature set.
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 tailscale-feature-gap wontfix
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#113
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?