You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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: