标签：xxx network ping destination bytes value MTU supported

Environment

• Red Hat Enterprise Linux (All versions).

Issue

• How to test a particular MTU value is support ?
• How I can check if this MTU size is supported by each Network Card ?
• Is there any checklist to verify our environment is prepared for enable MTU change ?
• How to test the custom Jumbo Frames are supported ?

Resolution

• Testing the MTU is supported in the network.

Raw

# ping -M do -s 8972 [destination IP]

Note: there is an overhead of 28 bytes for the packet size. 8 bytes for ICMP headers and 20 bytes for Ethernet header, so the MTU is 28 bytes larger than the figure you establish through the method above. So to test for MTU of 9000, you actually need to set your ping packet size to 9000-28 = 8972.

• By adjusting the MTU value its possible to find the supported MTU value in the network.

• If the MTU value is not enables in the client side the ping output will be :

  Raw

  PING xxx.xxx.xxx.xxx (xxx.xxx.xxx.xxx): 8184 data bytes
  ping: sendto: Message too long
  

• If the MTU value is enabled in client but not in destination (or switch in between) the ping output will be :

  Raw

  PING xxx.xxx.xxx.xxx (xxx.xxx.xxx.xxx): 8184 data bytes
  Request timeout for icmp_seq 0
  

• If the MTU is supported and enabled in client and destination the ping output will be :

  Raw

  PING xxx.xxx.xxx.xxx (xxx.xxx.xxx.xxx): 8184 data bytes
  8192 bytes from xxx.xxx.xxx.xxx: icmp_seq=0 ttl=128 time=0.714 ms

标签：xxx,network,ping,destination,bytes,value,MTU,supported
来源： https://blog.csdn.net/weixin_39833509/article/details/120634509

本站声明： 1. iCode9 技术分享网（下文简称本站）提供的所有内容，仅供技术学习、探讨和分享；
2. 关于本站的所有留言、评论、转载及引用，纯属内容发起人的个人观点，与本站观点和立场无关；
3. 关于本站的所有言论和文字，纯属内容发起人的个人观点，与本站观点和立场无关；
4. 本站文章均是网友提供，不完全保证技术分享内容的完整性、准确性、时效性、风险性和版权归属；如您发现该文章侵犯了您的权益，可联系我们第一时间进行删除；
5. 本站为非盈利性的个人网站，所有内容不会用来进行牟利，也不会利用任何形式的广告来间接获益，纯粹是为了广大技术爱好者提供技术内容和技术思想的分享性交流网站。