Revision history  [back]

In system configuration, we have set Initial receive window size value as 22* MSS but when checked via wireshark capture we cannot see that in TCP SYN or TCP ACK packets so just want to know how that Initial receive window value is related with Window size value we see in trace.

MSS is set as 1360 so based on that Initial window size should be 29920 but in trace in SYN request i can see window size as 43520, in ACK(in response to SYN-ACK from server) Window size was 45056 and some different value in subsequent ACK/PUSH/ACK packets

So my question is in which packet I can see initial receive window size in wireshark.

Also One more to notice was even TCP window scale was 16 still in SYN packet I always see window size and calculated window size as same so not sure why Window scale multiplier doesn't come into the picture for SYN packet.

Can anyone explain also make me understand the benefit of high Initial receive window size?

This is the call flow between end-user and Internet server and my product behave as TCP full transparent proxy.

Client ------------> My Product -------> Server

TCP SYN-->

<--SYN/AC-- --ACK--->
TCP SYN-->
<--SYN/AC-- --ACK---> From my product point of View towards Client, it must share its initial window size in SYN/ACK message towards the client and towards server-side it should share Initial window size in TCP SYN message. On client-side next message is ACK which doesn't carry any payload while on Server side next message is SYN/ACK which also doesn't carry any payload then how come setting Initial receive window size as this Initial window size value is of any use? As after those messages, new ACK message with new window size will be shared valid for one response and any payload from the Internet towards my product after some different value will be set as you mentioned Linux tcp_moderate_rcvbuf to provide max throughput. Is that true or from my product towards client will follow that new window size to send payload then how this there is real benefit of keeping high initial window size value is of any use or initial window size is shared after initial TCP handshake?receive window size.

In system configuration, we have set Initial receive window size value as 22* MSS but when checked via wireshark capture we cannot see that in TCP SYN or TCP ACK packets so just want to know how that Initial receive window value is related with Window size value we see in trace.

MSS is set as 1360 so based on that Initial window size should be 29920 but in trace in SYN request i can see window size as 43520, in ACK(in response to SYN-ACK from server) Window size was 45056 and some different value in subsequent ACK/PUSH/ACK packets

So my question is in which packet I can see initial receive window size in wireshark.

One more to notice was even TCP window scale was 16 still in SYN packet I always see window size and calculated window size as same so not sure why Window scale multiplier doesn't come into the picture for SYN packet.

Can anyone also make me understand the benefit of setting Initial receive window size as this will be valid for one response and after some different value will be set as you mentioned Linux tcp_moderate_rcvbuf to provide max throughput. Is that true or there is real benefit of keeping high initial receive window size.

In system configuration, we have set Initial receive window size value as 22* MSS but when checked via wireshark capture we cannot see that in TCP SYN or TCP ACK packets so just want to know how that Initial receive window value is related with Window size value we see in trace.

MSS is set as 1360 so based on that Initial window size should be 29920 but in trace in SYN request i can see window size as 43520, in ACK(in response to SYN-ACK from server) Window size was 45056 and some different value in subsequent ACK/PUSH/ACK packets

So my question is in which packet I can see initial receive window size in wireshark.

One more to notice was even TCP window scale was 16 still in SYN packet I always see window size and calculated window size as same so not sure why Window scale multiplier doesn't come into the picture for SYN packet.