Skip to content

tcpdrop: add support for dumping TCP drop reasons #5252

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

Merged
merged 1 commit into from
Mar 28, 2025

Conversation

ioworker0
Copy link
Contributor

@ioworker0 ioworker0 commented Mar 23, 2025

This commit adds support for dumping TCP drop reasons. It maps these reasons
to human-readable strings, making it easier to understand why TCP packets
are dropped. In cases where the drop reason is not supported, 'NOT_SPECIFIED'
will be displayed.

@ioworker0
Copy link
Contributor Author

Besides the bugfix[1], let's also take advantage of drop reasons; they will be very helpful for that purpose, as other eBPF tools like nettrace have already done ;)

[1] #5250

Cc @chenhengqi

This commit adds support for dumping TCP drop reasons. It maps these reasons
to human-readable strings, making it easier to understand why TCP packets
are dropped. In cases where the drop reason is not supported, 'NOT_SPECIFIED'
will be displayed.

Signed-off-by: Mingzhe Yang <[email protected]>
Signed-off-by: Lance Yang <[email protected]>
@ioworker0
Copy link
Contributor Author

Gently ping @chenhengqi

@chenhengqi chenhengqi merged commit 88d6219 into iovisor:master Mar 28, 2025
1 of 12 checks passed
@chenhengqi
Copy link
Collaborator

Just merged, thanks.

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.

2 participants