Changes

From SME Server
Jump to navigationJump to search
608 bytes added ,  14:40, 11 December 2012
Show how to find MTU using tracepath
Line 22: Line 22:  
*TCP Problems with Path MTU Discovery http://www.ietf.org/rfc/rfc2923.txt
 
*TCP Problems with Path MTU Discovery http://www.ietf.org/rfc/rfc2923.txt
   −
As discussed in [[Bugzilla:6888]] a workaround was found that may help in mitigating the issue.  
+
As discussed in [[Bugzilla:6888]] a workaround was found that may help in mitigating the issue.
   −
Ensure the MTU setting on your local (gateway) router is set to 1492, then set the MTU on your SME server to the same value (1492) using the following:
+
The [http://linux.die.net/man/8/tracepath tracepath] utility (included with SME 8.0 and SME 7.6) can be used to locate non-standard MTU values between your SME server and any remote host.
 +
 
 +
You can discover the smallest MTU between you and google.com (for example) by running this command, then locating the smallest value of "pmtu" in the results:
 +
tracepath google.com
 +
 
 +
If tracepath returns any value below 1500 between your SME server and a mail server that you need to receive email from, you may need to reset the MTU on the SME server to match the smallest value returned.
 +
 
 +
For example, if tracepath returns 1492 (typical for internet connections using PPPoE), you would need to set the MTU on your SME server to the same value (1492) using the following:
    
  config setprop InternalInterface MTU 1492
 
  config setprop InternalInterface MTU 1492

Navigation menu