|

[ACSA Training #7] IPv4 Header

⏱️ Estimated reading time: Approx. 2 minutes (2 min read)
Mitigates L3 route loops Version 10.1.1.1 Host A Indicates IJLP Type of Service Identification Protocol Flags - TCP or UDP Total Length Fragment Offset Checksum Source IP Address Destination IP Address Options R2 10.2.2.2 Host B
IPv4 header

The figure shows the IPv4 header information added to a packet at Layer 3. The important fields in the header are:.

  • TTL (Time To Live): This field indicates the expiration date of data, a method to prevent infinite packet looping at Layer 3. If a router is incorrectly configured, IP packets can be looped between two or more routers. To prevent this, a number between 0 and 255 is placed in this field.
    For example, if the TTL value is 15, each router that passes this packet will decrease the value of this field by 1. That is, after this packet passes through the first router, TTL=14, and after passing through the next router, TTL=13. When the TTL field becomes 0, the router discards the packet.
  •  Protocol: This field indicates whether the IP packet carries TCP or UDP traffic. When application data is passed to the lower layer, a header is added, depending on whether it's TCP or UDP, and then it's passed back to IP. From an IP perspective, TCP, UDP, and other protocols are at the upper OSI layer, so they are also called ULPs (Upper Layer Protocols).
  • Source/Destination IP Address: The sender of this IP packet adds an IP address to the Source IP Address field. The final destination for the packet is added to the Destination IP field. In the diagram, the source IP address is 10.1.1.1 for Host A, and the destination IP address is 10.2.2.2 for Host B.

The remaining fields are values used by the Layer 3 router to perform its operations.
It receives inbound packets, analyzes the destination IP address, and forwards the packets on the best route to the destination.
I will explain the details later when I have the chance.

Next, let's learn about TCP/UDP headers.

Similar Posts

  • [ACSA Education #28] MSTP Theory and Regional Structure

    ⏱️ Estimated read time: Approx. 6 minutes (6 min read) A Common Spanning Tree (CST) defines a single Spanning Tree Instance for the entire network, regardless of the number of VLANs. All BPDUs use Untagged VLAN 1, so VLAN details are not considered. Additionally, there is no load balancing, so alternative…

  • [ACSA Training #33] Routing

    ⏱️ Estimated read time: Approx. 10 minutes (10 min read) Since a switch is a Layer 2 device, its ports can only execute Layer 2 functions and protocols, such as becoming a member of each VLAN (member port) or transmitting frames. When an endpoint terminal is connected to a port used as a Layer 2 interface, based on the destination Layer 2 MAC address…

  • [ACSA Training #35] Routing Types

    ⏱️ Estimated reading time: Approx. 7 minutes (7 min read) We already covered routing in the last post. We examined how actual packets move at Layer 3 along with IP routing tables. Now, let's take a look at the actual types of routing and the protocols involved. Types of routing in AOS-CX Routing devices IP routing…

  • [APSC Training #5] Aruba Central Subscription Management

    ⏱️ Estimated reading time: Approx. 3 minutes (3 min read) In the previous post, we looked at adding Aruba devices to the cloud. Now, to actually operate them, we need to map subscription licenses to the devices. Let's take a look at subscription assignment and key management. HPE GreenLake Device Assignment HPE GreenLake is HPE's common…

  • [ACP-DC Training #3] Data Center Technology

    ⏱️ Estimated reading time: Approx. 14 minutes (14 min read) Last time, we discussed the robust hardware products of data centers. While physical equipment such as servers, storage, and switches are important, what truly makes a data center 'smart' is likely the various technologies running on top of this hardware. Simply put, data center technology refers to the various… configured on switches

  • [ACSA Training #2] OSI 7 Layers

    ⏱️ Estimated reading time: Approx. 7 minutes (7 min read) As computers rapidly advanced in the mid-1980s, all manufacturers attempted to implement their own proprietary communication protocols. As a result, compatibility issues arose between products from different manufacturers, leading to unreliable communication. Therefore, the International Organization for Standardization (ISO) [established] standard communication for computing devices…