Skip to content

fix: resolve #447 — Traffic misidentification on routing host#504

Open
chinhkrb113 wants to merge 1 commit into
imsnif:mainfrom
chinhkrb113:improve/quality/provide-complete-local-address-informati
Open

fix: resolve #447 — Traffic misidentification on routing host#504
chinhkrb113 wants to merge 1 commit into
imsnif:mainfrom
chinhkrb113:improve/quality/provide-complete-local-address-informati

Conversation

@chinhkrb113

Copy link
Copy Markdown

Summary

To determine whether a packet endpoint is actually local, the Linux backend needs to expose all IP addresses assigned to the host, not just the selected capture interface address. A routing host can have multiple local addresses, such as Slocal and Svpn, and process matching must know the full set. Using only one interface address can cause valid local traffic on another interface to be treated as forwarded, or forwarded traffic to be treated as local

Fixes #447

Changes

  • src/os/linux.rs

Why

src/os/linux.rs: To determine whether a packet endpoint is actually local, the Linux backend needs to expose all IP addresses assigned to the host, not just the selected capture interface address. A routing host can have multiple local addresses, such as Slocal and Svpn, and process matching must know the full set. Using only one interface address can cause valid local traffic on another interface to be treated as forwarded, or forwarded traffic to be treated as local.

Fixes imsnif#447

Signed-off-by: ChinhLee <76194645+chinhkrb113@users.noreply.github.com>
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.

Traffic misidentification on routing host

1 participant