03-20-2013 10:09 PM - edited 03-07-2019 12:23 PM
G1/2 G1/1
PC1 ---------- R1 ------------------------------------------- R2 --------------- PC2
MTU = 600 bytes
All interfaces have default interface MTU with length 1500 bytes except R1’s interface G1/2.
PC1 pings PC2 using cli “ping 100.1.1.2 size 1000”. So PC1 is sending the packet with IP header 20 bytes, and data 1000 bytes.
R1 has to fragment the packet before sending out interface G1/2.
Q1: The fragmented data length should be 600 bytes (MTU value) – 20 bytes (IP header) = 580 bytes. But 580 is not the multiple of 8 bytes, so the final fragmented data length should be 576 bytes.
Q2: The original 980 bytes data is fragmented into 2 pieces: 576 bytes, and 424 bytes
Destination PC2 assembles the 2 fragments.
Q3: PC2 then sends ICMP reply also with 2 fragments whose data sizes are: 576 bytes, and 424 bytes. Because if PC2 does not fragment, R1 will drop the packet which is bigger than R1’s interface MTU.
thx,
Jingyi
Solved! Go to Solution.
03-21-2013 02:38 AM
Disclaimer
The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.
Liability Disclaimer
In no event shall Author be liable for any damages whatsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.
Posting
Q3: PC2 then sends ICMP reply also with 2 fragments whose data sizes are: 576 bytes, and 424 bytes. Because if PC2 does not fragment, R1 will drop the packet which is bigger than R1’s interface MTU.
As already noted by Jcarvaja, PC2 would not reflect the fragmentation unless its NIC wasn't 1500.
If the R1<>R2 link MTU is only 600, then R2 should fragment just like R1. However, if R1<>R2 is incorrectly configured, i.e. R1 believes MTU is 600 and R2 believes MTU is 1500, then R2 will send packets GT 600 to R1 which R1 will drop.
03-20-2013 11:09 PM
Hello,
Exactly but I would say on point 3 that the PC will not fragment it,
I mean it will reply based on it's on NIC settings and then R2 will fragment packets it need it ( It will as by default the MTU for the link between the PC2 and R2 is of 1500 bytes,
Do you follow me
Regards
03-21-2013 02:38 AM
Disclaimer
The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.
Liability Disclaimer
In no event shall Author be liable for any damages whatsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.
Posting
Q3: PC2 then sends ICMP reply also with 2 fragments whose data sizes are: 576 bytes, and 424 bytes. Because if PC2 does not fragment, R1 will drop the packet which is bigger than R1’s interface MTU.
As already noted by Jcarvaja, PC2 would not reflect the fragmentation unless its NIC wasn't 1500.
If the R1<>R2 link MTU is only 600, then R2 should fragment just like R1. However, if R1<>R2 is incorrectly configured, i.e. R1 believes MTU is 600 and R2 believes MTU is 1500, then R2 will send packets GT 600 to R1 which R1 will drop.
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: