4.TCP congestion control in action Let's now amount of data sent pe sly!) gths from the raw dat Vireshark window use one of wireshark's TCP graphing utilities-Time-Sequence-aphStevens plot out data. .Select a TCP segment in the Wireshark's"listing of captured-packets"window. Then select the menu:Statistics->TCP Stream Graph->Time-Sequence- Graph(Stevens).You should see a plot that looks similar to the following plot which was created from the captured packets in the packet trace tep-ethereal- trace-/in http://gaia.cs.umass.edu/wireshark-labs/wireshark-traces.zip(see earlier footnote): TCP Graph 8:top-ethereal-trece-1 192168.1.102:1161->128.119 0 450000- 100000 50000 10 15 25 30 5 Tme(s] Here.each dot repr ents a TCP se ent sent,plotting the sequence number of segment the time at which ent tha above each other represents a series of packets that were sent back-to-back by the 4. TCP congestion control in action Let’s now examine the amount of data sent per unit time from the client to the server. Rather than (tediously!) calculating this from the raw data in the Wireshark window, we’ll use one of Wireshark’s TCP graphing utilities - Time-Sequence-Graph(Stevens) - to plot out data. • Select a TCP segment in the Wireshark’s “listing of captured-packets” window. Then select the menu : Statistics->TCP Stream Graph-> Time-Sequence￾Graph(Stevens). You should see a plot that looks similar to the following plot, which was created from the captured packets in the packet trace tcp-ethereal￾trace-1 in http://gaia.cs.umass.edu/wireshark-labs/wireshark-traces.zip (see earlier footnote ): Here, each dot represents a TCP segment sent, plotting the sequence number of the segment versus the time at which it was sent. Note that a set of dots stacked above each other represents a series of packets that were sent back-to-back by the sender