-
-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for WireGuard only peers #40
Labels
feature request
New feature or request
Comments
Related: juanfont/headscale#1545 |
This issue is stale because it has been open for 90 days with no activity. |
Not stale. |
This issue is stale because it has been open for 90 days with no activity. |
Not stale. |
This issue is stale because it has been open for 90 days with no activity. |
Not stale. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Why
Tailscale announced their support for integrated Mullvad exit nodes a while back. Being able to configure a similar setup via ionscale and independent Mullvad account(s) would be useful.
Description
I haven't looked deeply into the details, but it's my understanding that this is implemented via a "WireGuard only peer" feature, and then support in the Tailscale coordination server to synchronize these peers with Mullvad. I assume it would be possible for ionscale to allow manually configuring these peer types. The way I see it, you'd add one or multiple Mullvad account(s) to a tailnet, and the ionscale server adds the needed public node keys to the Mullvad api up to the limit of your added Mullvad accounts.
The text was updated successfully, but these errors were encountered: