- Notifications
You must be signed in to change notification settings - Fork928
feat: Use Tailscale networking by default#4003
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
Removal of WebRTC code will happen in another PR, but itfelt dangerious to default and remove in a single commit.Ideally, we can release this version and collect finalthoughts and feedback before a full commitment.
Tailscale doesn't support this, and adding supportfor it shouldn't block our rollout. Customers canalways forward over SSH.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
Why remove the Unix forwarding from the port-forward command? It might be more work to implement it with wireguard but if it's replacing webrtc it should at least have parity.
Uh oh!
There was an error while loading.Please reload this page.
Co-authored-by: Dean Sheather <dean@deansheather.com>
@deansheather it seems like it'd be quite a lot of work to implement, and the scope isn't quite clear. For now, I recommend we tell users to forwards UNIX sockets over SSH (even though the throughput isn't the best). |
Uh oh!
There was an error while loading.Please reload this page.
Removal of WebRTC code will happen in another PR, but it felt dangerous to default and remove in a single commit.
Ideally, we can release this version and collect final thoughts and feedback before fully committing.