# Path MTU Discovery

Path MTU Discovery determines the largest IP packet that can traverse a network path without fragmentation.

Cloud concept. Updated 2026-10-29. Page: https://blowstack.com/tools/cloud-concepts-hub/path-mtu-discovery

> The path maximum transmission unit is constrained by the smallest supported IP MTU along the route, including any tunnels and intermediate network devices. Discovering and respecting this limit prevents large-packet failures, while allowing workloads to use larger packets where the entire path supports them.

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

## 6 key aspects of Path MTU Discovery

Reliable packet sizing combines path-wide MTU compatibility, usable discovery feedback, encapsulation-aware configuration, and realistic traffic testing.

1. **End-to-end packet-size constraint**: The smallest usable MTU along a route determines its path MTU. A jumbo-capable instance or physical connection cannot compensate for a smaller tunnel or intermediate attachment.
2. **ICMP-based feedback**: Classic IPv4 discovery uses Don't Fragment packets and ICMP type 3, code 4 responses; IPv6 uses ICMPv6 Packet Too Big messages. Security controls must permit the relevant errors to reach the sender.
3. **Black-hole failure recognition**: Successful handshakes followed by stalled large transfers are a common symptom of oversized packets combined with missing feedback. Compare small and large probes before treating the issue as a general routing failure.
4. **Encapsulation-aware sizing**: VPNs and overlay tunnels add headers that reduce the available space for inner packets. Choose MTU and TCP MSS values for the actual encapsulation and encryption configuration.
5. **Validated jumbo-packet optimization**: Larger packets can reduce packet-processing work and improve bulk-transfer efficiency, but only across compatible paths. Test both traffic directions and failover routes before relying on jumbo support.
6. **Transport-specific mitigation**: TCP MSS clamping limits TCP segment size but does not protect UDP traffic. Packetization-layer discovery can provide an alternative to relying solely on ICMP when implemented by the transport or application.

## Cloud services for Path MTU Discovery

EC2 instances originate traffic and provide tools for testing packet sizes, while VPC security controls must allow relevant discovery feedback. Direct Connect can carry jumbo packets when its virtual interface and the complete path support them. Transit Gateway introduces attachment-specific limits, and Site-to-Site VPN requires explicit sizing because it does not support PMTUD. Engineers should map these limits from source to destination, account for encapsulation, and validate both directions. Repeat tests over backup routes: a VPN failover path may require smaller packets than the primary Direct Connect path.

- **[Amazon EC2](https://blowstack.com/tools/cloud-services-hub/amazon-ec2)**: EC2 instances provide endpoints where engineers configure interface MTUs and inspect operating-system PMTU behavior. Supported instance interfaces can use a 9001-byte MTU, but connectivity beyond the local path may require smaller packets.
- **[Amazon VPC](https://blowstack.com/tools/cloud-services-hub/amazon-vpc)**: VPC security groups and network ACLs participate in permitting or blocking the ICMP errors needed for discovery. VPC Flow Logs can help investigate filtering, but endpoint packet captures and size-controlled probes are needed to establish the usable packet-size boundary.
- **[AWS Direct Connect](https://blowstack.com/tools/cloud-services-hub/aws-direct-connect)**: Direct Connect supports different MTU limits by virtual interface type: 1500 for public virtual interfaces, up to 9001 for private virtual interfaces, and up to 8500 for transit virtual interfaces. Jumbo operation requires compatible connection capabilities, configuration, and the rest of the end-to-end path.
- **[AWS Site-to-Site VPN](https://blowstack.com/tools/cloud-services-hub/aws-site-to-site-vpn)**: Site-to-Site VPN does not support Path MTU Discovery and supports a maximum MTU of 1446 bytes, with lower effective limits possible depending on encryption settings. Configure suitable packet sizes and TCP MSS values, and test non-TCP traffic separately.
- **[AWS Transit Gateway](https://blowstack.com/tools/cloud-services-hub/aws-transit-gateway)**: Transit Gateway supports an MTU of 8500 bytes on supported attachment paths, while VPN connectivity has a smaller limit. Treat the gateway, its attachment types, and their PMTUD behavior as explicit constraints rather than assuming that an EC2 MTU of 9001 is usable across the transit path.

## Path MTU Discovery exam questions

Real practice exam questions on Path MTU Discovery, with the correct answer and its explanation.

### Question 1 (ANS-C01)

**Question:**

A company performs bulk TCP replication from Linux-based Amazon EC2 instances to an on-premises data center through an AWS Direct Connect private virtual interface. The normal path supports a 9,001-byte IP MTU end to end. During maintenance, an on-premises routing change temporarily directed traffic through a customer-managed path with a 1,500-byte MTU. The EC2 senders received the appropriate ICMP errors and continued transferring data using smaller packets.

The normal jumbo-capable path has now been restored. Replication still uses IP packets no larger than 1,500 bytes, and packet-processing overhead limits throughput. The EC2 interfaces and Direct Connect virtual interface remain configured for a 9,001-byte MTU. Inspection shows that the sending operating systems still have an unexpired 1,500-byte path-MTU entry for the replication destinations. Independent probes confirm that 9,001-byte IPv4 packets with Don't Fragment set now reach those destinations. CPU capacity apart from packet processing, storage, TCP windows, and available bandwidth are sufficient.

Which action will restore jumbo-packet efficiency most directly without changing packet sizes for unrelated destinations?

**Correct answer:** Use supported operating-system mechanisms to invalidate the affected destination-specific path-MTU entries, allow discovery to run over the restored path, and reestablish the replication TCP connections.

**Explanation:** The senders are still enforcing a previously discovered limit even though the path now supports jumbo packets. Invalidating the affected entries allows the senders to discover the current path capability. Reestablishing the TCP connections also removes connection-specific sizing state negotiated or learned while the smaller limit applied. The successful DF probes establish that using larger packets is now safe, and destination-specific changes preserve unrelated traffic settings.

## Practice Path MTU Discovery in a full exam

Questions on Path MTU Discovery 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): 5 questions

## What is Path MTU Discovery

Path MTU Discovery, commonly abbreviated PMTUD, allows a sender to adapt packet sizes to the capabilities of an end-to-end network path. An interface MTU describes the largest IP packet that an interface can carry without fragmentation; the path MTU is the smallest applicable MTU along the route. Ethernet frame size and IP MTU are related but are not interchangeable: Ethernet headers and other link-layer overhead are outside the IP MTU.

Classic IPv4 PMTUD sends packets with the Don't Fragment flag set. A router that cannot forward a packet because it exceeds the next-hop MTU drops it and returns an ICMP Destination Unreachable message with type 3, code 4, meaning fragmentation is needed. The sender uses that feedback to reduce its packet size. IPv6 routers do not fragment forwarded packets; they return ICMPv6 Packet Too Big messages, type 2, so the source can adjust its transmissions.

Filtering these messages can create a PMTUD black hole. DNS queries, TCP handshakes, and small interactive requests may succeed, while large responses, file transfers, or TLS exchanges stall. This pattern often indicates a packet-size problem rather than a routing failure. Permit the required ICMP feedback through relevant security groups, network ACLs, host firewalls, and on-premises firewalls. Allowing only ICMP echo requests and replies is not sufficient.

For example, an instance with a 9001-byte interface MTU might communicate successfully with another instance over a jumbo-capable path but encounter a smaller limit when reaching an on-premises system through a tunnel. Setting both endpoint interfaces to 9001 does not make the intermediate path jumbo-capable. IPsec and other encapsulations consume packet space, reducing the usable inner-packet MTU. Paths in opposite directions can also have different limits, and routing changes can invalidate a previously discovered value.

Validate connectivity with size-controlled probes as well as application traffic. On Linux, ping -4 -M do -s 1472 destination tests a 1500-byte IPv4 packet when there are no IP options: 1472 bytes of payload plus an 8-byte ICMP header and a 20-byte IPv4 header. Increase or decrease the payload to locate the working boundary. This test requires ICMP echo support and does not prove that TCP or UDP follows an identical path. Use tracepath where supported, capture ICMP errors and retransmissions, and test representative transfers in both directions. Account for segmentation and receive offloads when interpreting packet captures on endpoints.

Jumbo packets can reduce per-packet processing and header overhead during bulk transfers, but they do not increase the physical link speed. Configure them only where every relevant segment supports the intended MTU. In AWS, supported EC2 interfaces can use an MTU of 9001. AWS Direct Connect supports jumbo MTUs of 9001 on private virtual interfaces and 8500 on transit virtual interfaces, subject to connection support and configuration; public virtual interfaces use 1500. Transit Gateway has an 8500-byte MTU for supported attachment paths, while VPN paths have lower limits.

Not every managed connectivity service supports classic PMTUD. AWS Site-to-Site VPN does not support it, so select an appropriate tunnel MTU and TCP maximum segment size rather than assuming ICMP feedback will resolve oversized packets. Its maximum supported MTU is 1446 bytes, and encryption settings can require a smaller value. TCP MSS clamping can mitigate TCP sizing problems, but it does not fix UDP or increase the path MTU. Packetization-layer discovery can probe usable sizes without depending solely on ICMP, where the transport or application implements it. A practical design combines compatible MTUs, permitted feedback where supported, and explicit validation of primary and failover paths.
