TCP connection(including the segment containing the HTTP POST)?At what time was each segment sent?When was the ACK for each segment received? Given the difference between when each TCP segment was sent,and when its acknowledgement was received,what is the RTT value for each of the six segments?What is the EstimatedRTT value (see Section 3.5.3,page 242 in text)after the e that the value of the Estima easured Rfor thefirs ent,and then is computed using the EstimatedRTT equation on page 242 for all subsequent segments. Note:Wireshark has a nice feature that allows you to plot the RTT for each of the TCP segments sent.Select a TCP segment in the"listing of captured packets"window that is being sent from the client to the gaia.cs.umass.edu server.Then select:Statistics->TCP Stream Graph- >Round Trip Time Graph. 8.What is the length of each of the first six TCP segments?4 9 What is themunt of available buffer space advertised at the received for the entire trace?Does the lack of receiver buffer space e 10.Are there any re ansmitted se ents in the trace file?What did you check for(in the trace)i 11.Hov chdatao swer th中 is questio e recei lly acknowledge in an ACK?Car receive on page 250 in the text) 12 Wha the throughput(bytes transferred per unit time)for the TCP connection? value is the standard maximum length allowed by Ethemnet If your trace indicates a TCP o arge TCp ction,then Wireshark is repor ting the wrong ment rathe an m ACK We recommend that if you have this inconsistency,that you performTCP connection (including the segment containing the HTTP POST)? At what time was each segment sent? When was the ACK for each segment received? Given the difference between when each TCP segment was sent, and when its acknowledgement was received, what is the RTT value for each of the six segments? What is the EstimatedRTT value (see Section 3.5.3, page 242 in text) after the receipt of each ACK? Assume that the value of the EstimatedRTT is equal to the measured RTT for the first segment, and then is computed using the EstimatedRTT equation on page 242 for all subsequent segments. Note: Wireshark has a nice feature that allows you to plot the RTT for each of the TCP segments sent. Select a TCP segment in the “listing of captured packets” window that is being sent from the client to the gaia.cs.umass.edu server. Then select: Statistics->TCP Stream Graph- >Round Trip Time Graph. 8. What is the length of each of the first six TCP segments?4 9. What is the minimum amount of available buffer space advertised at the received for the entire trace? Does the lack of receiver buffer space ever throttle the sender? 10. Are there any retransmitted segments in the trace file? What did you check for (in the trace) in order to answer this question? 11. How much data does the receiver typically acknowledge in an ACK? Can you identify cases where the receiver is ACKing every other received segment (see Table 3.2 on page 250 in the text). 12. What is the throughput (bytes transferred per unit time) for the TCP connection? Explain how you calculated this value. 4 The TCP segments in the tcp-ethereal-trace-1 trace file are all less that 1460 bytes. This is because the computer on which the trace was gathered has an Ethernet card that limits the length of the maximum IP packet to 1500 bytes (40 bytes of TCP/IP header data and 1460 bytes of TCP payload). This 1500 byte value is the standard maximum length allowed by Ethernet. If your trace indicates a TCP length greater than 1500 bytes, and your computer is using an Ethernet connection, then Wireshark is reporting the wrong TCP segment length; it will likely also show only one large TCP segment rather than multiple smaller segments. Your computer is indeed probably sending multiple smaller segments, as indicated by the ACKs it receives. This inconsistency in reported segment lengths is due to the interaction between the Ethernet driver and the Wireshark software. We recommend that if you have this inconsistency, that you perform this lab using the provided trace file