[OpenVPN home] [Date Prev] [Date Index] [Date Next]
[OpenVPN mailing lists] [Thread Prev] [Thread Index] [Thread Next]
Google
 
Web openvpn.net

[Openvpn-users] MTU settings for non TCP traffic


  • Subject: [Openvpn-users] MTU settings for non TCP traffic
  • From: "Kevin P. Fleming" <kpfleming@xxxxxxxxxxxxxxxxxxxx>
  • Date: Thu, 04 Mar 2004 08:59:46 -0700

OK, I set up my first tunnel with openvpn-1.6rc1 yesterday, with Linux 2.4.25 at one end and Linux 2.6.4-rc1 at the other. Initially I made no MTU changes at all, and used --mtu-test. This reported 1325.

After trying various combinations, I've found that --tun-mtu 1500 and --mssfix 1325 appears to work well, and based on reading the list archives this seems to be the preferred way to set things up (i.e. don't use --fragment at all if you don't have to).

However, I have two more tunnels to set up, and these will be carrying primarily non-TCP traffic. It will also be "routed" traffic, originating and terminating from systems other than the ones running openvpn. Does this mean I'll be forced to use --fragment for these tunnels, since the other systems involved won't have any way to know the "path MTU"?

Also, is there any reason to use the --mtu-disc parameter? Does this affect the path _between_ the openvpn endpoints, or the path from openvpn out to its "clients"?

____________________________________________
Openvpn-users mailing list
Openvpn-users@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/openvpn-users