06-19-2012 04:10 AM - edited 03-07-2019 07:19 AM
this might sound like a dumb question
R1 (1500) <-> (1400) R2 (1400)<->(1500) R3
with the above setup if R3 sends a ping packet to R1 with a packet size of 1500 and df-bit set, Will it be dropped by R2 at the ingress interface or at the egress interface towards to R1.
MTU meaning Maximum "Transimission" Unit I am assuming that the ping will be dropped at egress interface of R2 towards to R1, but am not 100 % sure about this
06-19-2012 04:52 AM
Hello Vikram,
in your scenario the packet would be discarded at the ingress interface of R2, as it would be too big to be treated/received.
A packet too big is classified as an input error of type giant on a LAN interface and these counters are shown in show interface output.
MTU value should match at both ends of a single link.
Hope to help
Giuseppe
06-19-2012 06:24 AM
Please allow me to join this thread since I too had the same questions :
What would happen if we DF bit it not set?
Typically on a larger network it is practically impossible to know the MTU size of each of the router in the path? so how do we make the communication possible ? or is it mandatory to know the MTU size of all the interfaces on a flow from src to dstn?
Please advice.
Thanks
-Vijay
06-19-2012 06:43 AM
Hello Vijay,
in the scenario described by the original poster with both R2 interfaces MTU set to 1400, the DF bit settings on the received packet has no influence on the packet fate: it will be discarded and giant input error counter is incremented by 1.
The 1500 byte IP packet would be simply too big to be processed. If the ingress interface has MTU 1500 in that case the DF settings play a role allowing packet fragmentation if not set.
There are some mechanisms like path mtu discovery that allow to discover the MTU on the path from source to destination.
This path MTU discovery is not always possible and it has to be supported by endpoints
see
http://www.cisco.com/en/US/docs/ios/12_1/iproute/configuration/guide/1cdip.html#wp1001001
The general trend is to avoid fragmentation as much as possible:
on service provider network we see high MTU values on backbone and edge links to accomodate all possible services, Values as high as more then 9000 bytes are becoming common.
On VPN services built on internet access the trend is to use a reduced MTU to avoid fragmentation to take in account all the overhead
in these cases from 8 bytes overhead of PPPoE ( requires IP mtu 1492) to IP MTU values as low as 1300 bytes for some IPSEC+GRE scenarios
Hope to help
Giuseppe
06-19-2012 06:55 AM
Thanks Giuseppe.. that clears my doubt...
-Vijay
06-19-2012 06:45 AM
HI Vikram,
I am totaly agree with Giuseppe.
MTU problems may result in degraded network service, but may not affect some users' abilities to access the required applications, so sometimes MTU problems go unreported. Other times, MTU problems cause severe lags in network logon times, and cause to stop functioning entirely.
The MTU must be set to the same setting on all your router interface.
if not same then ......still it will work but ..later on you will face the problems.
Regards
Please rate if it helps.
06-19-2012 06:58 AM
Hi Vijay,
1.What would happen if we DF bit it not set?
If a packet is received which has the Don't Fragment (DF) bit set in the packet header, the packet is not fragmented, but instead discarded and if DF is not set then it Fragmented the packet according to the interface MTU size of the next router.
2.I also do not know much about,how to find the MTU of the all router in network because it differs according to the diff routers models. .
1500 | The biggest-sized IP packet that can normally traverse the Internet without getting fragmented. Typical MTU for non-PPPoE, non-VPN connections. |
1492 | The maximum MTU recommended for Internet PPPoE implementations. |
1472 | The maximum ping data payload before fragmentation errors are received on non-PPPoE, non-VPN connections. |
1460 | TCP Data size (MSS) when MTU is 1500 and not using PPPoE. |
1464 | The maximum ping data payload before fragmentation errors are received when using a PPPoE-connected machine. |
1452 | TCP Data size (MSS) when MTU is 1492 and using PPPoE. |
576 | Typically recommended as the MTU for dial-up type applications, leaving 536 bytes of TCP data. |
48 | The sum of IP, TCP and PPPoE headers. |
The sum of IP and TCP headers. | |
28 | The sum of IP and ICMP headers. |
Regards
Please rate if it helps
12-07-2019 05:30 PM
What happens when a frame or packet is larger in size than the MTU value of the interface?
It depends on whether the interface is switched (layer 2) or routed (layer 3), and, in the case of a routed interface, whether the IPv4 packet carried by the Ethernet frame has the Don’t Fragment (DF) bit set or not.
If the interface is layer 2, it will switch frames smaller or equal to its MTU value and it will silently discard larger ones.
If the interface is layer 3, it will forward packets whose size is within the IP MTU value, it will fragment packets larger than the MTU size and with the DF unset, and it will drop IP packets that have the DF bit set. Packets dropped will be signaled to the sender via the ICMP Fragmentation Required message (Type 3, Code 4).
Correct me if I am wrong.
12-08-2019 08:54 AM
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide