TCP:

1. What is the IP address and TCP port number used by the client
computer (source) that is transferring the alice.txt file to
gaia.cs.umass.edu?

The IP address of the client is 192.168.86.68, TCP port is 55639

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 ip address of gaia.cs.umass.edu is 128.119.245.12, TCP port is 80.

3. 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? (Note: this is the “raw” sequence number carried
in the TCP segment itself; it is NOT the packet # in the “No.” column in
the Wireshark window. Remember there is no such thing as a “packet
number” in TCP or UDP; as you know, there are sequence numbers in
TCP and that’s what we’re after here. Also note that this is not the
relative sequence number with respect to the starting sequence
number of this TCP session.). What is it in this TCP segment that
identifies the segment as a SYN segment? Will the TCP receiver in this
session be able to use Selective Acknowledgments ?

The sequence number of the TCP SYN segment is 423664649187, the flag
part (Syn bit: 1) in this TCP segment that identifies the segment as a SYN
segment. The TCP receiver in this session is able to use Selective
Acknowledgments since the SACK is permitted.
 4. 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
it in the segment that identifies the segment as a SYNACK segment?
What is the value of the Acknowledgement field in the SYNACK
segment? How did gaia.cs.umass.edu determine that value?

The sequence number of the TCP SYNACK segment is 1068969752, the flag
part (Syn + Acknowledgement bits : 1) in the segment that identifies the
segment as a SYNACK segment. The value of the Acknowledgement field in
the SYNACK segment is 4236649188. The value of the acknowledgement
field is 1 and is determined by the initial sequence number +1.

5. What is the sequence number of the TCP segment containing the

header of the HTTP POST command? Note that in order to find the
POST message header, you’ll need to dig into the packet content field
at the bottom of the Wireshark window, looking for a segment with the
ASCII text “POST” within its DATA fiel d 4 ,5 . How many bytes of data are
contained in the payload (data) field of this TCP segment? Did all of the
data in the transferred file alice.txt fit into this single segment?

The sequence number of the TCP segment is 4236649188. There are 1448
bytes in the payload, and all of the data in the transferred file alice.txt did
not fit into this single segment (since alice.txt is 152359)
6. Consider the TCP segment containing the HTTP “POST” as the first
segment in the data transfer part of the TCP connection:

• At what time was the first segment (the one containing the HTTP
POST) in the data-transfer part of the TCP connection sent?
Arrival Time: February 3rd, 2021, 09:43:26.716922000 SE Asia Standard
Time

UTC Arrival Time: February 3rd, 2021, 02:43:26.716922000 UTC

• At what time was the ACK for this first data-containing segment
received?
Arrival Time: February 3rd, 2021, 09:43:26.745546000 SE Asia Standard
Time

UTC Arrival Time: February 3rd, 2021, 02:43:26.745546000 UTC

• What is the RTT for this first data-containing segment?

The RTT is 09:43:26.745546000 - 09:43:26.716922000 = 0.028624

seconds

• What is the RTT value the second data-carrying TCP segment and
its ACK?

The second data-carrying has the Arrival Time of 09:43:26.716923000

and receive at 09:43:26.745551000

The RTT is 09:43:26.745551000 - 09:43:26.716923000 = 0.028628

seconds
 •What is the EstimatedRTT value (see Section 3.5.3, in the text) after
the ACK for the second data-carrying segment is received? Assume
that in making this calculation after the received of the ACK for the
second segment, that the initial value of EstimatedRTT is equal to the
measured RTT for the first segment and then is computed using the
EstimatedRTT equation on page 242, and a value of  = 0.125.

EstimatedRTT = (1-0.125) × 0.028624 + 0.125 × 0.028628 =

0.0286245 seconds.

7. What is the length (header plus payload) of each of the first four data-
carrying TCP segments?
All the four TCP data-carrying segments have the length of 1448 bytes and
the header length of 32 bytes, making the total of 1480 bytes.

8. What is the minimum amount of available buffer space advertised to

the client by gaia.cs.umass.edu among these first four data-carrying
TCP segments? Does the lack of receiver buffer space ever throttle the
sender for these first four datacarrying segments?
The minimum amount of available buffer space advertised to the client by
gaia.cs.umass.edu among these first four data-carrying TCP segments is 249.
The lack of receiver buffer space never throttles the sender for these first
four data carrying segments since we never reach the full capacity.

9. Are there any retransmitted segments in the trace file? What did you
check for (in the trace) in order to answer this question?

There are no retransmitted segments in the trace file. I check for the
sequence number, it does not repeat/goes down during the transmission
process, meaning it does not have to be retransmitted and if it does, it has to
be retransmitted.

10. How much data does the receiver typically acknowledge in an

ACK among the first ten data-carrying segments sent from the client to
gaia.cs.umass.edu? Can you identify cases where the receiver is
ACKing every other received segment (see Table 3.2 in the text) among
these first ten data-carrying segments?

Each one is 1448 bytes. First, the first ten data segments (Nos. 4, 5, 6, 9, 10,
11, 12, 14, 15, 20) are identified with sequence numbers and lengths.
Secondly, the ACKs from the receiver (128.119.245.12) for these segments
are listed: No. 7 (Ack=1449, Win=31872), No. 8 (Ack=2897, Win=34816),
No. 13 (Ack=4345, Win=37760), No. 16 (Ack=5793, Win=40576), No. 17
(Ack=7241, Win=43520), No. 18 (Ack=8689, Win=46336). ACK No. 19
(Ack=10137, Win=49280) is included as it acknowledges data within the
scope. Then, the data acknowledged per ACK is calculated: No. 7
acknowledges 1448 bytes No. 4, No. 8 acknowledges 1448 bytes No. 5, No.
13 acknowledges 1448 bytes No. 6, No. 16 acknowledges 1448 bytes No. 9,
No. 17 acknowledges 1448 bytes No. 10, No. 18 acknowledges 1448 bytes
No. 11, No. 19 acknowledges 1448 bytes No. 12, No.28 acknowledges 1448
bytes No.14, No.29 acknowledges 1448 bytes No.15, No.34 acknowledges
1448 bytes No.20. No ACK is acknowledging two segments in a row since
each ACK is acknowledging only 1 segment (1448 bytes), so there are no
cases where the receiver is acknowledging every other segment.

11. What is the throughput (bytes transferred per unit time) for the
TCP connection? Explain how you calculated this value.

The first segment of the data transferred part was sent at 09:43:26.716922
(question 6) and the whole data received at 09:43:26.8855 so the time it
took for the whole file to transfer is 09:43:26.8855 - 09:43:26.716922 =
0.168578 seconds. And the whole calculated window size has been
transferred is 194816 bits making the throughput 194816/0.168578 =
1155643.085 bits/second = 1.155643 Mbps.

12. 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. Consider the “fleets” of packets
sent around t = 0.025, t = 0.053, t = 0.082 and t = 0.1. Comment on
 whether this looks as if TCP is in its slow start phase, congestion
avoidance phase or some other phase.

The TCP is in its slow start phase

 13. These “fleets” of segments appear to have some periodicity.
What can you say about the period?

These fleets appear in these periods are around the same time as the RTT
calculated in questions 6.

14. Answer each of two questions above for the trace that you have
gathered when you transferred a file from your computer to
gaia.cs.umass.edu
The TCP segment is in the slow start phase

The RTT is about 0.024 seconds which is the same period at in each part of
the graph