Scribd
Upload
16 views5 pages

Lab4aa Wireshark

Uploaded by

dokhang2489
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
16 views5 pages

Lab4aa Wireshark

Uploaded by

dokhang2489
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 5

A first look at the captured trace

1. What is the IP address and TCP port number used by the client computer
(source) that is transferring the file to gaia.cs.umass.edu? To answer this question,
it’s probably easiest to select an HTTP message and explore the details of the TCP
packet used to carry this HTTP message, using the “details of the selected packet
header window” (refer to Figure 2 in the “Getting Started with Wireshark” Lab if
you’re uncertain about the Wireshark windows.
The source IP address was 192.168.0.199 using source port 62904.

2. What is the IP address of gaia.cs.umass.edu? On what port number is it sending


and receiving TCP segments for this connection?
The destination IP address was 128.119.245.12 using source port 80.
3. What is the IP address and TCP port number used by your client computer
(source) to transfer the file to gaia.cs.umass.edu?
My IP address was 192.168.0.199 using source port 62904.
TCP Basics

4. What is the sequence number of the TCP SYN segment that is used to initiate
the TCP connection between the client computer and gaia.cs.umass.edu? What is
it in the segment that identifies the segment as a SYN segment?
The sequence number of the segment used to initiate the TCP connection is
0. There is a SYN flag indicating that it is a SYN segment.

5. What is the sequence number of the SYNACK segment sent by


gaia.cs.umass.edu to the client computer in reply to the SYN? What is the value of
the Acknowledgement field in the SYNACK segment? How did gaia.cs.umass.edu
determine that value? What is it in the segment that identifies the segment as a
SYNACK segment?
The sequence number of the SYNACK segment is 0.
The value of the acknowledgement field is 1. Which is the initial sequence
number +1.
The message carries flags that show it to be a SYN ACK message.
6. What is the sequence number of the TCP segment containing the HTTP POST
command? Note that in order to find the POST command, you’ll need to dig into
the packet content field at the bottom of the Wireshark window, looking for a
segment with a “POST” within its DATA field.
2436536571

8. What is the length of each of the first six TCP segments?


The length of each of the first TCP segment is 626.
The following segments are all 1452.

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?
Minimum available buffer space advertised: 132,096 bytes.
Throttling: No indication that the lack of receiver buffer space throttled the
sender, as the window size remains sufficient.

10. Are there any retransmitted segments in the trace file? What did you check for
(in the trace) in order to answer this question?
Yes, there is one. I find out in Wireshark’s "Expert Information" (found under
Analyze > Expert Information) can show any retransmission events in the trace,
along with other possible TCP issues.

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 247 in the text).
The receiver is typically acking 1452 bytes. There seems to be no case where the
receiver acks every other segment.

12. What is the throughput (bytes transferred per unit time) for the TCP
connection? Explain how you calculated this value.
First, I find the total amount of data transferred in the connection by locating
the first and last packets in the TCP stream. This is the difference between the
last sequence number (indicating the total bytes sent) and the initial sequence
number. Then I find The difference between these timestamps of the first packet
and the last one, gives the duration of the connection in seconds.:
𝐵𝑦𝑡𝑒𝑠 𝑡𝑟𝑎𝑛𝑠𝑓𝑒𝑟𝑟𝑒𝑑 115489
𝑇ℎ𝑟𝑜𝑢𝑔ℎ𝑝𝑢𝑡 = = = 98708(𝑏𝑝𝑠)
𝐷𝑢𝑟𝑎𝑡𝑖𝑜𝑛 1.17
TCP Congestion Control In Action

13. Use the Time-Sequence-Graph(Stevens) plotting tool to view the sequence


number versus time plot of segments being sent from the client to the
gaia.cs.umass.edu server. Can you identify where TCP’s slowstart phase begins and
ends, and where congestion avoidance takes over? Comment on ways in which
the measured data differs from the idealized behavior of TCP that we’ve studied in
the text.

The TCP slowstart phase begins at just above seq number 500, and ends just
before sequence number 7500. Congestion avoidance takes over at 7500.

You might also like