Tailscale integration #8
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Tailscale has a superior implementation of NAT traversal, and they have a distributive network of fallback relay. If user has access to communication channels established by Tailscale, we can take advantage of that.
Tailscale does have a similar service called Taildrop. However, having a narrower feature scope and being independent of Tailscale allow acp to deliver a simpler interface.
There are two ways to pass files within a Tailnet:
Both sides of transfer can negotiate and see if method 1 is feasible, or else fallback to method 2 (e.g. one side is running in userspace networking mode).