Are there any OpenVPN directives not supported by the app?
While most OpenVPN client directives are supported by the app, we have made an effort to reduce bloat and improve maintainability by eliminating what we believe to be obsolete or rarely-used directives. Please email us at email@example.com if you believe that a specific directive that is not included should be reconsidered for inclusion.
Here is a partial list of directives not currently supported:
- dev tap — This directive is not supported because the underlying Android VPN API doesn’t support tap-style tunnels.
- fragment — The fragment directive is not supported due to the complexity it adds to the OpenVPN implementation and the fact that it is usually better to leave fragmentation up to the lower-level transport protocols. Note as well that the client does not support connecting to a server that uses the fragment directive.
- mssfix — This directive will be added in a future release. Since the functionality of mssfix can be achieved on either the client or server side, specifying it on the server side will enable it even if the client doesn’t support the directive.
- secret — Static key encryption mode (non-TLS) is not supported.
- socks-proxy — Socks proxy support is currently not supported.
- Ciphers other than AES, Blowfish, and DES family — Currently, only AES, Blowfish, and DES family ciphers are supported. This is done to reduce bloat and improve energy efficiency. The AES cipher algorithm, in particular, is well-suited for the ARM processor generally used in Android devices.
- proxy directives — While proxy directives are currently supported (http-proxy and http-proxy-option), they are currently NOT supported in <connection> profiles.