A host sends a packet larger than the outgoing interface MTU, and the IPv4 header has the Don't Fragment bit set.
What will a router do with the packet?
A host sends a packet larger than the outgoing interface MTU, and the IPv4 header has the Don't Fragment bit set.
What will a router do with the packet?
Answer choices
Good practice is not just finding the correct option. The wrong answers often show the exact trap the exam wants you to fall into.
Fragment it anyway and forward the pieces
The router cannot simply ignore the Don't Fragment bit. That bit exists specifically to prevent fragmentation. If the router fragmented the packet anyway, it would violate the sender's requirement and defeat the whole point of the flag.
Drop it and typically return an ICMP message indicating fragmentation is needed
Correct. This is correct. When a packet is too large for the outgoing MTU and fragmentation is not allowed, the router drops the packet and usually informs the sender that fragmentation would be required.
Translate it to IPv6 and forward it
Routers do not solve an oversized IPv4 packet by converting it into IPv6. These are different protocols with different headers and forwarding behaviors. The issue here is MTU and fragmentation policy, not an opportunity for protocol conversion.
Broadcast it so another router can handle fragmentation
Routers do not broadcast oversized packets to let another router solve the problem. The forwarding decision is made locally. If the packet cannot be forwarded because of the MTU and DF setting, it is dropped.
Common exam trap
A common exam trap is to assume that routers will fragment any oversized IPv4 packet regardless of the Don't Fragment bit. Candidates might select the option that routers fragment the packet anyway, ignoring the DF bit. This is incorrect because the DF bit explicitly prevents fragmentation. Another tempting mistake is to think that routers might broadcast the packet to other routers or convert it to IPv6 to solve the problem, which does not happen. Understanding that the router must drop the packet and send an ICMP message is critical to avoid this trap.
Technical deep dive
IPv4 packets include a header flag called the Don't Fragment (DF) bit, which instructs routers along the path not to fragment the packet under any circumstances. Fragmentation is the process of breaking a large IP packet into smaller pieces so that each piece fits within the Maximum Transmission Unit (MTU) size of the outgoing interface. The MTU is the largest packet size that a network link can transmit without needing fragmentation. When a packet exceeds the MTU of the next hop, routers typically fragment the packet to ensure delivery. However, when the DF bit is set, routers are prohibited from fragmenting the packet. If the packet size exceeds the MTU of the outgoing interface, the router must drop the packet and send an ICMP Type 3 Code 4 message (Destination Unreachable, Fragmentation Needed and DF Set) back to the sender. This behavior is fundamental to Path MTU Discovery (PMTUD), a mechanism that allows the sender to learn the smallest MTU along the path and adjust packet sizes accordingly to avoid fragmentation. A common exam trap is to assume that routers will fragment packets regardless of the DF bit setting. This is incorrect because the DF bit explicitly forbids fragmentation. Another misconception is that routers might broadcast or convert the packet to IPv6 to solve the issue, which is not true. In practice, the router drops the packet and notifies the sender, prompting the sender to reduce packet size. This mechanism ensures efficient network operation and prevents fragmentation-related performance issues.
Related practice questions
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Practise IPv4 subnetting, CIDR, masks, host ranges and subnet selection.
Practise OSPF neighbours, router IDs, metrics, areas and routing-table interpretation.
Practise VLANs, access ports, trunks, allowed VLANs and switching scenarios.
Practise spanning tree, root bridge election, port roles and STP troubleshooting.
Practise LACP, PAgP, port-channel behaviour and bundle requirements.
Practise standard and extended ACLs, permit/deny logic and traffic filtering.
Practise static NAT, dynamic NAT, PAT and inside/outside address translation.
Practise DHCP scopes, relay, leases and troubleshooting.
Practise routing-table output, longest-prefix match, AD and route selection.
Practise trunk verification and VLAN forwarding across switches.
Practise WLAN security, authentication and wireless architecture concepts.
Practise IPv6 addressing, routes, neighbour discovery and common IPv6 exam traps.
Keep practising from the same exam bank, or move into a focused topic page if this question exposed a weak area.
Question 1
Question 2
Question 3
Question 4
Question 5
Question 6
FAQ
The Don't Fragment (DF) bit in the IPv4 header instructs routers not to fragment the packet under any circumstances.
The correct answer is: Drop it and typically return an ICMP message indicating fragmentation is needed — The router drops the packet because the packet is too large for the next link and the sender has explicitly said the packet must not be fragmented. In IPv4, the Don't Fragment bit tells routers not to break the packet into smaller pieces. If the outgoing interface MTU is smaller than the packet size, the router cannot legally forward it as-is and cannot fragment it, so the normal result is to drop the packet and usually send back an ICMP unreachable message indicating that fragmentation is needed. In plain terms, the router is telling the sender, 'This packet is too big for the path you chose, and you told me I am not allowed to split it.' This behavior is central to path MTU discovery.
Then try more questions from the same exam bank and focus on understanding why the wrong options are tempting.
Sign in to join the discussion.