Home > Articles > Cisco > CCNA Routing and Switching

Anatomy of an IPv4 Packet

One of the first subjects that a new networking student must learn is TCP/IP as it is used to connect together almost all modern devices. This article takes a look at the IPv4 packet, the fields that are defined within it and how they are used to transport the traffic from source to destination.
Like this article? We recommend

Like this article? We recommend

When beginning a career in computer networking, it is vital that the person entering the field is ready to learn and has a very open mind when it comes to new technologies and concepts. One of the first subjects that a new networking student must learn is TCP/IP, as it is used to connect together almost all modern devices. This article takes a look at the IPv4 packet, the fields that are defined within it and how they are used to transport the traffic from source to destination.

TCP/IP Version 4 Packet Structure

The TCP/IP Version 4 packet is composed of a number of different fields that can be used by the source and intermediary devices to determine the way a specific packet is treated when being transported. Figure 1 below shows the structure of the packet and the different fields that are contained within:

Figure 1 TCP/IP Version 4 Packet

As can be seen from the figure, there are a number of fields which have rather obvious names and some that do not. The following sections will explain the purpose of each of these fields and how they can be used to change forwarding behavior.

Version Field

The version field is one of the fields with a more obvious name and uses 4 bits. There are currently two versions of TCP/IP used in modern networks, Version 4 and Version 6. This article takes a look at the structure of the Version 4 header; when sending a Version 4 packet the value of the Version field will be 4 which is represented in binary as‘0100’.

Internet Header Length (IHL)

The IHL field is used to specify the total length of the header and is represented in 32 bit words. The minimum valid value for the IHL field is 5 (5 x 32 = 160 bits) which accounts for the Version, IHL, TOS, Length, Identification, Flags, Fragment Offset, TTL, Protocol, Checksum, and the Source and Destination Addresses, which are all mandatory.

Type of Service (TOS)/Differentiated Services Code Point (DSCP)[md]Explicit Congestion Notification (ECN)

When the Internet Protocol (IP) was initially designed this part of the packet header was called the Type of Service field that used 8 bits; this field was used to define a precedence value along with other quality of service (QoS) parameters for the packet. The modern implementation has changed from using this part of the packet from a single 8-bit TOS field to a 6-bit DSCP and 2-bit ECN fields. The DSCP field extends on the way that QoS is placed upon a specific packet; the specifics of the DSCP field could run the length of this entire article and is outside the scope of this article. The ECN field is used to provide end-to-end congestion notification between supporting ECN equipment.


Unlike the IHL field, the Length field is used to indicate the total length of the IP packet including the data. This field is represented in octets (also referenced as bytes or 8 bits) and is provided a total of 16 bits in the header.


The Identification field uses 16 bits and is uniquely set by the sender to help identify specific packets when they are being reassembled from fragments. If there is only one packet and it is not fragmented then it will be the only packet with that specific identification value. For fragmented packets, the value is the same across all of the fragments and is used by the destination device to reassemble the data.


The Flags field is used to control how a specific IP packet is treated by a device. The field is 3 bits and is formatted as follows:

  • The first bit is always set to 0
  • The second bit represents whether a packet is allowed to be fragmented (Don’t Fragment[md]DF) or split into multiple pieces.
    • A value of 0 means that the packet is allowed to be fragmented
    • A value of 1 means that the packet is NOT allowed to be fragmented
  • The third bit represents the ‘location’ of a packet in a series of fragmented packets
    • A value of 0 means that the packet is the last fragment in a series OR a packet that is not fragmented at all
    • A value of 1 means that the packet is not the last fragment in a series and more fragments should be expected

Fragment Offset

The Fragment Offset field uses 13 bits and is represented in units of 8 octets (or bytes). This field is used to indicate to the destination device where a received fragment should be placed when all of the data from the packet is being reassembled. The Fragment Offset, along with the Identification field, is used to identify packets that have been fragmented and reassemble them in the correct order. Packets that are not fragmented AND the first packet in a series of fragmented packets will always have a fragment offset set to 0.

Time to Live (TTL)

The TTL field is used to limit the amount of time that a packet is allowed to exist on the “network”. The field uses 8 bits and is represented in seconds. Each device that receives a packet is required to decrement the TTL value by at least 1 regardless of whether the processing took less than a second; any device that decrements the value of the TTL field to 0 is required to drop the packet. Since almost all packets are processed in less than a second it is common for the value of the TTL field to be interpreted as maximum hops; for example, if a packet has a TTL of 3 and each device is required to decrement the TTL by at least 1 then the maximum number of devices that can process the packet is 3 before the packet must be dropped.


The Protocol field uses 8 bits and indicates the next level protocol that is contained within the data portion of the packet. The most common values include the Transmission Control Protocol (TCP) with a value of 0x06 (hex) or 00000110 (binary), User Datagram Protocol (UDP) with a value of 0x11 (hex) or 00010001 (binary) and the Internet Control Message Protocol (ICMP) with a value of 0x01 (hex) or 00000001 (binary).


The Checksum field uses 16 bits and is computed for only the packet header. Checksum provides a method of verifying that the header has not been corrupted when being transmitted from one device to another. To explain its function without going into the math, a checksum value is derived from the contents of the header at the source and is recomputed at the destination; if these values do not match, the packet will be discarded. Because the contents of the TTL field change from device to device, the checksum is recomputed at each device and reset in the header.

Source and Destination Address

Both the Source and Destination Address fields are 32 bits and indicate the source and destination IP addresses, respectively.


The Options field is variable in length depending on the specific options that are being set; this field is optional. Most modern network traffic does not utilize the options field at all and because it is an optional field is not typically used.


The padding field is variable in length and is used when the Options field is used to ensure that the packet header ends at a 32 bit boundary.


The data field inside a packet is variable in length and can contain any number of different protocols as defined by the developer. Common network traffic uses the TCP, UDP and ICMP protocols which will be contained within this part of the packet.


The processing of traffic from source to destination can be very confusing for those entering into the networking field. While most traffic uses basic parameters (no QoS, fragmentation or Options) it is possible for traffic to utilize a number of different complex features. The purpose of this article is to make the reader familiar with the fields contained within the IP packet and give a general overview as to how they are used. Hopefully the content of this article can give the reader a starting point when learning about IP and how it is used.

Pearson IT Certification Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from Pearson IT Certification and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about Pearson IT Certification products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites; develop new products and services; conduct educational research; and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by Adobe Press. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.pearsonitcertification.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020