fix: resolve #360 — Unable to detect some traffic#505
Open
chinhkrb113 wants to merge 3 commits into
Open
Conversation
Fixes imsnif#360 Signed-off-by: ChinhLee <76194645+chinhkrb113@users.noreply.github.com>
Fixes imsnif#360 Signed-off-by: ChinhLee <76194645+chinhkrb113@users.noreply.github.com>
Fixes imsnif#360 Signed-off-by: ChinhLee <76194645+chinhkrb113@users.noreply.github.com>
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
Combined multi-file contribution:
Changes
src/network/connection.rssrc/network/sniffer.rssrc/network/utilization.rsWhy
src/network/connection.rs: The iperf3 reverse-mode case indicates that packets flowing from the remote server to the local client are not being attributed to the same tracked connection as packets flowing from local to remote. This is commonly caused by treating a TCP/UDP 4-tuple as directional, eg.(src_ip, src_port, dst_ip, dst_port), while process/socket lookup data is usually represented from the local endpoint perspective. For reverse traffic, the packet tuple is flipped, so lookup misses and the traffic is either ignored or counted only as unrelated control traffic.