copy and paste this google map to your website or blog!
Press copy button and paste into your blog or website.
(Please switch to 'HTML' mode when posting into your blog. Examples: WordPress Example, Blogger Example)
Why is the last ACK needed in TCP four way termination The question of why the last ACK is required is just that nay FIN only means that the sender of the FIN is done sending, and it must still be open to receive more segments, and it must resend any unacknowledged segments Each side is a peer (client server is an application concept), and both sides must agree that everything is done
NACK vs. ACK? When to use one over the other one? 23 Personally I don't even feel that there is a need for ACK It's faster if we just send NACK (n) for the lost packets instead of sending an ACK for each received packet So when which situations would one use ACK over NACK and viceversa?
Why need Ack flag if we already have ack number in TCP The ACK flag indicates that the Acknowledgment Number field is significant, ie containing a meaningful value When a socket connection has already been established that is nearly always the case, but it isn't while a connection is being established Acknowledgment Number: 32 bits If the ACK control bit is set this field contains the value of the next sequence number the sender of the segment
TCP Fast Retransmit and duplicated acknowledgements Ask Or better yet, do an upload, and you can see your client doing a Fast Retransmit after it sees 3 identical ACK's You can also look closer at the TCP options and see the SACK's that manbearpig alluded to
The reason why TCP sends consecutive ACKs all together While analyzing Wireshark capturing, I noticed that the sender or the receiver sometimes sends a bunch of consecutive ACKs together as oppose to what I have learned I learned that for every packet