fix(dcutr): update the DCUtR initiator transport direction to Inbound#994
Merged
diegomrsantos merged 5 commits intounstablefrom Nov 29, 2023
Merged
fix(dcutr): update the DCUtR initiator transport direction to Inbound#994diegomrsantos merged 5 commits intounstablefrom
diegomrsantos merged 5 commits intounstablefrom
Conversation
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## unstable #994 +/- ##
=========================================
Coverage 83.23% 83.24%
=========================================
Files 91 91
Lines 15328 15325 -3
=========================================
- Hits 12759 12758 -1
+ Misses 2569 2567 -2
|
lchenut
approved these changes
Nov 29, 2023
This was referenced Nov 30, 2023
romanzac
pushed a commit
that referenced
this pull request
Dec 13, 2023
This file contains hidden or 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.
During DCUtR, the listener initiates the direct connection (it is called the DCUtR client) attempt and must connect to the other peer as the incoming upgrade direction. Yamux must use this direction to decide on using odd or even stream IDs, not the initial underlying connection direction or socket "direction". It means we need to change the underlying TCP connection direction to Inbound, despite it being a dial.
This is an unusual case where a peer initiates a connection, but should treat it as incoming. The reason is probably that DCUtR happens when the other remote peer dials a peer's relayed address, therefore the original connection was in fact incoming.
Related:
https://github.com/libp2p/specs/tree/master/yamux
https://github.com/libp2p/specs/blob/master/relay/DCUtR.md