fix: avoid attributing forwarded traffic to local processes - #3040
Open
xream wants to merge 1 commit into
Open
Conversation
Skip process lookup when the source IP is not owned by this host, preventing source-port collisions from borrowing a local socket identity while preserving the existing fallback for local traffic.
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.
Forwarded connections can be attributed to an unrelated local process when their source port collides with a local socket, causing PROCESS-NAME rules to match traffic from another host.
This skips process lookup only when the source address is not owned by the mihomo host. Unlike exact-match-only changes in the Linux socket resolver, it leaves the existing netlink fallback intact for local traffic, including wildcard/NAT cases where strict matching may fail.