Skip to content

fix: kick auth-fail pipes and tighten AuthTimeout - #47

Merged
esrrhs merged 1 commit into
masterfrom
fix/auth-fail-kick-pipes
Sep 20, 2026
Merged

esrrhs merged 1 commit into
masterfrom
fix/auth-fail-kick-pipes

Conversation

@esrrhs

@esrrhs esrrhs commented Sep 19, 2026

Copy link
Copy Markdown
Owner

Summary

  • Close main-channel pipes immediately on auth proof failure (LOGIN / CHANNEL_JOIN) so half-open RUDP/TCP workers cannot linger and burn CPU.
  • Add AuthTimeout (default 5s) for unauthenticated main channels; keep EstablishedTimeout for sonny business connects.
  • Add TCP/RUDP auth-fail load tests covering kick-and-release behavior.

No version bump / release in this PR.

Test plan

  • go test ./proxy/ -run TestAuthFail -count=1
  • Deploy to bwh and confirm auth-fail / half-open RUDP no longer sustains high CPU
  • Smoke: valid client still logs in normally within AuthTimeout

Made with Cursor

Failed LOGIN/CHANNEL_JOIN left half-open RUDP/TCP pipes burning CPU; close them immediately and default AuthTimeout to 5s so unauthenticated mains cannot linger.

Co-authored-by: Cursor <[email protected]>
@esrrhs
esrrhs merged commit e831cb9 into master Sep 20, 2026
8 checks passed
@esrrhs
esrrhs deleted the fix/auth-fail-kick-pipes branch September 20, 2026 02:52
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