- What is meant by IP fragmentation?
- Why is an IP datagram fragmented?
- Which RFCs discuss IP fragmentation?
- Is it possible to select an IP datagram size to always avoid fragmentation?
- Where an IP datagram may get fragmented?
- Where are the IP datagram fragments reassembled?
- How to prevent an IP datagram from being fragmented?
- What happens when a datagram must be fragmented to traverse a network, but the "don't fragment" flag in the datagram is set?
- Will all the fragments of a datagram reach the destination using the same path?
- Will all the fragments of a datagram arrive at the destination system in the correct order?
- What happens to the original IP datagram when one or more fragments are lost?
- What is the minimum size of an IP fragment?
- What are the limitations on the size of a fragment?
- The amount of remaining data in the original IP datagram
- The MTU of the network and
- Must be a multiple of 8, except for the final fragment.
- How is an IP datagram fragment differentiated from a non-fragmented IP datagram?
- How are the fragments of a single IP datagram identified?
- How is the last fragment of an IP datagram identified?
- How is the length of a complete IP datagram calculated from the received IP fragments?
- How is an IP datagram fragmented?
- The IP layer creates two new IP datagrams, whose length satisfies the requirements of the network in which the original datagram is going to be sent.
- The IP header from the original IP datagram is copied to the two new datagrams.
- The data in the original IP datagram is divided into two on an 8 byte boundary. The number of 8 byte blocks in the first portion is called Number of Fragment Blocks (NFB).
- The first portion of the data is placed in the first new IP datagram.
- The length field in the first new IP datagram is set to the length of the first datagram.
- The fragment offset field in the first IP datagram is set to the value of that field in the original datagram.
- The "more fragments" field in the first IP datagram is set to one.
- The second portion of the data is placed in the second new IP datagram.
- The length field in the second new IP datagram is set to the length of the second datagram.
- The "more fragments" field in the second IP datagram is set to the same value as the original IP datagram.
- The fragment offset field in the second IP datagram is set to the value of that field in the original datagram plus NFB.
- How a destination system reassembles the fragments of an IP datagram?
- When a host receives an IP fragment, it stores the fragment in a reassembly buffer based on its fragment offset field.
- Once all the fragments of the original IP datagram are received, the datagram is processed.
- Upon receiving the first fragment, a reassembly timer is started.
- If the reassembly timer expires before all the fragments are received, the datagram is discarded.
- What fields are changed in an IP header due to fragmentation?
- Total Length
- Header Length
- More Fragments Flag
- Fragment Offset
- Header Checksum
- Options
- What happens to the IP options field when an IP datagram is fragmented?
- Which IP options are copied to all the fragments of an IP datagram?
IP Fragmentation Q&A
by
January 11, 20066 minute read
0
Tags:
Your comments will be moderated before it can appear here.