# Maximum Transmission Unit

Maximum Transmission Unit (MTU) is the largest network-layer packet, measured in bytes, that a link or interface can carry without fragmentation.

Cloud concept. Updated 2026-10-29. Page: https://blowstack.com/tools/cloud-concepts-hub/maximum-transmission-unit

> MTU determines how much data can travel in each packet and whether that packet fits across every segment of a network path. Correct MTU sizing improves transmission efficiency, while mismatches can cause fragmentation, packet loss, or connections that establish successfully but stall during data transfer.

Practice exams covering Maximum Transmission Unit: [ANS-C01 AWS Certified Advanced Networking - Specialty](https://blowstack.com/practice-exams/aws-certified-advanced-networking-specialty).

## 6 key aspects of Maximum Transmission Unit

Reliable MTU design aligns packet sizes with every segment of the path while balancing jumbo-frame efficiency against encapsulation, discovery behavior, and failover constraints.

1. **Interface MTU and path MTU**: An interface MTU is a local limit; the path MTU reflects the smallest effective limit along a route. Size traffic for the actual destination path, including alternate routes and tunnel overhead.
2. **Packet size versus Ethernet frame size**: IP MTU excludes Ethernet headers, VLAN tags, and the frame check sequence. Confirm what each device's frame-size setting includes before comparing values across routers, switches, and hosts.
3. **Jumbo-frame efficiency**: Larger packets can reduce per-packet overhead and processing load during bulk transfers. Enable them only on compatible paths and benchmark throughput, CPU utilization, and latency rather than assuming improvement.
4. **Fragmentation and discovery**: IPv4 fragmentation depends on the Don't Fragment flag, while IPv6 routers never fragment forwarded packets. Permit the necessary ICMP feedback where supported so senders can discover smaller path limits.
5. **Encapsulation and connection-specific limits**: VPNs and overlays consume space with additional headers, reducing the packet size available to applications. Dedicated links, transit connections, and encrypted tunnels can have different limits even when they connect the same networks.
6. **Mismatch diagnosis and remediation**: Successful handshakes followed by stalled transfers are a common MTU black-hole symptom. Use size-controlled probes and packet captures, then correct MTU settings, discovery filtering, or TCP MSS as appropriate.

## Cloud services for Maximum Transmission Unit

EC2 interface settings establish the host's packet-size ceiling, while VPC routing selects the path those packets follow. Direct Connect can provide jumbo-capable private connectivity, but a transit virtual interface and Transit Gateway introduce an 8500-byte ceiling. Site-to-Site VPN imposes a much smaller limit and needs explicit consideration when used as a backup route. Coordinate host MTUs, customer-router settings, virtual-interface configuration, security filtering, and TCP MSS where needed. Test large transfers in both directions during normal operation and failover rather than validating only small connectivity probes.

- **[AWS Direct Connect](https://blowstack.com/tools/cloud-services-hub/aws-direct-connect)**: Direct Connect supports MTUs of 9001 bytes on private virtual interfaces, 8500 bytes on transit virtual interfaces, and 1500 bytes on public virtual interfaces. Jumbo-frame use requires compatible customer equipment and the appropriate connection and virtual-interface configuration; membership in a LAG does not increase MTU.
- **[Amazon EC2](https://blowstack.com/tools/cloud-services-hub/amazon-ec2)**: Supported EC2 instance network interfaces can use a 9001-byte MTU for jumbo traffic on compatible paths. Check the operating-system interface setting and the full route, because the instance's configured MTU does not establish the destination's path MTU.
- **[AWS Transit Gateway](https://blowstack.com/tools/cloud-services-hub/aws-transit-gateway)**: Transit Gateway supports an MTU of 8500 bytes on supported non-VPN attachment paths, including VPC and Direct Connect attachment paths. Traffic originating on a 9001-byte interface must accommodate this smaller limit, and VPN attachments remain subject to VPN-specific limits.
- **[AWS Site-to-Site VPN](https://blowstack.com/tools/cloud-services-hub/aws-site-to-site-vpn)**: Site-to-Site VPN does not support jumbo frames and has a maximum MTU of 1446 bytes, with lower effective limits possible depending on encryption and encapsulation. It does not support Path MTU Discovery, making deliberate tunnel MTU and TCP MSS configuration especially important.
- **[Amazon VPC](https://blowstack.com/tools/cloud-services-hub/amazon-vpc)**: VPC routing determines whether traffic remains on a jumbo-capable path or traverses a connection with a smaller MTU. Security groups and network ACLs must allow the required ICMP error messages for discovery where supported; VPC Flow Logs can support traffic diagnosis but do not replace packet captures for packet-size analysis.

## Maximum Transmission Unit exam questions

Real practice exam questions on Maximum Transmission Unit, with the correct answer and its explanation.

### Question 1 (ANS-C01)

**Question:**

A company is enabling jumbo frames for bulk replication between Linux-based Amazon EC2 instances in two subnets of the same VPC. The instances communicate directly through the VPC local route, support a 9,001-byte IP MTU, and currently use a 1,500-byte MTU. No tunnels or network appliances are in the path.

An engineer proposes using guest packet captures to validate the change. However, TCP segmentation offload and receive offload are enabled, and the captures already show TCP packets larger than 9,001 bytes. The company requires an acceptance test that demonstrates that a 9,001-byte IPv4 packet can traverse the path in either direction without fragmentation. Security controls permit ICMP, and the tests will use standard 20-byte IPv4 headers and 8-byte ICMP headers.

Which implementation and acceptance test meet these requirements?

**Correct answer:** Persistently configure both instance interfaces with an MTU of 9,001 bytes. Run ping -4 -M do -s 8973 from each instance to the other instance's private IPv4 address and require successful replies.

**Explanation:** The 8,973-byte ICMP payload plus the 20-byte IPv4 header and 8-byte ICMP header produces a 9,001-byte IP packet. Linux ping's -M do setting prohibits fragmentation. Testing in both directions validates jumbo-packet delivery independently of misleading TCP offload captures.

## Practice Maximum Transmission Unit in a full exam

Questions on Maximum Transmission Unit in each practice exam, with every answer option and an explanation for each:

- [ANS-C01](https://blowstack.com/practice-exams/aws-certified-advanced-networking-specialty): 12 questions

## What is Maximum Transmission Unit

Maximum Transmission Unit describes a packet-size limit, not a bandwidth limit. On an Ethernet interface, an IP MTU of 1500 bytes normally allows an IP packet containing its IP header and transport-layer data to occupy up to 1500 bytes. Ethernet headers and the frame check sequence are additional: a standard untagged Ethernet frame carrying that packet is 1518 bytes, excluding the preamble and interpacket gap. This distinction matters because switch vendors may express maximum frame size differently from an operating system's IP MTU.

The path MTU is the smallest packet-size limit along the route, accounting for encapsulation where applicable. Configuring a server for a 9001-byte MTU does not make every destination reachable with 9001-byte packets. Virtual interfaces, routers, firewalls, transit networks, tunnels, and destination interfaces can impose smaller limits. Forward and return paths can also differ, so testing only one direction is insufficient.

Jumbo frames carry IP packets larger than the conventional 1500-byte Ethernet MTU. They can reduce packets per second, protocol overhead, and host processing costs for sustained transfers such as replication or storage traffic. However, they require compatible handling throughout the intended path. Larger frames take longer to serialize on a link and are not automatically beneficial for small messages or latency-sensitive workloads. Increasing MTU does not increase the physical link rate or guarantee lower cloud data-transfer charges.

For physical interconnects, verify the supported MTU on the customer router, switch ports, provider connection, and logical interfaces. An 802.1Q VLAN tag adds four bytes to the Ethernet frame; equipment must accommodate that overhead without unintentionally reducing the intended IP MTU. A link aggregation group increases aggregate capacity and can improve resilience, but it does not increase MTU or necessarily increase the throughput of one flow. Compatible optics and link speeds establish the physical connection; they do not prove jumbo-frame support.

Cloud paths frequently mix MTU limits. Supported Amazon EC2 interfaces can use a 9001-byte MTU. AWS Direct Connect supports 9001 bytes on private virtual interfaces and 8500 bytes on transit virtual interfaces, while public virtual interfaces use 1500 bytes. AWS Transit Gateway supports an MTU of 8500 bytes on supported non-VPN attachment paths. Consequently, a 9001-byte EC2 packet cannot cross a transit-gateway path unchanged. AWS Site-to-Site VPN does not support jumbo frames; its maximum MTU is 1446 bytes, and the usable value can be lower depending on the encryption algorithms and encapsulation. Always evaluate the actual route rather than assuming a dedicated connection makes every attached path jumbo-capable.

IPv4 routers can fragment oversized packets when fragmentation is permitted, but packets with the Don't Fragment flag set must instead be dropped and normally trigger an ICMP fragmentation-needed response. IPv6 routers do not fragment forwarded packets; they return ICMPv6 Packet Too Big messages so the sender can adjust. Path MTU Discovery relies on these signals. If a firewall, security group, or network ACL blocks the necessary messages, small requests can succeed while large responses repeatedly retransmit. Some network services also do not provide the feedback required for conventional Path MTU Discovery, so discovery cannot be assumed to work across every cloud path.

When troubleshooting, compare interface MTUs, map the route and its attachment types, and probe progressively larger packets. On Linux, an IPv4 command such as ping -M do -s 1472 DESTINATION tests a 1500-byte IP packet with ordinary 20-byte IPv4 and 8-byte ICMP headers. Failure alone does not prove an MTU mismatch because ICMP echo might be blocked. Correlate tests with packet captures, retransmissions, interface errors, and ICMP responses. Account for segmentation and receive offloads when interpreting captures, because host captures can display packets larger than the frames actually transmitted.

Restore connectivity by correcting an inconsistent link configuration, lowering the source or tunnel MTU, or allowing the required discovery messages where supported. TCP maximum segment size clamping can prevent oversized TCP segments across constrained paths, but it does not fix UDP or replace correct MTU design. Validate both the preferred route and failover routes: a jumbo-capable dedicated connection might fail over to a substantially smaller VPN path.
