logo
logo
AI Products 

What is an IP Fragmentation?

avatar
Nilesh Parashar
What is an IP Fragmentation?

When a host sends an IP packet to a network, it must not exceed the maximum size supported by that local network. This size is determined by the network data link and the maximum IP transmission units (MTUs), which are usually the same. Today's typical network of offices, campuses, or data centers provided by Ethernet is 1,500 MTU bytes.


However, packets that are first sent to a network that supports MTUs may need to be forwarded to networks (such as a WAN tunnel or VPN) with a small MTU. In these cases, if the packet size is larger than the lower MTU, the packet data should be split (if possible). That is, the information is split into chunks that are transmitted within new packets (fragments) that are equal to or less than the lower MTU. This is called fragmentation, and the data in these fragments are often reconstituted when they reach their goal.


The first fragment has only high-layer headers, which can cause problems with firewalls, middleboxes, and routers (that is, NAT) that rely on header checking. Splitting may result in out-of-order delivery of the package and the need to reorder (especially if only a few packages are split or if link aggregation or other pad splitting technologies are used). A cyber security course will give you more insights into this topic.

 

Fragmentation and rearrangement processes involve several IP header fields located in fragments. Here is a reminder of all the fields and their order, marked by fragmentation headers. The Fragmentation operation relies on three IP header fields (a total of 32 bits), all of which have very different fragment values ​​compared to the original package.


The Identification field (16 bits) is populated with an identification number unique to the combination of source and destination addresses and the values ​​of the Protocol field in the original packet, which allows the destination to identify itself between different fragments. packet (from the same source). This does not mean that the same ID should be used when sharing packets with the same source, destination, algorithms and protocol, but the same ID will be used differently. To make this very clear, three packets are sent from host A to host B and each must be divided into parts:


  • The four fragments in the first packet will share the same value in the Identification field
  • The four fragments in the second packet will share the same identification field value, which differs from the value used by the fragments created from the first packet
  • The four fragments in the third packet will share the same amount in the Identification field, which differs from the amount used by the fragments created from the first and second packets

 

These subject field values ​​also change because they are common to each jump or as a subdivision product:


The Total Length (16 bits) field changes based on a reduction in the fragment data size (plus the IP header) equal to or less than the MTU. Since the fragment field, which should be more than 8 a piece of the following fragments that are not as often as MTU. Note IPv4 Displays this field's overall package size, including numbers. The Check Message field (16 bits) is cited based on the value of all header fields.

 

The cyber security salary in India could go up to INR 6 lakhs.

 

FIRST FRAGMENT

  • Area of ​​recognition inhabited by identification number
  • The dedicated hose is not set, flag is not set and large fragmented flag in the flags, in binary or: 001
  • Fragment of offset field is set to zero because it is the first fragment, expressed in binary as 0 0000 0000 0000
  • The total length of 572 height, which is stated in binary as 0000 0010 0011 1100; Maximum byte Package 576 is not used as fragment offset field The following particles should be in 852 bytes with data, with 868 bytes left


SECOND FRAGMENT

  • The area of ​​recognition inhabited by the same identification number used for the first particle
  • The dedicated hose is not set, flag is not set and large fragmented flag in the flags, in binary or: 001
  • The total length of 572 height, which is stated in binary as 0000 0010 0011 1100; This package also has 552 bait data, with the remaining 316 bytes

 

 

THIRD AND LAST FRAGMENT

  • Introductory field inhabiting the same identification number used for the first and second fragments
  • The dedicated snake is not set, the flag is not set and fragmented flag 0 in the flags, in binary or: 000
  • Fragment offset feel set to 138 (1104/8), declared in binary as 0 0000 1000 1010
  • The total length 336 of the length proposed binary as 0001 0101 0000; This package contains 316 data bytes

 

Many cyber security certifications from reputed institutes are added assets to your resume.

collect
0
avatar
Nilesh Parashar
guide
Zupyak is the world’s largest content marketing community, with over 400 000 members and 3 million articles. Explore and get your content discovered.
Read more