cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1869
Views
10
Helpful
3
Replies

Packet Fragmentation questions

Craddockc
Level 3
Level 3

Dear Community,

I am currently studying for the CCNP-ROUTE exam in an attempt to pass it before the February 2020 deadline. I am currently studying section 1.3b that has to do with IPv4 and IPv6 fragmentation and I had a couple of questions:

1) When the originating host decides that it needs to fragment the IPv4 packet, how does the host itself know that a downstream MTU is smaller than some of the packet sizes and that the packets need to be fragmented. 

2) If an IPv4 packet that is not fragmented needs to be fragmented in transit, or is fragmented already and needs to be fragmented again, can an intermediate router in the path perform the fragmentation? if so, under what circumstances would this occur?

 

I know these questions may be a little "in the weeds" for the exam but I always try to be as prepared as possible. I appreciate any feedback you can provide regarding the fragmentation process of IPv4.

 

Thanks!

1 Accepted Solution

Accepted Solutions

Joseph W. Doherty
Hall of Fame
Hall of Fame

#1 It would send its IP packets out with the don't-fragment bit set. If, along the path, some IP hop cannot forward the MTU received, i.e. it needs to fragment, it wouldn't fragment (because of the bit setting) but instead send a IGMP message to the source IP noting fragmentation is needed (later versions will include in the message how large the MTU can be).

When the sender receives this message, it normally decrease the MTU to fit (for the destination), it doesn't generally send/generate fragments.

If there's no don't-fragment bit, the transit router will fragment the IP packet and the sending host "doesn't know".

#2 Yes. It's just like the first instance. If don't-fragment isn't set, the already too large fragmented packet will be fragmented again. If the don't-fragment is set, to get to the next smaller transit hop, the packet would not have a larger MTU then all the upstream hops support. (I.e. an earlier too large packet might have already caused the source to reduce its MTU.)

For example the source send 1500 bytes with DF set. Along the way a hop can only handle 1000, so the source re-sends the data using 1000 byte packets, still with DF set. Then further along he path another hop can only handle 750 bytes. So, again, the source re-sends the data using 750 bytes.

View solution in original post

3 Replies 3

kubn2
Level 1
Level 1
Hi,

1) Sending host usually sending MTU with the size of the local link so if host is connected to router and on this link MTU is 1500 host will use this value. But also host can run MTU discovery algorithm to determinate the path MTU between him and destination host.

2) Yes, intermediate router can perform fragmentation of already fragmented packets. This occur when for example router from one link with MTU 1500 recives packets with size of 1500 then based on his routing table router need to forward packet on other link and this link use smaller MTU than 1500 so it can be 1000 so router will perform fragmentation to make packets to be a size of 1000 and will forward these smaller packets over link with this 1000 MTU setting.

Joseph W. Doherty
Hall of Fame
Hall of Fame

#1 It would send its IP packets out with the don't-fragment bit set. If, along the path, some IP hop cannot forward the MTU received, i.e. it needs to fragment, it wouldn't fragment (because of the bit setting) but instead send a IGMP message to the source IP noting fragmentation is needed (later versions will include in the message how large the MTU can be).

When the sender receives this message, it normally decrease the MTU to fit (for the destination), it doesn't generally send/generate fragments.

If there's no don't-fragment bit, the transit router will fragment the IP packet and the sending host "doesn't know".

#2 Yes. It's just like the first instance. If don't-fragment isn't set, the already too large fragmented packet will be fragmented again. If the don't-fragment is set, to get to the next smaller transit hop, the packet would not have a larger MTU then all the upstream hops support. (I.e. an earlier too large packet might have already caused the source to reduce its MTU.)

For example the source send 1500 bytes with DF set. Along the way a hop can only handle 1000, so the source re-sends the data using 1000 byte packets, still with DF set. Then further along he path another hop can only handle 750 bytes. So, again, the source re-sends the data using 750 bytes.

Craddockc
Level 3
Level 3
Thank you both very much for your responses! They are very helpful!
Review Cisco Networking for a $25 gift card