(TCP, IP, MTU and MSS magic numbers)
| 1500 | The biggest-sized IP packet that can normally traverse the Internet without getting fragmented. Typical MTU for non-PPPoE, non-VPN connections. |
| 1492 | The maximum MTU recommended for Internet PPPoE implementations. |
| 1472 | The maximum ping data payload before fragmentation errors are received on non-PPPoE, non-VPN connections. |
| 1460 | TCP Data size (MSS) when MTU is 1500 and not using PPPoE. |
| 1464 | The maximum ping data payload before fragmentation errors are received when using a PPPoE-connected machine. |
| 1452 | TCP Data size (MSS) when MTU is 1492 and using PPPoE. |
| 576 | Typically recommended as the MTU for dial-up type applications, leaving 536 bytes of TCP data. |
| 48 | The sum of IP, TCP and PPPoE headers. |
| 28 | The sum of IP and ICMP headers. |
Reduce 1472 by 10 until you no longer get the “packet needs to be fragmented” error message.
Then increase by 1 until you are 1 less away from getting the “packet need to be fragmented” message again.
Add 28 more to this (since you specified ping packet size, not including IP/ICMP header of 28 bytes),
and this is your MaxMTU.
Note: If you can ping through with the number at 1472, you are done! Stop right there.
Add 28 and your MaxMTU is 1500.
For PPPoE, your MaxMTU should be no more than 1492 to allow space for the 8 byte PPPoE “wrapper,”
but again, experiment to find the optimal value.
For PPPoE, the stakes are high: if you get your MTU wrong, you may not just be sub-optimal, things like
UPLOADING or web pages may stall or not work at all!
Comments
(There are currently no comments for this post.)