Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(network-monitor): Include the packet payload regarless of L4 protocol #303

Merged
merged 2 commits into from
Jun 24, 2024

Conversation

vadorovsky
Copy link
Member

@vadorovsky vadorovsky commented Jun 24, 2024

  • User-space part of pulsar is expecting the buffer to be initialized regardless of L4 protocol (TCP or UDP).
  • DNS responses, if long enough, might go through TCP. Not very common, but possible.
  • Stop returning an error when packet payload length is 0. It's totally normal for SYN, SYN-ACK and ACK packets. Logging errors for them is an unnecessary noise.

Fixes #297

…ocol

* User-space part of pulsar is expecting the buffer to be initialized
  regardless of L4 protocol (TCP or UDP).
* DNS responses, if long enough, might go through TCP. Not very common,
  but possible.
* Stop returning an error when packet payload length is 0. It's totally
  normal for SYN, SYN-ACK and ACK packets. Logging errors for them is
  an unnecessary noise.

Fixes #297
@vadorovsky vadorovsky merged commit 38c6c5b into main Jun 24, 2024
21 checks passed
@vadorovsky vadorovsky deleted the vadorovsky/fix-network-monitor branch June 24, 2024 14:03
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.

network-monitor dns error
2 participants