Hello there,

Here are just a few points to clarify some discrepancies you could be seeing with CMD vs. PingPlotter:

• Setting the packet size from CMD does not include the byte size for the header, which is 28 bytes. This means a 1500 byte packet would be 1528 bytes.
  
  
• Setting the packet size in PingPlotter does include the byte size for the header. If the packet size is set to 1472, it does take the header into account, which drops the payload size down to 1444 (and, consequently, is 1472 when it ships out).
  
  
• If a CMD line packet size is 1473, it would still add on a header and push the final size to 1501 - exceeding the MTU.
  
  
• If a PingPlotter packet size is 1473, it already factors in the header, so the final size would be 1473.

In a nutshell, CMD does not factor in the header size, but PingPlotter does - this would mean that a 1500 byte packet in PP would equal a command-line packet of 1472.

If PingPlotter is still able to send out unfragmented UDP packets of 1700 while specifying the VPN Network Interface in Edit -> Options -> Engine, it would be greatly appreciated if you could send over corresponding screenshots of both the target graphs and the engine options.

I hope this helps explain a few things - please let me know if this leaves you with any questions.

All the best,

Austin Berner
Quality Assurance Analyst | Pingman Tools
support@pingman.com | (208) 345-0030 ext. 1059 or 1062