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

TCP/IP not handling "DUP ACK" from the remote end #24

Open
watsonads opened this issue Jun 18, 2024 · 0 comments
Open

TCP/IP not handling "DUP ACK" from the remote end #24

watsonads opened this issue Jun 18, 2024 · 0 comments

Comments

@watsonads
Copy link

I'm evaluating the performance of the hardened tcp/ip stack with the iperf client user module. After transferring for less than 1sec, the transfer stop. I monitor the tcp traffic with wireshark. I can find a lot of "DUP ACK" packet from the iperf server side (Desktop PC with 100G QSFP interface).

The DUP ACK packets all point to the same sequence number - 872278593.
Screenshot from 2024-06-18 17-00-23

Looks like tcp/ip not response to "DUP ACK".
Please advise.

Watson

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