340
edits
Line 210: | Line 210: | ||
|Connection end can be regular FIN, RST, or timeout if no termination is seen at all | |Connection end can be regular FIN, RST, or timeout if no termination is seen at all | ||
|- | |- | ||
|TCP | |Max announced TCP window size | ||
|shows the size of the biggest TCP receive window announced for each direction of a connection. | |shows the size of the biggest TCP receive window announced for each direction of a connection. | ||
|- | |- | ||
|TCP | |Max TCP bytes in flight | ||
|shows how much of the TCP receive window of the corresponding direction has been used at max during the lifetime of the connection, in other words this is the bytes in flight of the opposite, sending direction. | |shows how much of the TCP receive window of the corresponding direction has been used at max during the lifetime of the connection, in other words this is the bytes in flight of the opposite, sending direction. | ||
|- | |- | ||
|TCP window size limit | |Announced TCP window size limit | ||
|The TCP window size limit columns show the maximum possible value that could be used for the TCP receive window size. This is calculated from the announced TCP window scale option for each direction of a connection. The raw window scale (ws) shift count value is displayed in parentheses next to the byte value. | |The TCP window size limit columns show the maximum possible value that could be used for the TCP receive window size. This is calculated from the announced TCP window scale option for each direction of a connection. The raw window scale (ws) shift count value is displayed in parentheses next to the byte value. | ||
|- | |- |
edits