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

tcpdump cuts off header options #209

Open
tflach opened this issue May 11, 2016 · 0 comments
Open

tcpdump cuts off header options #209

tflach opened this issue May 11, 2016 · 0 comments

Comments

@tflach
Copy link

tflach commented May 11, 2016

For packet captures, the capture length is currently set to a size that cuts off almost all TCP header options. When analyzing traces it is very useful to be able to see SACK blocks. In older traces at least the first SACK block was still captured, however since many connections now have timestamps enabled SACKs are pushed further out in the header, and they are no longer captured at all.

It would be very beneficial to use a mechanism that does not truncate header options. I am aware that header length is dynamic, so maybe there is a way to sanitize traces after capturing while extending capture length to make sure that headers are always completely captured?

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

No branches or pull requests

1 participant