You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/content/docs/cloudflare-one/team-and-resources/devices/warp/deployment/mdm-deployment/path-mtu-discovery.mdx
The [Maximum Transmission Unit (MTU)](https://www.cloudflare.com/learning/network-layer/what-is-mtu/) is the largest data packet size that a device can send over a network without fragmentation. When you connect to services through WARP, your data is encapsulated, which adds extra headers and increases the overall packet size. On some networks, especially cellular or guest Wi-Fi networks, the network's MTU may be smaller than WARP's [default packet size](#default-warp-mtu). This mismatch forces packets to be fragmented or dropped entirely, leading to connection instability or complete connection failures.
28
+
The [Maximum Transmission Unit (MTU)](https://www.cloudflare.com/learning/network-layer/what-is-mtu/) is the largest data packet size that a device can send over a network without fragmentation. When you connect to services through WARP, your data is encapsulated, which adds extra headers and increases the overall packet size. On some networks, especially cellular or guest Wi-Fi networks, the network's MTU may be smaller than WARP's [default packet size](#recommended-mtu). This mismatch forces packets to be fragmented or dropped entirely, leading to connection instability or complete connection failures.
29
29
30
30
WARP's Path MTU Discovery (PMTUD) feature solves this problem by actively probing for the minimum MTU along the entire network path between the device and Cloudflare. WARP will then dynamically adjust its [tunnel interface](/cloudflare-one/team-and-resources/devices/warp/configure-warp/route-traffic/warp-architecture/#virtual-interface) MTU based on the probe results. This allows WARP to maintain a stable connection on low MTU networks and take advantage of higher MTUs when available.
31
31
@@ -58,14 +58,14 @@ WARP will now send active probes to detect the network path MTU and will update
58
58
59
59
## Minimum MTUs
60
60
61
-
### Default WARP MTU
61
+
### Recommended MTU
62
62
63
63
WARP requires the following MTUs for full functionality and performance:
64
64
65
65
| Device tunnel protocol| IPv4 | IPv6 |
66
66
| --- | --- | --- |
67
67
| WireGuard | 1340 bytes | 1360 bytes |
68
-
| MASQUE |1330 bytes |1350 bytes |
68
+
| MASQUE |1361 bytes |1381 bytes |
69
69
70
70
### Path MTU Discovery
71
71
@@ -95,27 +95,27 @@ You can check your current network path MTU by collecting [WARP diagnostic logs]
95
95
96
96
1. Run the `warp-diag` command on the device or [collect logs via the the dashboard](/cloudflare-one/team-and-resources/devices/warp/troubleshooting/warp-logs/#collect-logs-via-the-dashboard).
97
97
2. Open the resulting `warp-debugging-info-<date>-<time>.zip` file.
98
-
3. Open `connectivity.txt` and search for `PMTU`. For example, the following diagnostic log shows an MTU of 1500 bytes which meets the [default MTU requirements](#default-warp-mtu) for WARP.
Testing H3 QUIC connectivity to 'https://cloudflare-quic.com/cdn-cgi/l4-stats' result: Successful
106
+
IPv4:
107
+
"
108
+
Headers:
109
+
server address=104.18.26.14:443
110
+
...
111
+
112
+
Body:
113
+
transport=TCP
114
+
...
115
+
116
+
PMTU:
117
+
1500 bytes
118
+
"
119
+
```
120
+
121
+
The example log shows an MTU of 1500 bytes, which meets the [recommended MTU requirements](#recommended-mtu) for WARP. If your MTU falls below the recommended threshold, consider [enabling Path MTU Discovery](#enable-path-mtu-discovery) to optimize connection performance.
0 commit comments