Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

asked 2024-06-04 05:49:26 +0000

aland gravatar image

TCP same ack, different payload

I am receiving 2 following tcp packets: 9000 → 34967 [PSH, ACK] Seq=803864717 Ack=348117840 Win=28960 Len=28 TSval=863760043 TSecr=0 9000 → 34967 [ACK] Seq=803864717 Ack=348117840 Win=28960 Len=0 TSval=863760043 TSecr=0 Why does this happen? How can this not be considered a retransmission?

TCP same ack, different payload

I am receiving 2 following tcp packets: 9000 → 34967 [PSH, ACK] Seq=803864717 Ack=348117840 Win=28960 Len=28 TSval=863760043 TSecr=0 TSecr=0

9000 → 34967 [ACK] Seq=803864717 Ack=348117840 Win=28960 Len=0 TSval=863760043 TSecr=0 Why does this happen? How can this not be considered a retransmission?

TCP same ack, different payload

I am receiving 2 following tcp packets: packets:

9000 → 34967 [PSH, ACK] Seq=803864717 Ack=348117840 Win=28960 Len=28 TSval=863760043 TSecr=0

9000 → 34967 [ACK] Seq=803864717 Ack=348117840 Win=28960 Len=0 TSval=863760043 TSecr=0 Why does this happen? How can this not be considered a retransmission?

TCP same ack, different payload

I am receiving 2 following tcp packets:

9000 → 34967 [PSH, ACK] Seq=803864717 Ack=348117840 Win=28960 Len=28 TSval=863760043 TSecr=0

9000 → 34967 [ACK] Seq=803864717 Ack=348117840 Win=28960 Len=0 TSval=863760043 TSecr=0 TSecr=0

Why does this happen? How can this not be considered a retransmission?

click to hide/show revision 5
None

updated 2024-06-04 06:46:40 +0000

SYN-bit gravatar image

TCP same ack, different payload

I am receiving 2 following tcp packets:

9000 → 34967 [PSH, ACK] Seq=803864717 Ack=348117840 Win=28960 Len=28 TSval=863760043 TSecr=0
 
TSecr=0
9000 → 34967 [ACK] Seq=803864717 Ack=348117840 Win=28960 Len=0 TSval=863760043 TSecr=0
TSecr=0

Why does this happen? How can this not be considered a retransmission?