IP

  1. My computer’s IP address is 192.168.4.27
  2. The value in the upper layer protocol field is 01 (ICMP)
  3. The IP header length is 20. The total length of the datagram is 84, meaning the payload is 64 bytes.
  4. This IP datagram has not been fragmented. We can tell because all flags, as well as the fragmentation offset, are 0.
  5. The identification and checksum fields always change from one datagram to the next.
  6. The other fields, except for the TTL field, stay constant. The protocol, source, and destination fields must stay constant. The identification and checksum (because it is a function in part of the identification field) must change.
  7. The identification field appears to be incremented by 1 for each datagram sent.
  8. The value of the identification field of the first ICMP TTL-exceeded reply is 36949. The TTL value is 64.
  9. The identification value changes for each reply. The TTL value stays the same.
  10. The first UDP message of packet size 2000 has been fragmented across two IP datagrams.
  11. The first fragment has the “More fragments” flag set. It has a fragmentation offset of 0. It has a total length of 1500 (the length of an Ethernet frame): IP Datagram Header 1
  12. The second fragment indicates that it is not the first fragment by having a “Fragment offset” value greater than 0. There are no more fragments, as indicated by the “More fragments” bit being set to 0: IP Datagram Header 1
  13. The fields that change between the first and second fragments are: total length, flags (more fragments), and fragment offset.
  14. The UDP message of 3500 bytes is split into three fragments.
  15. The first fragment has a total length of 1500, the “More fragments” flag set, and a fragment offset of 0. The second has a total length of 1500, the “More fragments” flag set, and a fragment offset of 1480. The third has a total length of 540, the “More fragments” flag not set, and a fragment offset of 2960 (2960 + 540 = 3500).

Back to wireshark_labs