Fix WireGuard inbound domain-based routing #5555
Draft
+26
−20
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.
WireGuard inbound sniffing/routing broken since PR #4030. The
sniffingRequestandtagwere stored in a sharedroutingInfostruct duringProcess(), causing race conditions when multiple peers connect concurrently—each call overwrites the session info used byforwardConnection().Changes
tagandsniffingRequestfrom context inNewServer()(same pattern as TUN handler)routingInfo: RemoveinboundTag/contentTagfields, keep onlyctxanddispatcherforwardConnection()creates freshsession.Inboundandsession.Contentusing stored configOriginal prompt
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.