Scribd
Upload
19 views2 pages

Computer Network Assignment - 1

Uploaded by

Amit Choubey
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
19 views2 pages

Computer Network Assignment - 1

Uploaded by

Amit Choubey
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/ 2

1.

In the upper layer protocol field the value given is 0x01, it


represents ICMP.
2. The IP Header Length as specified in the header length field is 20
bytes.
The total length of the IP Datagram is mentioned as 56bytes.
Payload Size = Total Length – Header Length
= 56 – 20
=36 bytes
Therefore, the payload size is 36bytes.

The payload consists of the data of the upper layer protocol, i.e.
ICMP

3. This IP Datagram has not been fragmented.


To determine if an IP datagram has been fragmented, we need to
examine the More Fragments flag and the Fragment Offset field
in the IP header.
More Fragments Flag: This flag indicates whether there are more
fragments to follow. If this bit is 0, it means that this datagram is not
part of a fragmented sequence or that it is the last fragment in a
series (if it were fragmented).
Fragment Offset: This field specifies the offset of the current
fragment within the original datagram. It indicates where this
fragment should be placed when reassembling the original
datagram.
In the given wireshark capture both the More Fragments bit and the
Fragment Offset bit is set to 0, which indicates that the datagram is
not fragmented.
4. The identification field has a value of 0x80b2 which is 32946
decimal equivalent. TTL value field is 1.
5. Yes, the message corresponding to the above packet has been
fragmented.
6. There are two important fields in the datagram which indicate
datagram has been fragmented.
Flags Field: The Flags field in Frame 121 is 0x02. It indicates
that the More Fragments (MF) bit is set, meaning this is part of a
fragmented message and that more fragments follow this one.

Fragment Offset: The Fragment Offset is 0 in Frame 121,


indicating that this is the first fragment of the IP datagram. Subsequent
fragments would have non-zero fragment offset values, indicating their
position within the original message.
7. The fragment offset bit is set to 0 in the attached capture which
indicates that this is the first segment of the IP datagram.
8. The Fragment Offset field in the IP header specifies the position of
this fragment within the original datagram. The Fragment Offset if
zero it indicates that the Fragment is the initial one. Here, the
Fragment Offset is 1480 (a non-zero value), indicating it is a
subsequent fragment rather than the initial one.
9. No, there are no more fragments. In the IP header, the "Flags" field
does not have the "More Fragments" (MF) flag set. When the "MF"
flag is set to 0, it indicates that this is the last fragment of the
datagram.
10. Total Length: The length field varies between fragments
since each fragment contains a different portion of the original
packet. In Fig. 2, the Total Length is 1514 bytes, while in Fig. 3, it is
534 bytes.
Flags and Fragment Offset:
Fragment Offset: This field changes to indicate the position of
each fragment within the original message. In Fig. 2, the Fragment
Offset is set to 0, indicating the first fragment. In Fig. 3, the
Fragment Offset is 1480, indicating the starting point of the second
fragment within the packet.
Flags: The "More Fragments" flag (in the Flags field) is set in Fig. 2,
indicating that additional fragments follow. In Fig. 3, this flag is not
set, indicating it’s the last fragment.
Header Checksum: Since the IP header changes between
fragments (due to differences in length and fragment offset), the
checksum recalculates for each fragment, resulting in different
values in Fig. 2 and Fig. 3.

You might also like