One of the most common questions is how much overhead do I need to account for on my transport network? I have put together a quick list to help when you are calculating your overhead.<\/p>\n
-GRE (IP Protocol 47) (RFC 2784): 24 bytes (20 byte IPv4 header, 4 byte GRE header)
\n-6in4 encapsulation (IP Protocol 41, RFC 4213): 20 bytes
\n-4in6 encapsulation (e.g. DS-Lite RFC 6333): 40 bytes
\n Addition IPv4 header:20 bytes
\n-IPsec encryption:
\n 73 bytes for ESP-AES-256 and ESP-SHA-HMAC overhead (overhead depends on transport or tunnel mode and the encryption\/authentication algorithm and HMAC)
\n-MPLS: 4 bytes for each label in the stack
\n-802.1Q tag: 4 bytes
\n Q-in-Q: 8 bytes
\n-VXLAN: 50 bytes
\n-OTV: 42 bytes<\/p>\n
Some rules of thumb when setting MTUs. You won’t get fragmentation if your L2 MTU is higher than your L3 MTU. This is just not the setting, but the actual overhead in use. Just setting it to a number doesn’t necessarily make it right. The above list will help you calculate the minimum MTU you may need. I try to get gear that supports a 1548 MTU and set everything to that. Makes it simple. I still want to know how much MTU I am utilizing because it helps me validate my designs.
\nThe most important rule of thumb is you won’t get fragmentation if your l3 MTU is less than your L2 MTU. <\/p>\n","protected":false},"excerpt":{"rendered":"
One of the most common questions is how much overhead do I need to account for on my transport network? I have put together a quick list to help when you are calculating your overhead. -GRE (IP Protocol 47) (RFC 2784): 24 bytes (20 byte IPv4 header, 4 byte GRE header) -6in4 encapsulation (IP Protocol […]<\/p>\n","protected":false},"author":1,"featured_media":1501,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","jetpack_publicize_message":"","jetpack_is_tweetstorm":false,"jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":true,"jetpack_social_options":{"image_generator_settings":{"template":"highway","enabled":false}}},"categories":[17],"tags":[369,414,412,413,205,411,415,416],"jetpack_publicize_connections":[],"aioseo_notices":[],"jetpack_featured_media_url":"https:\/\/i0.wp.com\/www.mtin.net\/blog\/wp-content\/uploads\/2017\/01\/ethernet.jpeg?fit=1800%2C1162&ssl=1","jetpack_sharing_enabled":true,"jetpack_shortlink":"https:\/\/wp.me\/p6VLMf-ob","jetpack-related-posts":[{"id":2584,"url":"https:\/\/www.mtin.net\/blog\/tech-tip-determining-mtu-via-macosx-ping-oh-yeah-and-windows\/","url_meta":{"origin":1499,"position":0},"title":"Tech Tip: Determining MTU via MacOSX Ping oh yeah and Windows","author":"j2sw","date":"November 9, 2018","format":false,"excerpt":"The command: ping -D -s\u00a01472 What the command does ping = Obvious -D = Don't fragment -s