fix: refresh repeated RakNet challenges#60
Open
RestartFU wants to merge 4 commits into
Open
Conversation
Protected endpoints may answer Request2 with another Reply1 and a new security cookie. Resend Request2 with the replacement handshake state instead of retrying stale values.
RestartFU
marked this pull request as ready for review
July 17, 2026 13:50
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
1 participant
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.
Summary
OpenConnectionReply1during the Request2 phaseProblem
Some protected RakNet endpoints issue another Reply1 after receiving the
first Request2. That reply carries a replacement security cookie. The dialer
currently ignores it and keeps retrying Request2 with the stale cookie until
the connection deadline expires.
Observed packet flow before the fix:
After refreshing the Request2 state:
Scope
This only fixes the initial open-connection handshake. Reconnect teardown and
expired-reader behavior are intentionally excluded.
Validation
gofmt -w dial.gogit diff --check