Skip to content

distinguish fast-open from probe echoes - #279

Open
marcus-pousette-hp wants to merge 4 commits into
mainfrom
fix/fast-open-probe-phase
Open

distinguish fast-open from probe echoes#279
marcus-pousette-hp wants to merge 4 commits into
mainfrom
fix/fast-open-probe-phase

Conversation

@marcus-pousette-hp

@marcus-pousette-hp marcus-pousette-hp commented Aug 4, 2026

Copy link
Copy Markdown
Contributor

Distinguish ordinary holepunch probes from the responder's intentional fast-open confirmation. [0] remains the probe and coordinated-punch payload, while [1] confirms fast-open after NAT analysis.

Initiator Responder Result
Old Old Existing behavior, including the premature-open bug
New New Probe echoes cannot prematurely select a socket while fast-open remains available
Old New Fast-open is preserved because existing initiators accept [1]
New Old Falls back to coordinated punching because the old responder's pre-punch [0] is ignored

For New → Old, compatibility depends on coordinated punching succeeding. If punching is rejected or unavailable, the connection can fail rather than only become slower. Both mixed-version directions are tested against HyperDHT 6.33.1

co-authored with AI

@marcus-pousette-hp marcus-pousette-hp changed the title fix: distinguish fast-open from probe echoes distinguish fast-open from probe echoes Aug 4, 2026
@marcus-pousette-hp
marcus-pousette-hp force-pushed the fix/fast-open-probe-phase branch from 1719e48 to 37268cb Compare August 13, 2026 13:07
@marcus-pousette-hp
marcus-pousette-hp marked this pull request as ready for review August 13, 2026 13:42
@marcus-pousette-hp
marcus-pousette-hp requested a review from a team August 13, 2026 13:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant