Wireshark-bugs: [Wireshark-bugs] [Bug 5541] Custom Window Size Column Shows Two Values and Doesn
Date: Sat, 8 Jan 2011 09:45:54 -0800 (PST)

--- Comment #12 from Jim Aragon <[email protected]> 2011-01-08 09:45:53 PST ---
(In reply to comment #11)

> @Jim: Could you try an automated build from
> http://www.wireshark.org/download/automated/ (pick an installer with version
> 35425 or higher) to see whether the new window-scaling implementation does
> indeed suit your need?

Yes, it does. I tested on a TCP stream that included the three-way handshake,
then cut the handshake packets out of the .pcap file and tested again. It gives
me exactly what I'm looking for: Wireshark's best idea of the window size,
whether the three-way handshake was seen or not, and the tcp.window_size column
now sorts properly.

It's also very handy to be able to check the value of
tcp.window_size_scalefactor to find out whether Wireshark's calculated window
size is based on having seen the three-way handshake or not without having to
filter the stream and then go all the way back to the first packet. I can now
determine this without losing my place in the Packet List.

I'm happy!

Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.