0% found this document useful (0 votes)
12 views7 pages

Lab10 (22l 6759)

Uploaded by

Umair Hassan
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
12 views7 pages

Lab10 (22l 6759)

Uploaded by

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

Question 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?

Question 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?

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
in the segment that identifies the segment as a SYN segment?
Part1:

Part2:
Question 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 the value of the
Acknowledgement field in the SYNACK segment? What is it in the segment that
identifies the segment as a SYNACK segment?

Part1:
Part b:
Part c:

Question 5: In packet 9, Ack = 2026 and Seq = 1. Explain these values?


Ans: This packet is sent as Ack of packet 2026 and has sequence no 1.

Question 6: In packet 16, Ack = 7866 and Seq = 1. Explain these values?
Ans: This packet is sent as Ack of packet 7866 and has sequence no 1.

Question 7: Why Wireshark uses relative sequence and ack?

Wireshark uses relative sequence and acknowledgment numbers to


simplify analysis, making large numbers easier to read and track,
focusing on data flow progress instead of raw values. It starts every
TCP stream at 0 for consistency, aiding troubleshooting and
readability.

Trace 2
Question 1: Select the first DNS packet in the trace. Determine, how
many fields there
are in the UDP header
There are 8 fields

Question 2: From the packet content field (click on any header and observe the display
in the Packet Bytes Window), determine the length (in bytes) of each of the UDP header
fields.

Ans: the length of each header of UDP packet is 8 bytes

Question 3: The value in the Length field is the length of what? Verify your claim using
the selected packet.

Ans:The length field in a UDP header specifies the total size of the UDP packet, including both the
header and the data, in bytes.

If the length field contains 52, this means the entire UDP packet is **52 bytes long**.

Since the UDP header is always 8 bytes, the payload (data) size would be:

Payload size = Total length - Header length = 52 - 8 = 44 bytes

Question 4: What is the port number to query the DNS Server?


Ans: The port number to query a DNS server is:53

This is the standard port used by the DNS protocol for both UDP (for most queries) and TCP (for zone
transfers or queries exceeding 512 bytes).

Q3
Sending message to server and receving responce

Connection Rejection

Disconnect feature

You might also like