On Fri, 2015-10-16 at 13:33 +0200, Daniel Wagner wrote:
> OpenVPN has several command line option to configure how to handle the
> MTU of packets. The plugin accepts a OpenVPN.MTU options which is
> translated to '--mtu'. This options not available (has it ever
> existed?) since 2.0. We recommend at least version 2.2 of OpenVPN.
>
> It looks like no one is using this, because if he did, OpenVPN bails
> out and complains about unknown --mtu option.
>
> In this light, let's drop it and add the exising MTU releated options.
> ---
>
> Changes since v0
> - Update documation
>
> doc/vpn-config-format.txt | 9 ++++++++-
> vpn/plugins/openvpn.c | 7 ++++++-
> 2 files changed, 14 insertions(+), 2 deletions(-)
>
> diff --git a/doc/vpn-config-format.txt b/doc/vpn-config-format.txt
> index 23c9c14..1b49765 100644
> --- a/doc/vpn-config-format.txt
> +++ b/doc/vpn-config-format.txt
> @@ -76,7 +76,14 @@ OpenVPN VPN supports following options (see openvpn(8) for
> details):
> OpenVPN.CACert --ca Certificate authority file (M)
> OpenVPN.Cert --cert Local peer's signed certificate (M)
> OpenVPN.Key --key Local peer's private key (M)
> - OpenVPN.MTU --mtu MTU of the tunnel (O)
> + OpenVPN.LinkMTU --link-mtu Set the TCP/UDP device MTU
> + and derive the tun MTU (O)
> + OpenVPN.TunMTU --tun-mtu Take the tun/tap device MTU and
> + derive the TCP/UDP MTU from it (O)
> + OpenVPN.TunMTUExtra --tun-mtu-extra Assume that tun/tap device adds
> + additional overhead (O)
> + OpenVPN.Fragment --fragment Enable internal fragmenation (O)
> + OpenVPN.MSSFix --mssfix Set uppper bound on TCP MSS (O)
Are any of these necessary for any use cases? If they are needed for
something, could the currently specified OpenVPN.MTU be used to derive
proper MTUs for the devices involved?
Cheers,
Patrik
_______________________________________________
connman mailing list
connman@connman.net
https://lists.connman.net/mailman/listinfo/connman
