The window size is used to prevent congestion at the receiver (as opposed to the congestion window that tries to prevent congestion in the network). This weird ack with a sequence number one higher than the received fin is the acknowledgement for the fin. Why does it respond with an ack then?
Stuck in traffic? You're not alone. Check out the cities with the worst
This is how tcp is. Personally i don't even feel that there is a need for ack. I can't see the correlation between acks and the receive window property.
It would make sense if the ack is send whenever the bytes are read () from.
It's faster if we just send nack (n) for the lost packets instead of sending an ack. My client sends a segment with a sequence number that has already been ackd, and the server acks with the. While analyzing wireshark capturing, i noticed that the sender or the receiver sometimes sends a bunch of consecutive acks together as oppose to what.
