Wireshark TCP/HTTP Connections #158
|
SUMMARY STEPS TO REPRODUCE
EXPECTED and ACTUAL RESULT ENVIRONMENT
ADDITIONAL INFORMATION |
Replies: 3 comments
|
@peremen apologies for tagging, but would you happen to have any insight on this? I’m happy to investigate the code base if you have any potential strategies in mind. |
|
It is usually considered rude for pinging in less than two days apart. I do not have a commercial contract or obligation regarding processing the issues. There are duplicate packets in the trace: 310/311, 312/313 looks the same, but I don't think there was an actual retransmission. And I also recommend understanding how TCP handshake works: https://www.sciencedirect.com/topics/computer-science/three-way-handshake The packet 310 is a TCP SYN packet, which usually does not contain the payload (Len=0). The packet 312: for whatever reason, the server did not want to establish a TCP connection, therefore answering with FIN+ACK packet. Since the original sequence number was 0, ack number is then 1, server's sequence number was 85. |
|
Apologies again--this shows my in-experience with the open-source community, and that I need to get better at communicating. I will look into this deeper. Thank you. |

It is usually considered rude for pinging in less than two days apart. I do not have a commercial contract or obligation regarding processing the issues.
There are duplicate packets in the trace: 310/311, 312/313 looks the same, but I don't think there was an actual retransmission. And I also recommend understanding how TCP handshake works: https://www.sciencedirect.com/topics/computer-science/three-way-handshake The packet 310 is a TCP SYN packet, which usually does not contain the payload (Len=0). The packet 312: for whatever reason, the server did not want to establish a TCP connection, therefore answering with FIN+ACK packet. Since the original sequence number was 0, ack number is the…