MTU Test
AvailableFind the largest packet your connection carries without fragmentation, calculate MTU and TCP MSS for VPN and tunnel stacks, and generate MTU and MSS clamping commands for common routers.
MTU Test
The NetTools server sends packets with the Don’t Fragment bit set to your own public IP address and narrows down the largest size that gets through. No target to enter: only the address your request comes from is ever probed.
Methods
HTTP transfer test
Downloads 32 KB, 256 KB, 1024 KB and 2048 KB from the NetTools server. If small downloads finish but larger ones stall, full-size packets are being lost somewhere — a typical PMTU black-hole symptom. Uses one speed-test session.
Manual test from your device
Measures the path from your own computer — the most reliable result, and the only option when your router does not answer ping. Run the command, lower the size until replies come back without “fragmentation needed”, “message too long” or “Packet needs to be fragmented but DF set”, then enter the largest size that worked.
Advanced diagnostics — every probe
Default WireGuard value. Run a test or the calculator to fill this in.
Commands are shown for you to review and copy; NetTools never runs anything on your devices. Test on a maintenance window or with console access — a wrong MTU on the interface you are connected through can cut you off.
How it works
The NetTools server sends ICMP echo requests with the Don’t Fragment bit set to your own public IPv4 address (your router or NAT), starting small and narrowing the size with a binary search; ICMP “Fragmentation needed” replies are used when they arrive. The calculator adds up the exact header sizes of each tunnel layer, including ESP and OpenVPN padding, and derives the effective MTU and TCP MSS.
How the discovery works
- The server first sends a small ping (84 bytes) to check that your address answers at all. If it does not, the result is BLOCKED — common, because many routers drop ping from the internet.
- It then tries the largest size it can send itself (1500 bytes), and if that fails, narrows the size with a binary search. An ICMP “Fragmentation needed” reply names the exact MTU and is used directly.
- Packets that simply vanish are never taken as proof that they were too big. Results that rest only on missing replies are marked INCONCLUSIVE.
- The probe ends at your router or NAT, not at your computer. The manual test measures from your own device.
What cannot be measured here
- TCP MSS: NetTools.tech is reached through Cloudflare and a reverse proxy that terminate TCP, so the server never sees the MSS your device advertises.
- IPv6: the probe server has no IPv6 connectivity yet. Use the manual test with IPv6 selected.
Labels
- Measured — from NetTools probes. Observed — from downloads in your browser. User supplied — from your manual test. Calculated — derived from header sizes. Unknown — no method produced a value.
Safeguards & responsible use
- Probes go only to the public IPv4 address your request came from — you cannot enter another target. At most 24 probe sizes with 2 packets each, one running test per visitor, a per-address budget and the normal rate limits.
- The calculator and configuration generator run entirely in your browser; generated commands are shown for you to copy and are never executed.
Learn more
What is MTU Test?How it works, how to read the results, troubleshooting and FAQs. Complete guide →Frequently asked questions
What MTU should I use?
Use the path MTU: 1500 on plain Ethernet and most fibre or cable links, 1492 on PPPoE, and lower inside VPN tunnels — for example 1420 for WireGuard over IPv4/IPv6. The calculator shows the exact value for your stack.
Why does the test say BLOCKED?
Your router or firewall does not answer ping from the internet, which is common and not a fault. Run the manual test from your own computer instead; it measures the path from your device.
What is the difference between MTU and MSS?
The MTU is the largest IP packet a link carries. The TCP MSS is the largest TCP payload in one segment: MTU minus 40 bytes for IPv4 (20 IP + 20 TCP) or 60 bytes for IPv6.
Can NetTools see the MSS my device sends?
No. NetTools.tech is served through Cloudflare and a reverse proxy, which terminate TCP, so the probe server never receives your SYN. The test reports this as UNSUPPORTED instead of guessing.