Repository navigation
Conversation
MarcoPolo
left a comment
There was a problem hiding this comment.
I think this page would be better as a much higher level overview of dcutr and nat holepunching. It can even be shorter. And simply link to the spec to have it explain the technical details.
| they can continue using the relay connection. Once the two nodes have synchronized, they can simultaneously | ||
| open a connection to each other's addresses, allowing for successful hole punching. | ||
|
|
||
| The DCUtR protocol supports TCP and QUIC connections with slightly different procedures. For TCP |
There was a problem hiding this comment.
This part is also somewhat technical, and I feel like would be better to just link to the spec directly.
There was a problem hiding this comment.
I think this is important to have but simplified it even more. We also link to the spec at the bottom.
|
Maybe we want to link: https://tailscale.com/blog/how-nat-traversal-works/ |
Let's do that! At some point, I'd like to have our own post about NAT traversal that uses pretty diagrams, but for now, the Tailscale blog post is a good reference. |
Co-authored-by: Prithvi Shahi <50885601+p-shahi@users.noreply.github.com>
|
@MarcoPolo Can you take a look at this PR, it looks good to merge from my end |
|
@MarcoPolo or @mxinden need a review from either of you |
|
This is ready, will merge when ci/builds finish |
Context
Latest preview
Please view the latest Fleek preview here.