IP packet structure in Computer Networks - Full Explanation

Introduction

Imagine sending a letter through the mail but needing a special envelope that tells the post office where to send it, how important it is, and how to handle it. Computers use a similar system called an IP packet to send data across networks safely and correctly.

Explanation

Version

This part tells the network which version of the Internet Protocol is being used, usually IPv4 or IPv6. It helps devices understand how to read the rest of the packet.

The Version field ensures the packet is processed according to the correct IP rules.

Header Length

This indicates the size of the packet's header, which can vary because of optional information. Knowing the header length helps devices find where the actual data starts.

Header Length tells where the data begins inside the packet.

Total Length

This field shows the entire size of the packet, including both header and data. It helps the receiving device know how much information to expect.

Total Length defines the full size of the packet for proper handling.

Identification, Flags, and Fragment Offset

These fields work together to manage packet fragmentation. If a packet is too big for a network segment, it is split into smaller pieces, and these fields help reassemble them correctly.

These fields ensure large packets are split and reassembled without errors.

Time to Live (TTL)

TTL limits how long a packet can travel through the network to prevent it from circulating forever. Each device that forwards the packet reduces this number by one.

TTL prevents packets from endlessly looping in the network.

Protocol

This field tells which higher-level protocol (like TCP or UDP) is inside the packet. It guides the receiving device on how to process the data part.

Protocol indicates the type of data carried inside the packet.

Header Checksum

This is a simple error-checking code for the header. It helps detect if the header was corrupted during transmission so the packet can be discarded if needed.

Header Checksum verifies the header's integrity.

Source and Destination IP Addresses

These fields contain the sender's and receiver's IP addresses. They are like the return and destination addresses on a letter, guiding the packet to its destination.

Source and Destination addresses direct the packet's path.

Options and Padding

These optional fields can carry extra control information or fill space to align the header size. They are not always used but provide flexibility for special needs.

Options and Padding add extra control or alignment when necessary.

Data (Payload)

This is the actual information being sent, such as part of a web page or an email. The header fields help deliver this data safely to the right place.

Data is the main content carried inside the IP packet.

Real World Analogy

Imagine sending a package through a courier service. The package has a label with the sender's address, recipient's address, instructions on how to handle it, and a tracking number. Sometimes, if the package is too big, it is split into smaller boxes with matching labels to be reassembled later.

Version → The courier service type or system version used for delivery

Header Length → The size of the label on the package

Total Length → The total size of the package including the label and contents

Identification, Flags, and Fragment Offset → Tracking numbers and instructions for splitting and reassembling large packages

Time to Live (TTL) → The expiration date or maximum delivery attempts before returning the package

Protocol → The type of contents inside the package, like documents or electronics

Header Checksum → Quality check on the label to ensure it is readable and correct

Source and Destination IP Addresses → Sender's and recipient's addresses on the package

Options and Padding → Special instructions or extra padding inside the package

Data (Payload) → The actual items inside the package being sent

Diagram

Diagram

┌───────────────┬───────────────┬───────────────┐
│ Version (4b)  │ Header Length  │ Type of Service│
├───────────────┼───────────────┼───────────────┤
│ Total Length (16b)                        │
├─────────────────────────────────────────┤
│ Identification (16b)                     │
├───────┬─────────┬─────────────────────────┤
│ Flags │ Fragment Offset (13b)              │
├─────────────────────────────────────────┤
│ Time to Live (8b) │ Protocol (8b)           │
├─────────────────────────────────────────┤
│ Header Checksum (16b)                    │
├─────────────────────────────────────────┤
│ Source IP Address (32b)                   │
├─────────────────────────────────────────┤
│ Destination IP Address (32b)              │
├─────────────────────────────────────────┤
│ Options (variable) + Padding              │
├─────────────────────────────────────────┤
│ Data (variable)                           │
└─────────────────────────────────────────┘

This diagram shows the layout of an IP packet header and its main fields from top to bottom.

Key Facts

Version → Indicates the IP protocol version used, such as IPv4 or IPv6.

Total Length → Specifies the entire size of the IP packet including header and data.

Time to Live (TTL) → Limits the packet's lifetime to prevent infinite circulation.

Protocol → Identifies the protocol of the encapsulated data, like TCP or UDP.

Source IP Address → The IP address of the sender of the packet.

Destination IP Address → The IP address of the intended recipient of the packet.

Common Confusions

Believing the IP packet contains the entire message or file being sent.

Believing the IP packet contains the entire message or file being sent. An IP packet carries only a small piece of data called a payload; large messages are split across many packets.

Thinking the Time to Live (TTL) is about actual time in seconds.

Thinking the Time to Live (TTL) is about actual time in seconds. TTL counts the number of hops (routers) a packet can pass through, not real time.

Assuming the header length is always fixed.

Assuming the header length is always fixed. The header length can vary due to optional fields, so devices must read this field to find where data starts.

Summary

An IP packet is like a special envelope that carries data across networks with important information to guide it safely.

The header contains fields that control routing, fragmentation, and error checking to ensure data arrives correctly.

Understanding each field helps grasp how computers communicate reliably over the internet.

Practice

1. Which part of an IP packet contains the source and destination addresses?

easy

A. Payload

B. Trailer

C. Header

D. Checksum

Solution

1. Step 1: Understand IP packet parts

   An IP packet mainly has two parts: the header and the payload (data).

2. Step 2: Identify address location

   The header contains control information including source and destination IP addresses.

3. Final Answer:

   Header -> Option C

4. Quick Check:

   Addresses are in the header [OK]

Hint: Remember: addresses are always in the header [OK]

Common Mistakes:

• Confusing payload with header
• Thinking addresses are in the trailer
• Assuming checksum holds addresses

2. Which field in the IP packet header specifies the version of the IP protocol?

easy

A. Protocol

B. Time to Live (TTL)

C. Header Checksum

D. Version

Solution

1. Step 1: Recall IP header fields

   The IP header includes fields like Version, TTL, Protocol, and Checksum.

2. Step 2: Identify version field

   The Version field specifically indicates whether the packet uses IPv4 or IPv6.

3. Final Answer:

   Version -> Option D

4. Quick Check:

   Version field shows IP protocol version [OK]

Hint: Version field always shows IPv4 or IPv6 [OK]

Common Mistakes:

• Confusing TTL with version
• Thinking checksum holds version info
• Mixing Protocol field with version

3. Given an IP packet with TTL set to 1, what happens when it reaches a router?

medium

A. The packet is dropped and an error message is sent back

B. The packet is delivered to the destination immediately

C. The packet's TTL is reset to 64

D. The packet is forwarded to the next router

Solution

1. Step 1: Understand TTL purpose

   TTL (Time to Live) limits how many routers a packet can pass through to avoid endless loops.

2. Step 2: Analyze TTL=1 at router

   When TTL reaches 0 after decrement, the router drops the packet and sends an error (ICMP Time Exceeded) back.

3. Final Answer:

   The packet is dropped and an error message is sent back -> Option A

4. Quick Check:

   TTL 1 means drop and notify [OK]

Hint: TTL zero means drop packet and send error [OK]

Common Mistakes:

• Assuming packet is forwarded with TTL 1
• Thinking TTL resets automatically
• Believing packet reaches destination immediately

4. A network engineer notices packets are not reaching the destination. Which IP header field should they check first to debug routing issues?

medium

A. Time to Live (TTL)

B. Identification

C. Source Address

D. Header Length

Solution

1. Step 1: Identify fields related to routing

   TTL controls packet lifespan; if too low, packets get dropped before reaching destination.

2. Step 2: Check TTL for routing problems

   Low or zero TTL causes packets to be discarded, causing delivery failure.

3. Final Answer:

   Time to Live (TTL) -> Option A

4. Quick Check:

   TTL affects packet routing success [OK]

Hint: Check TTL first when packets fail to route [OK]

Common Mistakes:

• Checking Identification instead of TTL
• Assuming Source Address causes routing failure
• Ignoring TTL impact on packet delivery

5. You want to create a custom IP packet for testing that includes a header with a specific Protocol field value indicating TCP. Which Protocol number should you set in the IP header?

hard

A. 1

B. 6

C. 17

D. 255

Solution

1. Step 1: Recall common IP Protocol numbers

   Protocol field indicates the next layer protocol: 1=ICMP, 6=TCP, 17=UDP, 255=Reserved.

2. Step 2: Identify TCP protocol number

   TCP is assigned protocol number 6 in the IP header.

3. Final Answer:

   6 -> Option B

4. Quick Check:

   TCP protocol number is 6 [OK]

Hint: TCP protocol number is 6 in IP header [OK]

Common Mistakes:

• Confusing UDP (17) with TCP
• Using ICMP (1) instead of TCP
• Choosing reserved number 255