When the window full packet is sent shouldnt the next packet be a window zero and if that packet is not sent would this cause application issues here is the link to the capture file
It looks like you made the capture on the client system. The iRTT (initial roundtrip time) is 34 ms. The client was sending the data, so Wireshark sees the client send as much data that it fills the receive buffer on the receiving side, hence the window full notification. But the last received ACK from the server was an ACK to a packet that was sent ~34 ms ago. In the mean time the server is reading data from the receive buffer, opening up more space, as can be seen in the ACKs ~34ms after data has been sent.
If you would capture on the server side, there will be no Window full notifications as the ACKs follow the received data more directly.
Asked: Dec 17 '4
Seen: 1,889 times
Last updated: Dec 17 '24
