![]() ![]() Is it normal to see the same packet sequence number sent with additional data? I guess this can only happen when an ack is dropped and in the meantime additional data was written right?Ĥ) Assuming the ACK in #1479 was dropped caused the retransmission, albiet with additional data, to happen in #1480, what can be learned from the fact that the retransmission was 27 seconds later? Shouldn't the retransmission have happened (with or without subsequent data) every half second or so? It seems like if the client did not get the ACK it it would have retransmitted earlier. Is this considered an out-of-order because the second packet was different in its data portion (seq and ack were the same)?Īm I reading this correctly that the client never saw the ACK in #1479? It was 27 seconds before the out-of-order packet came in that duplicated the data in #1478. This was reported as a TCP Out-of-order as opposed to a retransmission. In fact, it contains everything #1478 did, plus the next block of data it was to send. The client then sends the same sequence packet as it did in #1478, but the data is larger. The dialog is going fine and the client sends 67 bytes of data in #1478 and the host is ACKs in #1479. I've zeroed in on a sample, but I see this multiple places. ![]() I've got a situation where there appears to be timeouts on the client side. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |