CINXE.COM

<!DOCTYPE html> <html lang="en"> <head> <meta charset="utf-8"> <meta http-equiv="X-UA-Compatible" content="IE=edge"> <meta name="viewport" content="width=device-width, initial-scale=1"> <title>Advanced Configuration Commands - SparkLabs</title> <link href="/static/css/bootstrap.min.css" rel="stylesheet"> <link href="/static/css/sl_styles.css" rel="stylesheet">   <link rel="apple-touch-icon" sizes="180x180" href="/apple-touch-icon.png"> <link rel="icon" type="image/png" sizes="32x32" href="/favicon-32x32.png"> <link rel="icon" type="image/png" sizes="16x16" href="/favicon-16x16.png"> <link rel="mask-icon" href="/safari-pinned-tab.svg" color="#5bbad5"> <meta name="msapplication-TileColor" content="#da532c"> <meta name="theme-color" content="#ffffff"> <link href="/static/css/lity.min.css" rel="stylesheet"> <script src="/static/js/moment.min.js"></script> <link href="/blog/feed/" rel="alternate" title="SparkLabs Blog" type="application/atom+xml"> </head> <body> <div class="sl_header_background_generic" id="slheader"> <nav class="navbar navbar-default bs-docs-nav"> <div class="container"> <div class="navbar-header"> <button type="button" class="navbar-toggle collapsed" data-toggle="collapse" data-target="#navbar" aria-expanded="false" aria-controls="navbar"> Toggle navigation </button> <div style="position: relative;height:50px;"> <a class="navbar-brand" href="/">SparkLabs</a> </div> </div> <div id="navbar" class="navbar-collapse collapse"> <ul class="nav navbar-nav navbar-right"> <li class="dropdown"> <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-haspopup="true" aria-expanded="false">Products </a> <ul class="dropdown-menu dropdown-menu-left"> <li><a href="/viscosity/">Viscosity</a></li> </ul> </li> <li><a href="/blog/">Blog</a></li> <li><a href="/company/">Company</a></li> <li><a href="/support/">Support</a></li> </ul> </div> </div> </nav>  <div class="container sl_header"> <div class="row"> <div class="col-md-12"> <h1 class="sl_headertext">App Support.</h1> <h1 class="sl_subheadertext">We're here to help.</h1> </div> </div> </div> </div>  <div class="content">  <div class="sl_row_gradient"> <div class="container bs-docs-container"> <div class="row sl_paddedrow"> <div class="col-md-12"> <ol class="breadcrumb"><li><a href="/support/kb/">Knowledge Base</a></li><li><a href="/support/kb/category/documentation/">Documentation</a></li><li class="active">Advanced Configuration Commands</li></ol> </div> <div class="col-md-8"> <h3 class="sl_section_header" id="advanced-configuration-commands">Advanced Configuration Commands</h3> <div class="sl_article">Viscosity provides the ability to configure additional advanced connection settings using raw configuration commands. Adding and editing configuration commands should only be attempted by advanced users: incorrect use can break your connection, make it insecure, or cause performance problems. For the vast majority of connections it is not necessary to specify or edit configuration commands. <h1 id="specifying-advanced-configuration-commands">Specifying Advanced Configuration Commands</h1> Viscosity allows commands to be specified in the configuration commands section, located under the Advanced tab when editing your connection in Viscosity. The screenshot below shows an example of an empty configuration commands area. Each command should be specified on a new line in the commands area. A line should start with the desired command, followed by the paramaters (if any) separated by spaces. More information about the available commands can be found in the sections below. To remove a command simply delete the entire line it is on. <div class="row"><div class="col-xs-12 text-center screenshot_image" id="advanced-commands-macos" data-screenshot-zoom="0.50" data-screenshot-mac="advanced-commands-macos" data-screenshot-win="editor-advanced-win" > </div><div class="col-xs-12 text-center" style="padding-top:10px;padding-bottom:10px;"><a href="" class="screenshot_button screenshot_button_left_v" data-screenshot="advanced-commands-macos" data-platform="mac"></a><a href="" class="screenshot_button screenshot_button_right_v" data-screenshot="advanced-commands-macos" data-platform="win"></a>   <a href="" class="screenshot_button screenshot_button_fullscreen" data-screenshot="advanced-commands-macos"></a></div></div><div id="screenshot-advanced-commands-macos" class="lity-hide"><img src="advanced-commands-macos" class="img-responsive"></div><div id="screenshot-editor-advanced-win" class="lity-hide"><img src="editor-advanced-win" class="img-responsive"></div> <h1 id="advanced-viscosity-commands">Advanced Viscosity Commands</h1> Viscosity provides a number of additional commands that provide advanced features and options beyond what is available through the editor. When specifying a Viscosity command it must start with <code>#viscosity</code>, which provides backwards compatibility with older clients. <h2 id="static-challenge-password"><a href="#static-challenge-password">static-challenge-password </a></h2> Syntax <code>#viscosity static-challenge-password text [delimiter]</code> Specifies that Viscosity should separately prompt for a two-factor credential (such as a one-time password or PIN) and append this credential to the password sent to the server. The user will be prompted using the "text" parameter. If a delimiter (such as a special character) should be automatically added between the password and the two-factor credential, it can be optionally specified as the "delimiter" parameter. This command is designed to be used with servers using legacy authentication scripts (instead of modern challenge support) where the server expects both user's password and two-factor credential are combined. For example <code>#viscosity static-challenge-password "Please enter your one time password"</code> or <code>#viscosity static-challenge-password "Please enter your one time password" "+"</code>. <h2 id="static-challenge-acknowledge"><a href="#static-challenge-acknowledge">static-challenge-acknowledge </a></h2> Syntax <code>#viscosity static-challenge-acknowledge text</code> Specifies that Viscosity should prompt the user during the authentication stage. The user will be prompted using the "text" parameter. This command is designed to be used with servers that require the user to perform an action (where no input is required) to allow the authentication request to succeed. A common use case is asking the user to approve an authentication request on a two-factor device. The prompt will be automatically closed when the authentication phase succeeds or fails. For example <code>#viscosity static-challenge-acknowledge "Please approve the authentication request on your registered mobile device to establish the connection."</code>. <h2 id="system-identity-domain"><a href="#system-identity-domain">system-identity-domain </a></h2> Syntax <code>#viscosity system-identity-domain domain</code> Specifies that Viscosity should only search a particular Keychain domain when using System Identity authentication with a Match DN. Valid domains include "user", "system", "dynamic", and "all" (the default). A value of "user" will limit searches to the user鈥檚 keychain, "system" will limit searches to the system keychain, "dynamic" will limit searches to dynamic (token, smart card, etc.) keychains, and "all" will search all keychains in the user鈥檚 search list. For example <code>#viscosity system-identity-domain user</code>. <h2 id="proxy-automatic"><a href="#proxy-automatic">proxy-automatic </a></h2> Syntax: <code>#viscosity proxy-automatic address</code> Specifies an automatic proxy configuration file to set on the VPN interface. If DNS mode is set to full this setting will be used by web browsers and other applications on the system. "address" must be a full http or https address to a <a href="https://en.wikipedia.org/wiki/Proxy_auto-config">PAC (Proxy Auto-Configuration)</a> file. For example <code>#viscosity proxy-automatic http://example.com/proxy.pac</code>. <h2 id="proxy-http"><a href="#proxy-http">proxy-http </a></h2> Syntax: <code>#viscosity proxy-http address port</code> Specifies a Web Proxy (HTTP) to set on the VPN interface. If DNS mode is set to full this setting will be used by web browsers and other applications on the system. "address" must be a DNS or IP address of the proxy host, and port number must be the port. For example <code>#viscosity proxy-http proxy.example.com 8080</code>. <h2 id="proxy-https"><a href="#proxy-https">proxy-https </a></h2> Syntax: <code>#viscosity proxy-https address port</code> Specifies a Secure Web Proxy (HTTPS) to set on the VPN interface. If DNS mode is set to full this setting will be used by web browsers and other applications on the system. "address" must be a DNS or IP address of the proxy host, and port number must be the port. For example <code>#viscosity proxy-https proxy.example.com 8080</code>. <h2 id="proxy-socks"><a href="#proxy-socks">proxy-socks </a></h2> Syntax: <code>#viscosity proxy-socks address port</code> Specifies a SOCKS Proxy to set on the VPN interface. If DNS mode is set to full this setting will be used by web browsers and other applications on the system. "address" must be a DNS or IP address of the proxy host, and port number must be the port. For example <code>#viscosity proxy-socks proxy.example.com 1080</code>. <h1 id="advanced-openvpn-commands">Advanced OpenVPN Commands</h1> OpenVPN configuration commands that can be specified can be found below. Please be aware that this list does not contain all possible OpenVPN commands: commands that are only valid when OpenVPN is being used in server-mode, as well as ignored commands, are not listed. <h2 id="allow-compression"><a href="#allow-compression">allow-compression</a></h2> Syntax: <code>allow-compression <var>mode</var></code> As described in the <a href="#compress">compress</a> option, compression is a potentially dangerous option. This option allows controlling the behaviour of OpenVPN when compression is used and allowed. Valid syntaxes: <pre class="literal-block"> allow-compression allow-compression mode </pre> The mode argument can be one of the following values: <code>asym</code> OpenVPN will only decompress downlink packets but not compress uplink packets. This also allows migrating to disable compression when changing both server and client configurations to remove compression at the same time is not a feasible option. <code>no</code> (default) OpenVPN will refuse any compression. If data-channel offloading is enabled, OpenVPN will additionally also refuse compression framing (stub). <code>yes</code> OpenVPN will send and receive compressed packets. <h2 id="allow-pull-fqdn"><a href="#allow-pull-fqdn">allow-pull-fqdn</a></h2> Syntax: <code>allow-pull-fqdn</code> Allow client to pull DNS names from server (rather than being limited to IP address) for <a href="#ifconfig">ifconfig</a>, <a href="#route">route</a>, and <a href="#route-gateway">route-gateway</a>. <h2 id="allow-recursive-routing"><a href="#allow-recursive-routing">allow-recursive-routing</a></h2> Syntax: <code>allow-recursive-routing</code> When this option is set, OpenVPN will not drop incoming tun packets with same destination as host. <h2 id="askpass"><a href="#askpass">askpass</a></h2> Syntax: <code>askpass <var>file</var></code> Get certificate password from console or file before we daemonize. Valid syntaxes: <pre class="literal-block"> askpass askpass file </pre> For the extremely security conscious, it is possible to protect your private key with a password. Of course this means that every time the OpenVPN daemon is started you must be there to type the password. The askpass option allows you to start OpenVPN from the command line. It will query you for a password before it daemonizes. To protect a private key with a password you should omit the -nodes option when you use the openssl command line tool to manage certificates and private keys. If file is specified, read the password from the first line of file. Keep in mind that storing your password in a file to a certain extent invalidates the extra security provided by using an encrypted key. <h2 id="auth"><a href="#auth">auth</a></h2> Syntax: <code>auth <var>alg</var></code> Authenticate data channel packets and (if enabled) tls-auth control channel packets with HMAC using message digest algorithm alg. (The default is SHA1 ). HMAC is a commonly used message authentication algorithm (MAC) that uses a data string, a secure hash algorithm and a key to produce a digital signature. The OpenVPN data channel protocol uses encrypt-then-mac (i.e. first encrypt a packet then HMAC the resulting ciphertext), which prevents padding oracle attacks. If an AEAD cipher mode (e.g. GCM) is chosen then the specified auth algorithm is ignored for the data channel and the authentication method of the AEAD cipher is used instead. Note that alg still specifies the digest used for tls-auth. In static-key encryption mode, the HMAC key is included in the key file generated by genkey. In TLS mode, the HMAC key is dynamically generated and shared between peers via the TLS control channel. If OpenVPN receives a packet with a bad HMAC it will drop the packet. HMAC usually adds 16 or 20 bytes per packet. Set alg=none to disable authentication. For more information on HMAC see http://www.cs.ucsd.edu/users/mihir/papers/hmac.html <h2 id="auth-nocache"><a href="#auth-nocache">auth-nocache</a></h2> Syntax: <code>auth-nocache</code> Don't cache <a href="#askpass">askpass</a> or <a href="#auth-user-pass">auth-user-pass</a> username/passwords in virtual memory. If specified, this directive will cause OpenVPN to immediately forget username/password inputs after they are used. As a result, when OpenVPN needs a username/password, it will prompt for input from stdin, which may be multiple times during the duration of an OpenVPN session. When using auth-nocache in combination with a user/password file and chroot or daemon, make sure to use an absolute path. This directive does not affect the <a href="#http-proxy">http-proxy</a> username/password. It is always cached. <h2 id="auth-retry"><a href="#auth-retry">auth-retry</a></h2> Syntax: <code>auth-retry <var>type</var></code> Controls how OpenVPN responds to username/password verification errors such as the client-side response to an <code>AUTH_FAILED</code> message from the server or verification failure of the private key password. Normally used to prevent auth errors from being fatal on the client side, and to permit username/password requeries in case of error. An <code>AUTH_FAILED</code> message is generated by the server if the client fails <a href="#auth-user-pass">auth-user-pass</a> authentication, or if the server-side client-connect script returns an error status when the client tries to connect. type can be one of: <code>none</code> Client will exit with a fatal error (this is the default). <code>nointeract</code> Client will retry the connection without requerying for an <a href="#auth-user-pass">auth-user-pass</a> username/password. Use this option for unattended clients. <code>interact</code> Client will requery for an <a href="#auth-user-pass">auth-user-pass</a> username/password and/or private key password before attempting a reconnection. Note that while this option cannot be pushed, it can be controlled from the management interface. <h2 id="auth-token-user"><a href="#auth-token-user">auth-token-user</a></h2> Syntax: <code>auth-token-user <var>base64username</var></code> Companion option to auth-token. This options allows one to override the username used by the client when reauthenticating with the auth-token. It also allows one to use auth-token in setups that normally do not use username and password. The username has to be base64 encoded. <h2 id="auth-user-pass"><a href="#auth-user-pass">auth-user-pass</a></h2> Syntax: <code>auth-user-pass</code> Authenticate with server using username/password. Valid syntaxes: <pre class="literal-block"> auth-user-pass auth-user-pass up </pre> If up is present, it must be a file containing username/password on 2 lines. If the password line is missing, OpenVPN will prompt for one. If up is omitted, username/password will be prompted from the console. The server configuration must specify an auth-user-pass-verify script to verify the username/password provided by the client. <h2 id="bcast-buffers"><a href="#bcast-buffers">bcast-buffers</a></h2> Syntax: <code>bcast-buffers <var>n</var></code> Allocate n buffers for broadcast datagrams (default <code>256</code>). <h2 id="bind"><a href="#bind">bind</a></h2> Syntax: <code>bind <var>keywords</var></code> Bind to local address and port. This is the default unless any of <a href="#proto">proto</a> tcp-client , <a href="#http-proxy">http-proxy</a> or <a href="#socks-proxy">socks-proxy</a> are used. If the optional <code>ipv6only</code> keyword is present OpenVPN will bind only to IPv6 (as opposed to IPv6 and IPv4) when a IPv6 socket is opened. <h2 id="bind-dev"><a href="#bind-dev">bind-dev</a></h2> Syntax: <code>bind-dev <var>device</var></code> (Linux only) Set device to bind the server socket to a Virtual Routing and Forwarding device <h2 id="block-ipv6"><a href="#block-ipv6">block-ipv6</a></h2> Syntax: <code>block-ipv6</code> On the client, instead of sending IPv6 packets over the VPN tunnel, all IPv6 packets are answered with an ICMPv6 no route host message. On the server, all IPv6 packets from clients are answered with an ICMPv6 no route to host message. This options is intended for cases when IPv6 should be blocked and other options are not available. block-ipv6 will use the remote IPv6 as source address of the ICMPv6 packets if set, otherwise will use <code>fe80::7</code> as source address. For this option to make sense you actually have to route traffic to the tun interface. The following example config block would send all IPv6 traffic to OpenVPN and answer all requests with no route to host, effectively blocking IPv6 (to avoid IPv6 connections from dual-stacked clients leaking around IPv4-only VPN services). Client config <pre class="first last literal-block"> <a href="#ifconfig-ipv6">ifconfig-ipv6</a> fd15:53b6:dead::2/64 fd15:53b6:dead::1 <a href="#redirect-gateway">redirect-gateway</a> ipv6 block-ipv6 </pre> Server config Push a "valid" ipv6 config to the client and block on the server <pre class="last literal-block"> <a href="#push">push</a> "ifconfig-ipv6 fd15:53b6:dead::2/64 fd15:53b6:dead::1" <a href="#push">push</a> "redirect-gateway ipv6" block-ipv6 </pre> Note: this option does not influence traffic sent from the server towards the client (neither on the server nor on the client side). This is not seen as necessary, as such traffic can be most easily avoided by not configuring IPv6 on the server tun, or setting up a server-side firewall rule. <h2 id="ca"><a href="#ca">ca</a></h2> Syntax: <code>ca <var>file</var></code> Certificate authority (CA) file in .pem format, also referred to as the root certificate. This file can have multiple certificates in .pem format, concatenated together. You can construct your own certificate authority certificate and private key by using a command such as: <pre class="literal-block"> openssl req -nodes -new -x509 -keyout ca.key -out ca.crt </pre> Then edit your openssl.cnf file and edit the certificate variable to point to your new root certificate ca.crt. For testing purposes only, the OpenVPN distribution includes a sample CA certificate (ca.crt). Of course you should never use the test certificates and test keys distributed with OpenVPN in a production environment, since by virtue of the fact that they are distributed with OpenVPN, they are totally insecure. <h2 id="capath"><a href="#capath">capath</a></h2> Syntax: <code>capath <var>dir</var></code> Directory containing trusted certificates (CAs and CRLs). Not available with mbed TLS. CAs in the capath directory are expected to be named <hash>.<n>. CRLs are expected to be named <hash>.r<n>. See the -CApath option of openssl verify, and the -hash option of openssl x509, openssl crl and X509_LOOKUP_hash_dir()(3) for more information. Similar to the <a href="#crl-verify">crl-verify</a> option, CRLs are not mandatory - OpenVPN will log the usual warning in the logs if the relevant CRL is missing, but the connection will be allowed. <h2 id="ccd-exclusive"><a href="#ccd-exclusive">ccd-exclusive</a></h2> Syntax: <code>ccd-exclusive</code> Require, as a condition of authentication, that a connecting client has a client-config-dir file. <h2 id="cd"><a href="#cd">cd</a></h2> Syntax: <code>cd <var>dir</var></code> Change directory to dir prior to reading any files such as configuration files, key files, scripts, etc. dir should be an absolute path, with a leading "/", and without any references to the current directory such as <code>.</code> or <code>..</code>. This option is useful when you are running OpenVPN in daemon mode, and you want to consolidate all of your OpenVPN control files in one location. <h2 id="cert"><a href="#cert">cert</a></h2> Syntax: <code>cert <var>file</var></code> Local peer's signed certificate in .pem format -- must be signed by a certificate authority whose certificate is in <a href="#ca">ca</a> file. Each peer in an OpenVPN link running in TLS mode should have its own certificate and private key file. In addition, each certificate should have been signed by the key of a certificate authority whose public key resides in the <a href="#ca">ca</a> certificate authority file. You can easily make your own certificate authority (see above) or pay money to use a commercial service such as thawte.com (in which case you will be helping to finance the world's second space tourist :). To generate a certificate, you can use a command such as: <pre class="literal-block"> openssl req -nodes -new -keyout mycert.key -out mycert.csr </pre> If your certificate authority private key lives on another machine, copy the certificate signing request (mycert.csr) to this other machine (this can be done over an insecure channel such as email). Now sign the certificate with a command such as: <pre class="literal-block"> openssl ca -out mycert.crt -in mycert.csr </pre> Now copy the certificate (mycert.crt) back to the peer which initially generated the .csr file (this can be over a public medium). Note that the openssl ca command reads the location of the certificate authority key from its configuration file such as <code>/usr/share/ssl/openssl.cnf</code> -- note also that for certificate authority functions, you must set up the files <code>index.txt</code> (may be empty) and <code>serial</code> (initialize to <code>01</code>). <h2 id="cipher"><a href="#cipher">cipher</a></h2> Syntax: <code>cipher <var>alg</var></code> This option should not be used any longer in TLS mode and still exists for two reasons: compatibility with old configurations still carrying it around; allow users connecting to OpenVPN peers older than 2.6.0 to have cipher configured the same way as the remote counterpart. This can avoid MTU/frame size warnings. Before 2.4.0, this option was used to select the cipher to be configured on the data channel, however, later versions usually ignored this directive in favour of a negotiated cipher. Starting with 2.6.0, this option is always ignored in TLS mode when it comes to configuring the cipher and will only control the cipher for <a href="#secret">secret</a> pre-shared-key mode (note: this mode is deprecated and strictly not recommended). If you wish to specify the cipher to use on the data channel, please see <a href="#data-ciphers">data-ciphers</a> (for regular negotiation) and <a href="#data-ciphers-fallback">data-ciphers-fallback</a> (for a fallback option when the negotiation cannot take place because the other peer is old or has negotiation disabled). To see ciphers that are available with OpenVPN, use the show-ciphers option. Set alg to <code>none</code> to disable encryption. <h2 id="client-nat"><a href="#client-nat">client-nat</a></h2> Syntax: <code>client-nat <var>args</var></code> This pushable client option sets up a stateless one-to-one NAT rule on packet addresses (not ports), and is useful in cases where routes or ifconfig settings pushed to the client would create an IP numbering conflict. Examples: <pre class="literal-block"> client-nat snat 192.168.0.0/255.255.0.0 client-nat dnat 10.64.0.0/255.255.0.0 </pre> network/netmask (for example <code>192.168.0.0/255.255.0.0</code>) defines the local view of a resource from the client perspective, while alias/netmask (for example <code>10.64.0.0/255.255.0.0</code>) defines the remote view from the server perspective. Use <code>snat</code> (source NAT) for resources owned by the client and <code>dnat</code> (destination NAT) for remote resources. Set <a href="#verb">verb</a> 6 for debugging info showing the transformation of src/dest addresses in packets. <h2 id="comp-lzo"><a href="#comp-lzo">comp-lzo</a></h2> Syntax: <code>comp-lzo <var>mode</var></code> DEPRECATED Enable LZO compression algorithm. Compression is generally not recommended. VPN tunnels which uses compression are suspectible to the VORALCE attack vector. Use LZO compression -- may add up to 1 byte per packet for incompressible data. mode may be <code>yes</code>, <code>no</code>, or <code>adaptive</code> (default). In a server mode setup, it is possible to selectively turn compression on or off for individual clients. First, make sure the client-side config file enables selective compression by having at least one comp-lzo directive, such as comp-lzo no. This will turn off compression by default, but allow a future directive push from the server to dynamically change the <code>on</code>/<code>off</code>/<code>adaptive</code> setting. Next in a client-config-dir file, specify the compression setting for the client, for example: <pre class="literal-block"> comp-lzo yes push "comp-lzo yes" </pre> The first line sets the comp-lzo setting for the server side of the link, the second sets the client side. <h2 id="comp-noadapt"><a href="#comp-noadapt">comp-noadapt</a></h2> Syntax: <code>comp-noadapt</code> DEPRECATED When used in conjunction with <a href="#comp-lzo">comp-lzo</a>, this option will disable OpenVPN's adaptive compression algorithm. Normally, adaptive compression is enabled with <a href="#comp-lzo">comp-lzo</a>. Adaptive compression tries to optimize the case where you have compression enabled, but you are sending predominantly incompressible (or pre-compressed) packets over the tunnel, such as an FTP or rsync transfer of a large, compressed file. With adaptive compression, OpenVPN will periodically sample the compression process to measure its efficiency. If the data being sent over the tunnel is already compressed, the compression efficiency will be very low, triggering openvpn to disable compression for a period of time until the next re-sample test. <h2 id="compat-mode"><a href="#compat-mode">compat-mode</a></h2> Syntax: <code>compat-mode <var>version</var></code> This option provides a convenient way to alter the defaults of OpenVPN to be more compatible with the version version specified. All of the changes this option applies can also be achieved using individual configuration options. The version specified with this option is the version of OpenVPN peer OpenVPN should try to be compatible with. In general OpenVPN should be compatible with the last two previous version without this option. E.g. OpenVPN 2.6.0 should be compatible with 2.5.x and 2.4.x without this option. However, there might be some edge cases that still require this option even in these cases. Note: Using this option reverts defaults to no longer recommended values and should be avoided if possible. The following table details what defaults are changed depending on the version specified. 2.5.x or lower: <a href="#allow-compression">allow-compression</a> asym is automatically added to the configuration if no other compression options are present. 2.4.x or lower: The cipher in <a href="#cipher">cipher</a> is appended to <a href="#data-ciphers">data-ciphers</a>. 2.3.x or lower: data-cipher-fallback is automatically added with the same cipher as <a href="#cipher">cipher</a>. 2.3.6 or lower: <a href="#tls-version-min">tls-version-min</a> 1.0 is added to the configuration when <a href="#tls-version-min">tls-version-min</a> is not explicitly set. If not required, this is option should be avoided. Setting this option can lower security or disable features like data-channel offloading. <h2 id="compress"><a href="#compress">compress</a></h2> Syntax: <code>compress <var>algorithm</var></code> DEPRECATED Enable a compression algorithm. Compression is generally not recommended. VPN tunnels which use compression are susceptible to the VORALCE attack vector. See also the <code>migrate</code> parameter below. The algorithm parameter may be <code>lzo</code>, <code>lz4</code>, <code>lz4-v2</code>, <code>stub</code>, <code>stub-v2</code>, <code>migrate</code> or empty. LZO and LZ4 are different compression algorithms, with LZ4 generally offering the best performance with least CPU usage. The <code>lz4-v2</code> and <code>stub-v2</code> variants implement a better framing that does not add overhead when packets cannot be compressed. All other variants always add one extra framing byte compared to no compression framing. Especially <code>stub-v2</code> is essentially identical to no compression and no compression framing as its header indicates IP version 5 in a tun setup and can (ab)used to complete disable compression to clients. (See the <code>migrate</code> option below) If the algorithm parameter is <code>stub</code>, <code>stub-v2</code> or empty, compression will be turned off, but the packet framing for compression will still be enabled, allowing a different setting to be pushed later. Additionally, <code>stub</code> and <code>stub-v2</code> wil disable announcing lzo and lz4 compression support via IV_ variables to the server. Note: the <code>stub</code> (or empty) option is NOT compatible with the older option <a href="#comp-lzo">comp-lzo</a> no. Using <code>migrate</code> as compression algorithm enables a special migration mode. It allows migration away from the --compress/<a href="#comp-lzo">comp-lzo</a> options to no compression. This option sets the server to no compression mode and the server behaves identical to a server without a compression option for all clients without a compression in their config. However, if a client is detected that indicates that compression is used (via OCC), the server will automatically add <a href="#push">push</a> compress stub-v2 to the client specific configuration if supported by the client and otherwise switch to comp-lzo no and add <a href="#push">push</a> comp-lzo to the client specific configuration. Security Considerations: Compression and encryption is a tricky combination. If an attacker knows or is able to control (parts of) the plain-text of packets that contain secrets, the attacker might be able to extract the secret if compression is enabled. See e.g. the CRIME and BREACH attacks on TLS and VORACLE on VPNs which also leverage to break encryption. If you are not entirely sure that the above does not apply to your traffic, you are advised to not enable compression. <h2 id="connect-retry"><a href="#connect-retry">connect-retry</a></h2> Syntax: <code>connect-retry <var>args</var></code> Wait n seconds between connection attempts (default <code>1</code>). Repeated reconnection attempts are slowed down after 5 retries per remote by doubling the wait time after each unsuccessful attempt. Valid syntaxes: <pre class="literal-block"> connect retry n connect retry n max </pre> If the optional argument max is specified, the maximum wait time in seconds gets capped at that value (default <code>300</code>). <h2 id="connect-retry-max"><a href="#connect-retry-max">connect-retry-max</a></h2> Syntax: <code>connect-retry-max <var>n</var></code> n specifies the number of times each <a href="#remote">remote</a> or <connection> entry is tried. Specifying n as <code>1</code> would try each entry exactly once. A successful connection resets the counter. (default unlimited). <h2 id="connect-timeout"><a href="#connect-timeout">connect-timeout</a></h2> Syntax: <code>connect-timeout <var>n</var></code> See <a href="#server-poll-timeout">server-poll-timeout</a>. <h2 id="crl-verify"><a href="#crl-verify">crl-verify</a></h2> Syntax: <code>crl-verify <var>args</var></code> Check peer certificate against a Certificate Revocation List. Valid syntax: <pre class="literal-block"> crl-verify file/directory flag </pre> Examples: <pre class="literal-block"> crl-verify crl-file.pem crl-verify /etc/openvpn/crls dir </pre> A CRL (certificate revocation list) is used when a particular key is compromised but when the overall PKI is still intact. Suppose you had a PKI consisting of a CA, root certificate, and a number of client certificates. Suppose a laptop computer containing a client key and certificate was stolen. By adding the stolen certificate to the CRL file, you could reject any connection which attempts to use it, while preserving the overall integrity of the PKI. The only time when it would be necessary to rebuild the entire PKI from scratch would be if the root certificate key itself was compromised. The option is not mandatory - if the relevant CRL is missing, OpenVPN will log a warning in the logs - e.g. <pre class="literal-block"> VERIFY WARNING: depth=0, unable to get certificate CRL </pre> but the connection will be allowed. If the optional <code>dir</code> flag is specified, enable a different mode where the crl-verify is pointed at a directory containing files named as revoked serial numbers (the files may be empty, the contents are never read). If a client requests a connection, where the client certificate serial number (decimal string) is the name of a file present in the directory, it will be rejected. Note: As the crl file (or directory) is read every time a peer connects, if you are dropping root privileges with user, make sure that this user has sufficient privileges to read the file. <h2 id="cryptoapicert"><a href="#cryptoapicert">cryptoapicert</a></h2> Syntax: <code>cryptoapicert <var>select-string</var></code> (Windows/OpenSSL Only) Load the certificate and private key from the Windows Certificate System Store. Use this option instead of <a href="#cert">cert</a> and <a href="#key">key</a>. This makes it possible to use any smart card, supported by Windows, but also any kind of certificate, residing in the Cert Store, where you have access to the private key. This option has been tested with a couple of different smart cards (GemSAFE, Cryptoflex, and Swedish Post Office eID) on the client side, and also an imported PKCS12 software certificate on the server side. To select a certificate, based on a substring search in the certificate's subject: <pre class="literal-block"> cryptoapicert "SUBJ:Peter Runestig" </pre> To select a certificate, based on certificate's thumbprint (SHA1 hash): <pre class="literal-block"> cryptoapicert "THUMB:f6 49 24 41 01 b4 ..." </pre> The thumbprint hex string can easily be copy-and-pasted from the Windows Certificate Store GUI. The embedded spaces in the hex string are optional. To select a certificate based on a substring in certificate's issuer name: <pre class="literal-block"> cryptoapicert "ISSUER:Sample CA" </pre> The first non-expired certificate found in the user's store or the machine store that matches the select-string is used. <h2 id="data-ciphers"><a href="#data-ciphers">data-ciphers</a></h2> Syntax: <code>data-ciphers <var>cipher-list</var></code> Restrict the allowed ciphers to be negotiated to the ciphers in cipher-list. cipher-list is a colon-separated list of ciphers, and defaults to <code>AES-256-GCM:AES-128-GCM:CHACHA20-POLY1305</code> when Chacha20-Poly1305 is available and otherwise <code>AES-256-GCM:AES-128-GCM</code>. For servers, the first cipher from cipher-list that is also supported by the client will be pushed to clients that support cipher negotiation. For more details see the chapter on Data channel cipher negotiation. Especially if you need to support clients with OpenVPN versions older than 2.4! Starting with OpenVPN 2.6 a cipher can be prefixed with a <code>?</code> to mark it as optional. This allows including ciphers in the list that may not be available on all platforms. E.g. <code>AES-256-GCM:AES-128-GCM:?CHACHA20-POLY1305</code> would only enable Chacha20-Poly1305 if the underlying SSL library (and its configuration) supports it. Cipher negotiation is enabled in client-server mode only. I.e. if mode is set to server (server-side, implied by setting server ), or if <a href="#pull">pull</a> is specified (client-side, implied by setting --client). If no common cipher is found during cipher negotiation, the connection is terminated. To support old clients/old servers that do not provide any cipher negotiation support see <a href="#data-ciphers-fallback">data-ciphers-fallback</a>. If <a href="#compat-mode">compat-mode</a> is set to a version older than 2.5.0 the cipher specified by <a href="#cipher">cipher</a> will be appended to data-ciphers if not already present. This list is restricted to be 127 chars long after conversion to OpenVPN ciphers. This option was called ncp-ciphers in OpenVPN 2.4 but has been renamed to data-ciphers in OpenVPN 2.5 to more accurately reflect its meaning. <h2 id="data-ciphers-fallback"><a href="#data-ciphers-fallback">data-ciphers-fallback</a></h2> Syntax: <code>data-ciphers-fallback <var>alg</var></code> Configure a cipher that is used to fall back to if we could not determine which cipher the peer is willing to use. This option should only be needed to connect to peers that are running OpenVPN 2.3 or older versions, and have been configured with enable-small (typically used on routers or other embedded devices). <h2 id="dhcp-option"><a href="#dhcp-option">dhcp-option</a></h2> Syntax: <code>dhcp-option <var>args</var></code> Set additional network parameters on supported platforms. May be specified on the client or pushed from the server. On Windows these options are handled by the tap-windows6 driver by default or directly by OpenVPN if dhcp is disabled or the wintun driver is in use. The OpenVPN for Android client also handles them internally. On all other platforms these options are only saved in the client's environment under the name <code>foreign_option_{n}</code> before the <a href="#up">up</a> script is called. A plugin or an <a href="#up">up</a> script must be used to pick up and interpret these as required. Many Linux distributions include such scripts and some third-party user interfaces such as tunnelblick also come with scripts that process these options. Valid syntax: <pre class="literal-block"> dhcp-option type [parm] </pre> <code>DOMAIN</code> name Set Connection-specific DNS Suffix to <code>name</code>. <code>ADAPTER_DOMAIN_SUFFIX</code> name Alias to <code>DOMAIN</code>. This is a compatibility option, it should not be used in new deployments. <code>DOMAIN-SEARCH</code> name Add <code>name</code> to the domain search list. Repeat this option to add more entries. Up to 10 domains are supported. <code>DNS</code> address Set primary domain name server IPv4 or IPv6 address. Repeat this option to set secondary DNS server addresses. Note: DNS IPv6 servers are currently set using netsh (the existing DHCP code can only do IPv4 DHCP, and that protocol only permits IPv4 addresses anywhere). The option will be put into the environment, so an <a href="#up">up</a> script could act upon it if needed. <code>WINS</code> address Set primary WINS server address (NetBIOS over TCP/IP Name Server). Repeat this option to set secondary WINS server addresses. <code>NBDD</code> address Set primary NBDD server address (NetBIOS over TCP/IP Datagram Distribution Server). Repeat this option to set secondary NBDD server addresses. <code>NTP</code> address Set primary NTP server address (Network Time Protocol). Repeat this option to set secondary NTP server addresses. <code>NBT</code> type Set NetBIOS over TCP/IP Node type. Possible options: <code>1</code> b-node (broadcasts) <code>2</code> p-node (point-to-point name queries to a WINS server) <code>4</code> m-node (broadcast then query name server) <code>8</code> h-node (query name server, then broadcast). <code>NBS</code> scope-id Set NetBIOS over TCP/IP Scope. A NetBIOS Scope ID provides an extended naming service for the NetBIOS over TCP/IP (Known as NBT) module. The primary purpose of a NetBIOS scope ID is to isolate NetBIOS traffic on a single network to only those nodes with the same NetBIOS scope ID. The NetBIOS scope ID is a character string that is appended to the NetBIOS name. The NetBIOS scope ID on two hosts must match, or the two hosts will not be able to communicate. The NetBIOS Scope ID also allows computers to use the same computer name, as they have different scope IDs. The Scope ID becomes a part of the NetBIOS name, making the name unique. (This description of NetBIOS scopes courtesy of NeonSurge@abyss.com) <code>DISABLE-NBT</code> Disable Netbios-over-TCP/IP. <code>PROXY_HTTP</code> host port Sets a HTTP proxy that should be used when connected to the VPN. This option currently only works on OpenVPN for Android and requires Android 10 or later. <h2 id="dhcp-release"><a href="#dhcp-release">dhcp-release</a></h2> Syntax: <code>dhcp-release</code> Ask Windows to release the TAP adapter lease on shutdown. This option has no effect now, as it is enabled by default starting with OpenVPN 2.4.1. <h2 id="dhcp-renew"><a href="#dhcp-renew">dhcp-renew</a></h2> Syntax: <code>dhcp-renew</code> Ask Windows to renew the TAP adapter lease on startup. This option is normally unnecessary, as Windows automatically triggers a DHCP renegotiation on the TAP adapter when it comes up, however if you set the TAP-Win32 adapter Media Status property to "Always Connected", you may need this flag. <h2 id="disable-occ"><a href="#disable-occ">disable-occ</a></h2> Syntax: <code>disable-occ</code> DEPRECATED Disable "options consistency check" (OCC) in configurations that do not use TLS. Don't output a warning message if option inconsistencies are detected between peers. An example of an option inconsistency would be where one peer uses dev tun while the other peer uses dev tap. Use of this option is discouraged, but is provided as a temporary fix in situations where a recent version of OpenVPN must connect to an old version. <h2 id="dns"><a href="#dns">dns</a></h2> Syntax: <code>dns <var>args</var></code> Client DNS configuration to be used with the connection. Valid syntaxes: <pre class="literal-block"> dns search-domains domain [domain ...] dns server n address addr[:port] [addr[:port] ...] dns server n resolve-domains domain [domain ...] dns server n dnssec yes|optional|no dns server n transport DoH|DoT|plain dns server n sni server-name </pre> The dns search-domains directive takes one or more domain names to be added as DNS domain suffixes. If it is repeated multiple times within a configuration the domains are appended, thus e.g. domain names pushed by a server will amend locally defined ones. The dns server directive is used to configure DNS server n. The server id n must be a value between -128 and 127. For pushed DNS server options it must be between 0 and 127. The server id is used to group options and also for ordering the list of configured DNS servers; lower numbers come first. DNS servers being pushed to a client replace already configured DNS servers with the same server id. The address option configures the IPv4 and / or IPv6 address(es) of the DNS server. Up to eight addresses can be specified per DNS server. Optionally a port can be appended after a colon. IPv6 addresses need to be enclosed in brackets if a port is appended. The resolve-domains option takes one or more DNS domains used to define a split-dns or dns-routing setup, where only the given domains are resolved by the server. Systems which do not support fine grained DNS domain configuration will ignore this setting. The dnssec option is used to configure validation of DNSSEC records. While the exact semantics may differ for resolvers on different systems, yes likely makes validation mandatory, no disables it, and optional uses it opportunistically. The transport option enables DNS-over-HTTPS (DoH) or DNS-over-TLS (DoT) for a DNS server. The sni option can be used with them to specify the server-name for TLS server name indication. Each server has to have at least one address configured for a configuration to be valid. All the other options can be omitted. Note that not all options may be supported on all platforms. As soon support for different systems is implemented, information will be added here how unsupported options are treated. The dns option will eventually obsolete the <a href="#dhcp-option">dhcp-option</a> directive. Until then it will replace configuration at the places <a href="#dhcp-option">dhcp-option</a> puts it, so that dns overrides <a href="#dhcp-option">dhcp-option</a>. Thus, dns can be used today to migrate from <a href="#dhcp-option">dhcp-option</a>. <h2 id="down"><a href="#down">down</a></h2> Syntax: <code>down <var>cmd</var></code> Run command cmd after TUN/TAP device close (post user UID change and/or chroot ). cmd consists of a path to script (or executable program), optionally followed by arguments. The path and arguments may be single- or double-quoted and/or escaped using a backslash, and should be separated by one or more spaces. Called with the same parameters and environmental variables as the <a href="#up">up</a> option above. Note that if you reduce privileges by using user and/or group, your down script will also run at reduced privilege. <h2 id="down-pre"><a href="#down-pre">down-pre</a></h2> Syntax: <code>down-pre</code> Call <a href="#down">down</a> cmd/script before, rather than after, TUN/TAP close. <h2 id="ecdh-curve"><a href="#ecdh-curve">ecdh-curve</a></h2> Syntax: <code>ecdh-curve <var>name</var></code> Specify the curve to use for elliptic curve Diffie Hellman. Available curves can be listed with show-curves. The specified curve will only be used for ECDH TLS-ciphers. This option is not supported in mbed TLS builds of OpenVPN. <h2 id="echo"><a href="#echo">echo</a></h2> Syntax: <code>echo <var>parms</var></code> Echo parms to log output. Designed to be used to send messages to a controlling application which is receiving the OpenVPN log output. <h2 id="engine"><a href="#engine">engine</a></h2> Syntax: <code>engine <var>engine-name</var></code> Enable OpenSSL hardware-based crypto engine functionality. Valid syntaxes: <pre class="literal-block"> engine engine engine-name </pre> If engine-name is specified, use a specific crypto engine. Use the show-engines standalone option to list the crypto engines which are supported by OpenSSL. <h2 id="explicit-exit-notify"><a href="#explicit-exit-notify">explicit-exit-notify</a></h2> Syntax: <code>explicit-exit-notify <var>n</var></code> In UDP client mode or point-to-point mode, send server/peer an exit notification if tunnel is restarted or OpenVPN process is exited. In client mode, on exit/restart, this option will tell the server to immediately close its client instance object rather than waiting for a timeout. If both server and client support sending this message using the control channel, the message will be sent as control-channel message. Otherwise the message is sent as data-channel message, which will be ignored by data-channel offloaded peers. The n parameter (default <code>1</code> if not present) controls the maximum number of attempts that the client will try to resend the exit notification message if messages are sent in data-channel mode. In UDP server mode, send <code>RESTART</code> control channel command to connected clients. The n parameter (default <code>1</code> if not present) controls client behavior. With n = <code>1</code> client will attempt to reconnect to the same server, with n = <code>2</code> client will advance to the next server. OpenVPN will not send any exit notifications unless this option is enabled. <h2 id="extra-certs"><a href="#extra-certs">extra-certs</a></h2> Syntax: <code>extra-certs <var>file</var></code> Specify a file containing one or more PEM certs (concatenated together) that complete the local certificate chain. This option is useful for "split" CAs, where the CA for server certs is different than the CA for client certs. Putting certs in this file allows them to be used to complete the local certificate chain without trusting them to verify the peer-submitted certificate, as would be the case if the certs were placed in the ca file. <h2 id="fast-io"><a href="#fast-io">fast-io</a></h2> Syntax: <code>fast-io</code> (Experimental) Optimize TUN/TAP/UDP I/O writes by avoiding a call to poll/epoll/select prior to the write operation. The purpose of such a call would normally be to block until the device or socket is ready to accept the write. Such blocking is unnecessary on some platforms which don't support write blocking on UDP sockets or TUN/TAP devices. In such cases, one can optimize the event loop by avoiding the poll/epoll/select call, improving CPU efficiency by 5% to 10%. This option can only be used on non-Windows systems, when <a href="#proto">proto</a> udp is specified, and when <a href="#shaper">shaper</a> is NOT specified. <h2 id="float"><a href="#float">float</a></h2> Syntax: <code>float</code> Allow remote peer to change its IP address and/or port number, such as due to DHCP (this is the default if <a href="#remote">remote</a> is not used). float when specified with <a href="#remote">remote</a> allows an OpenVPN session to initially connect to a peer at a known address, however if packets arrive from a new address and pass all authentication tests, the new address will take control of the session. This is useful when you are connecting to a peer which holds a dynamic address such as a dial-in user or DHCP client. Essentially, float tells OpenVPN to accept authenticated packets from any address, not only the address which was specified in the <a href="#remote">remote</a> option. <h2 id="fragment"><a href="#fragment">fragment</a></h2> Syntax: <code>fragment <var>args</var></code> Valid syntax: <pre class="literal-block"> fragment max fragment max mtu </pre> Enable internal datagram fragmentation so that no UDP datagrams are sent which are larger than max bytes. If the <code>mtu</code> parameter is present the max parameter is interpreted to include IP and UDP encapsulation overhead. The <code>mtu</code> parameter is introduced in OpenVPN version 2.6.0. If the <code>mtu</code> parameter is absent, the max parameter is interpreted in the same way as the <a href="#link-mtu">link-mtu</a> parameter, i.e. the UDP packet size after encapsulation overhead has been added in, but not including the UDP header itself. The fragment option only makes sense when you are using the UDP protocol (<a href="#proto">proto</a> udp). fragment adds 4 bytes of overhead per datagram. See the <a href="#mssfix">mssfix</a> option below for an important related option to fragment. It should also be noted that this option is not meant to replace UDP fragmentation at the IP stack level. It is only meant as a last resort when path MTU discovery is broken. Using this option is less efficient than fixing path MTU discovery for your IP link and using native IP fragmentation instead. Having said that, there are circumstances where using OpenVPN's internal fragmentation capability may be your only option, such as tunneling a UDP multicast stream which requires fragmentation. <h2 id="hand-window"><a href="#hand-window">hand-window</a></h2> Syntax: <code>hand-window <var>n</var></code> Handshake Window -- the TLS-based key exchange must finalize within n seconds of handshake initiation by any peer (default <code>60</code> seconds). If the handshake fails we will attempt to reset our connection with our peer and try again. Even in the event of handshake failure we will still use our expiring key for up to <a href="#tran-window">tran-window</a> seconds to maintain continuity of transmission of tunnel data. The hand-window parameter also controls the amount of time that the OpenVPN client repeats the pull request until it times out. <h2 id="hash-size"><a href="#hash-size">hash-size</a></h2> Syntax: <code>hash-size <var>args</var></code> Set the size of the real address hash table to r and the virtual address table to v. Valid syntax: <pre class="literal-block"> hash-size r v </pre> By default, both tables are sized at 256 buckets. <h2 id="http-proxy"><a href="#http-proxy">http-proxy</a></h2> Syntax: <code>http-proxy <var>args</var></code> Connect to remote host through an HTTP proxy. This requires at least an address server and port argument. If HTTP Proxy-Authenticate is required, a file name to an authfile file containing a username and password on 2 lines can be given, or <code>stdin</code> to prompt from console. Its content can also be specified in the config file with the <a href="#http-proxy-user-pass">http-proxy-user-pass</a> option (See INLINE FILE SUPPORT). The last optional argument is an auth-method which should be one of <code>none</code>, <code>basic</code>, or <code>ntlm</code>. HTTP Digest authentication is supported as well, but only via the <code>auto</code> or <code>auto-nct</code> flags (below). This must replace the authfile argument. The <code>auto</code> flag causes OpenVPN to automatically determine the auth-method and query stdin or the management interface for username/password credentials, if required. This flag exists on OpenVPN 2.1 or higher. The auto-nct flag (no clear-text auth) instructs OpenVPN to automatically determine the authentication method, but to reject weak authentication protocols such as HTTP Basic Authentication. Examples: <pre class="last literal-block"> # no authentication http-proxy proxy.example.net 3128 # basic authentication, load credentials from file http-proxy proxy.example.net 3128 authfile.txt # basic authentication, ask user for credentials http-proxy proxy.example.net 3128 stdin # NTLM authentication, load credentials from file http-proxy proxy.example.net 3128 authfile.txt ntlm2 # determine which authentication is required, ask user for credentials http-proxy proxy.example.net 3128 auto # determine which authentication is required, but reject basic http-proxy proxy.example.net 3128 auto-nct # determine which authentication is required, but set credentials http-proxy proxy.example.net 3128 auto http-proxy-user-pass authfile.txt # basic authentication, specify credentials inline http-proxy proxy.example.net 3128 "" basic <http-proxy-user-pass> username password </http-proxy-user-pass> </pre> <h2 id="http-proxy-option"><a href="#http-proxy-option">http-proxy-option</a></h2> Syntax: <code>http-proxy-option <var>args</var></code> Set extended HTTP proxy options. Requires an option type as argument and an optional parameter to the type. Repeat to set multiple options. <code>VERSION</code> version Set HTTP version number to version (default <code>1.0</code>). <code>AGENT</code> user-agent Set HTTP "User-Agent" string to user-agent. <code>CUSTOM-HEADER</code> name content Adds the custom Header with name as name and content as the content of the custom HTTP header. Examples: <pre class="last literal-block"> http-proxy-option VERSION 1.1 http-proxy-option AGENT OpenVPN/2.4 http-proxy-option X-Proxy-Flag some-flags </pre> <h2 id="http-proxy-user-pass"><a href="#http-proxy-user-pass">http-proxy-user-pass</a></h2> Syntax: <code>http-proxy-user-pass <var>userpass</var></code> Overwrite the username/password information for <a href="#http-proxy">http-proxy</a>. If specified as an inline option (see INLINE FILE SUPPORT), it will be interpreted as username/password separated by a newline. When specified on the command line it is interpreted as a filename same as the third argument to <a href="#http-proxy">http-proxy</a>. Example: <pre class="last literal-block"> <http-proxy-user-pass> username password </http-proxy-user-pass> </pre> <h2 id="ifconfig"><a href="#ifconfig">ifconfig</a></h2> Syntax: <code>ifconfig <var>args</var></code> Set TUN/TAP adapter parameters. It requires the IP address of the local VPN endpoint. For TUN devices in point-to-point mode, the next argument must be the VPN IP address of the remote VPN endpoint. For TAP devices, or TUN devices used with <a href="#topology">topology</a> subnet, the second argument is the subnet mask of the virtual network segment which is being created or connected to. For TUN devices, which facilitate virtual point-to-point IP connections (when used in <a href="#topology">topology</a> net30 or p2p mode), the proper usage of ifconfig is to use two private IP addresses which are not a member of any existing subnet which is in use. The IP addresses may be consecutive and should have their order reversed on the remote peer. After the VPN is established, by pinging rn, you will be pinging across the VPN. For TAP devices, which provide the ability to create virtual ethernet segments, or TUN devices in <a href="#topology">topology</a> subnet mode (which create virtual "multipoint networks"), ifconfig is used to set an IP address and subnet mask just as a physical ethernet adapter would be similarly configured. If you are attempting to connect to a remote ethernet bridge, the IP address and subnet should be set to values which would be valid on the the bridged ethernet segment (note also that DHCP can be used for the same purpose). This option, while primarily a proxy for the ifconfig(8) command, is designed to simplify TUN/TAP tunnel configuration by providing a standard interface to the different ifconfig implementations on different platforms. ifconfig parameters which are IP addresses can also be specified as a DNS or /etc/hosts file resolvable name. For TAP devices, ifconfig should not be used if the TAP interface will be getting an IP address lease from a DHCP server. Examples: <pre class="last literal-block"> # tun device in net30/p2p mode ifconfig 10.8.0.2 10.8.0.1 # tun/tap device in subnet mode ifconfig 10.8.0.2 255.255.255.0 </pre> <h2 id="ifconfig-ipv6"><a href="#ifconfig-ipv6">ifconfig-ipv6</a></h2> Syntax: <code>ifconfig-ipv6 <var>args</var></code> Configure an IPv6 address on the tun device. Valid syntax: <pre class="literal-block"> ifconfig-ipv6 ipv6addr/bits [ipv6remote] </pre> The ipv6addr/bits argument is the IPv6 address to use. The second parameter is used as route target for <a href="#route-ipv6">route-ipv6</a> if no gateway is specified. The <a href="#topology">topology</a> option has no influence with ifconfig-ipv6 <h2 id="ifconfig-noexec"><a href="#ifconfig-noexec">ifconfig-noexec</a></h2> Syntax: <code>ifconfig-noexec</code> Don't actually execute ifconfig/netsh commands, instead pass <a href="#ifconfig">ifconfig</a> parameters to scripts using environmental variables. <h2 id="ifconfig-nowarn"><a href="#ifconfig-nowarn">ifconfig-nowarn</a></h2> Syntax: <code>ifconfig-nowarn</code> Don't output an options consistency check warning if the <a href="#ifconfig">ifconfig</a> option on this side of the connection doesn't match the remote side. This is useful when you want to retain the overall benefits of the options consistency check (also see <a href="#disable-occ">disable-occ</a> option) while only disabling the ifconfig component of the check. For example, if you have a configuration where the local host uses <a href="#ifconfig">ifconfig</a> but the remote host does not, use ifconfig-nowarn on the local host. This option will also silence warnings about potential address conflicts which occasionally annoy more experienced users by triggering "false positive" warnings. <h2 id="ignore-unknown-option"><a href="#ignore-unknown-option">ignore-unknown-option</a></h2> Syntax: <code>ignore-unknown-option <var>args</var></code> Valid syntax: <pre class="literal-block"> ignore-unknown-options opt1 opt2 opt3 ... optN </pre> When one of options opt1 ... optN is encountered in the configuration file the configuration file parsing does not fail if this OpenVPN version does not support the option. Multiple ignore-unknown-option options can be given to support a larger number of options to ignore. This option should be used with caution, as there are good security reasons for having OpenVPN fail if it detects problems in a config file. Having said that, there are valid reasons for wanting new software features to gracefully degrade when encountered by older software versions. ignore-unknown-option is available since OpenVPN 2.3.3. <h2 id="inactive"><a href="#inactive">inactive</a></h2> Syntax: <code>inactive <var>args</var></code> Causes OpenVPN to exit after n seconds of inactivity on the TUN/TAP device. The time length of inactivity is measured since the last incoming or outgoing tunnel packet. The default value is 0 seconds, which disables this feature. Valid syntaxes: <pre class="literal-block"> inactive n inactive n bytes </pre> If the optional bytes parameter is included, exit if less than bytes of combined in/out traffic are produced on the tun/tap device in n seconds. In any case, OpenVPN's internal ping packets (which are just keepalives) and TLS control packets are not considered "activity", nor are they counted as traffic, as they are used internally by OpenVPN and are not an indication of actual user activity. <h2 id="ip-win32"><a href="#ip-win32">ip-win32</a></h2> Syntax: <code>ip-win32 <var>method</var></code> When using <a href="#ifconfig">ifconfig</a> on Windows, set the TAP-Win32 adapter IP address and netmask using method. Don't use this option unless you are also using <a href="#ifconfig">ifconfig</a>. <code>manual</code> Don't set the IP address or netmask automatically. Instead output a message to the console telling the user to configure the adapter manually and indicating the IP/netmask which OpenVPN expects the adapter to be set to. <code>dynamic [offset] [lease-time]</code> Automatically set the IP address and netmask by replying to DHCP query messages generated by the kernel. This mode is probably the "cleanest" solution for setting the TCP/IP properties since it uses the well-known DHCP protocol. There are, however, two prerequisites for using this mode: The TCP/IP properties for the TAP-Win32 adapter must be set to "Obtain an IP address automatically", and OpenVPN needs to claim an IP address in the subnet for use as the virtual DHCP server address. By default in dev tap mode, OpenVPN will take the normally unused first address in the subnet. For example, if your subnet is <code>192.168.4.0 netmask 255.255.255.0</code>, then OpenVPN will take the IP address <code>192.168.4.0</code> to use as the virtual DHCP server address. In dev tun mode, OpenVPN will cause the DHCP server to masquerade as if it were coming from the remote endpoint. The optional offset parameter is an integer which is > <code>-256</code> and < <code>256</code> and which defaults to 0. If offset is positive, the DHCP server will masquerade as the IP address at network address + offset. If offset is negative, the DHCP server will masquerade as the IP address at broadcast address + offset. The Windows <code>ipconfig /all</code> command can be used to show what Windows thinks the DHCP server address is. OpenVPN will "claim" this address, so make sure to use a free address. Having said that, different OpenVPN instantiations, including different ends of the same connection, can share the same virtual DHCP server address. The lease-time parameter controls the lease time of the DHCP assignment given to the TAP-Win32 adapter, and is denoted in seconds. Normally a very long lease time is preferred because it prevents routes involving the TAP-Win32 adapter from being lost when the system goes to sleep. The default lease time is one year. <code>netsh</code> Automatically set the IP address and netmask using the Windows command-line "netsh" command. This method appears to work correctly on Windows XP but not Windows 2000. <code>ipapi</code> Automatically set the IP address and netmask using the Windows IP Helper API. This approach does not have ideal semantics, though testing has indicated that it works okay in practice. If you use this option, it is best to leave the TCP/IP properties for the TAP-Win32 adapter in their default state, i.e. "Obtain an IP address automatically." <code>adaptive</code> (Default) Try <code>dynamic</code> method initially and fail over to <code>netsh</code> if the DHCP negotiation with the TAP-Win32 adapter does not succeed in 20 seconds. Such failures have been known to occur when certain third-party firewall packages installed on the client machine block the DHCP negotiation used by the TAP-Win32 adapter. Note that if the <code>netsh</code> failover occurs, the TAP-Win32 adapter TCP/IP properties will be reset from DHCP to static, and this will cause future OpenVPN startups using the <code>adaptive</code> mode to use <code>netsh</code> immediately, rather than trying <code>dynamic</code> first. To "unstick" the <code>adaptive</code> mode from using <code>netsh</code>, run OpenVPN at least once using the <code>dynamic</code> mode to restore the TAP-Win32 adapter TCP/IP properties to a DHCP configuration. <h2 id="ipchange"><a href="#ipchange">ipchange</a></h2> Syntax: <code>ipchange <var>cmd</var></code> Run command cmd when our remote ip-address is initially authenticated or changes. cmd consists of a path to a script (or executable program), optionally followed by arguments. The path and arguments may be single- or double-quoted and/or escaped using a backslash, and should be separated by one or more spaces. When cmd is executed two arguments are appended after any arguments specified in cmd , as follows: <pre class="literal-block"> cmd ip address port number </pre> Don't use ipchange in mode server mode. Use a client-connect script instead. See the Environmental Variables section below for additional parameters passed as environmental variables. If you are running in a dynamic IP address environment where the IP addresses of either peer could change without notice, you can use this script, for example, to edit the <code>/etc/hosts</code> file with the current address of the peer. The script will be run every time the remote peer changes its IP address. Similarly if our IP address changes due to DHCP, we should configure our IP address change script (see man page for dhcpcd(8)) to deliver a SIGHUP or SIGUSR1 signal to OpenVPN. OpenVPN will then re-establish a connection with its most recently authenticated peer on its new IP address. <h2 id="iproute"><a href="#iproute">iproute</a></h2> Syntax: <code>iproute <var>cmd</var></code> Set alternate command to execute instead of default iproute2 command. May be used in order to execute OpenVPN in unprivileged environment. <h2 id="keepalive"><a href="#keepalive">keepalive</a></h2> Syntax: <code>keepalive <var>args</var></code> A helper directive designed to simplify the expression of <a href="#ping">ping</a> and <a href="#ping-restart">ping-restart</a>. Valid syntax: <pre class="literal-block"> keepalive interval timeout </pre> Send ping once every interval seconds, restart if ping is not received for timeout seconds. This option can be used on both client and server side, but it is enough to add this on the server side as it will push appropriate <a href="#ping">ping</a> and <a href="#ping-restart">ping-restart</a> options to the client. If used on both server and client, the values pushed from server will override the client local values. The timeout argument will be twice as long on the server side. This ensures that a timeout is detected on client side before the server side drops the connection. For example, keepalive 10 60 expands as follows: <pre class="last literal-block"> if mode server: ping 10 # Argument: interval ping-restart 120 # Argument: timeout*2 push "ping 10" # Argument: interval push "ping-restart 60" # Argument: timeout else ping 10 # Argument: interval ping-restart 60 # Argument: timeout </pre> <h2 id="key"><a href="#key">key</a></h2> Syntax: <code>key <var>file</var></code> Local peer's private key in .pem format. Use the private key which was generated when you built your peer's certificate (see <a href="#cert">cert</a> file above). <h2 id="key-direction"><a href="#key-direction">key-direction</a></h2> Syntax: <code>key-direction</code> Alternative way of specifying the optional direction parameter for the <a href="#tls-auth">tls-auth</a> and <a href="#secret">secret</a> options. Useful when using inline files (See section on inline files). <h2 id="key-method"><a href="#key-method">key-method</a></h2> Syntax: <code>key-method</code> Removed in OpenVPN 2.5. This option should not be used, as using the old key-method weakens the VPN tunnel security. The old key-method was also only needed when the remote side was older than OpenVPN 2.0. <h2 id="link-mtu"><a href="#link-mtu">link-mtu</a></h2> Syntax: <code>link-mtu <var>n</var></code> DEPRECATED Sets an upper bound on the size of UDP packets which are sent between OpenVPN peers. It's best not to set this parameter unless you know what you're doing. Due to variable header size of IP header (20 bytes for IPv4 and 40 bytes for IPv6) and dynamically negotiated data channel cipher, this option is not reliable. It is recommended to set tun-mtu with enough headroom instead. <h2 id="lladdr"><a href="#lladdr">lladdr</a></h2> Syntax: <code>lladdr <var>address</var></code> Specify the link layer address, more commonly known as the MAC address. Only applied to TAP devices. <h2 id="local"><a href="#local">local</a></h2> Syntax: <code>local <var>host</var></code> Local host name or IP address for bind. If specified, OpenVPN will bind to this address only. If unspecified, OpenVPN will bind to all interfaces. <h2 id="lport"><a href="#lport">lport</a></h2> Syntax: <code>lport <var>port</var></code> Set local TCP/UDP port number or name. Cannot be used together with <a href="#nobind">nobind</a> option. <h2 id="mark"><a href="#mark">mark</a></h2> Syntax: <code>mark <var>value</var></code> Mark encrypted packets being sent with value. The mark value can be matched in policy routing and packetfilter rules. This option is only supported in Linux and does nothing on other operating systems. <h2 id="max-packet-size"><a href="#max-packet-size">max-packet-size</a></h2> Syntax: <code>max-packet-size <var>size</var></code> This option will instruct OpenVPN to try to limit the maximum on-write packet size by restricting the control channel packet size and setting <a href="#mssfix">mssfix</a>. OpenVPN will try to keep its control channel messages below this size but due to some constraints in the protocol this is not always possible. If the option is not set, the control packet maximum size defaults to 1250. The control channel packet size will be restricted to values between 154 and 2048. The maximum packet size includes encapsulation overhead like UDP and IP. In terms of <a href="#mssfix">mssfix</a> it will expand to: <pre class="literal-block"> mssfix size mtu </pre> If you need to set <a href="#mssfix">mssfix</a> for data channel and control channel maximum packet size independently, use max-packet-size first, followed by a <a href="#mssfix">mssfix</a> in the configuration. In general the default size of 1250 should work almost universally apart from specific corner cases, especially since IPv6 requires a MTU of 1280 or larger. <h2 id="mssfix"><a href="#mssfix">mssfix</a></h2> Syntax: <code>mssfix <var>args</var></code> Valid syntax: <pre class="literal-block"> mssfix max [mtu] mssfix max [fixed] mssfix </pre> Announce to TCP sessions running over the tunnel that they should limit their send packet sizes such that after OpenVPN has encapsulated them, the resulting UDP packet size that OpenVPN sends to its peer will not exceed max bytes. The default value is <code>1492 mtu</code>. Use <code>0</code> as max to disable mssfix. If the <code>mtu</code> parameter is specified the max value is interpreted as the resulting packet size of VPN packets including the IP and UDP header. Support for the <code>mtu</code> parameter was added with OpenVPN version 2.6.0. If the <code>mtu</code> parameter is not specified, the max parameter is interpreted in the same way as the <a href="#link-mtu">link-mtu</a> parameter, i.e. the UDP packet size after encapsulation overhead has been added in, but not including the UDP header itself. Resulting packet would be at most 28 bytes larger for IPv4 and 48 bytes for IPv6 (20/40 bytes for IP header and 8 bytes for UDP header). Default value of 1450 allows OpenVPN packets to be transmitted over IPv4 on a link with MTU 1478 or higher without IP level fragmentation (and 1498 for IPv6). If the <code>fixed</code> parameter is specified, OpenVPN will make no attempt to calculate the VPN encapsulation overhead but instead will set the MSS to limit the size of the payload IP packets to the specified number. IPv4 packets will have the MSS value lowered to mssfix - 40 and IPv6 packets to mssfix - 60. if mssfix is specified is specified without any parameter it inherits the parameters of <a href="#fragment">fragment</a> if specified or uses the default for mssfix otherwise. The mssfix option only makes sense when you are using the UDP protocol for OpenVPN peer-to-peer communication, i.e. <a href="#proto">proto</a> udp. mssfix and <a href="#fragment">fragment</a> can be ideally used together, where mssfix will try to keep TCP from needing packet fragmentation in the first place, and if big packets come through anyhow (from protocols other than TCP), <a href="#fragment">fragment</a> will internally fragment them. <a href="#max-packet-size">max-packet-size</a>, <a href="#fragment">fragment</a>, and mssfix are designed to work around cases where Path MTU discovery is broken on the network path between OpenVPN peers. The usual symptom of such a breakdown is an OpenVPN connection which successfully starts, but then stalls during active usage. If <a href="#fragment">fragment</a> and mssfix are used together, mssfix will take its default max parameter from the <a href="#fragment">fragment</a> max option. Therefore, one could lower the maximum UDP packet size to 1300 (a good first try for solving MTU-related connection problems) with the following options: <pre class="literal-block"> <a href="#tun-mtu">tun-mtu</a> 1500 <a href="#fragment">fragment</a> 1300 mssfix </pre> If the max-packet-size size option is used in the configuration it will also act as if mssfix size mtu was specified in the configuration. <h2 id="mtu-test"><a href="#mtu-test">mtu-test</a></h2> Syntax: <code>mtu-test</code> To empirically measure MTU on connection startup, add the mtu-test option to your configuration. OpenVPN will send ping packets of various sizes to the remote peer and measure the largest packets which were successfully received. The mtu-test process normally takes about 3 minutes to complete. <h2 id="mute"><a href="#mute">mute</a></h2> Syntax: <code>mute <var>n</var></code> Log at most n consecutive messages in the same category. This is useful to limit repetitive logging of similar message types. <h2 id="mute-replay-warnings"><a href="#mute-replay-warnings">mute-replay-warnings</a></h2> Syntax: <code>mute-replay-warnings</code> Silence the output of replay warnings, which are a common false alarm on WiFi networks. This option preserves the security of the replay protection code without the verbosity associated with warnings about duplicate packets. <h2 id="nobind"><a href="#nobind">nobind</a></h2> Syntax: <code>nobind</code> Do not bind to local address and port. The IP stack will allocate a dynamic port for returning packets. Since the value of the dynamic port could not be known in advance by a peer, this option is only suitable for peers which will be initiating connections by using the <a href="#remote">remote</a> option. <h2 id="ns-cert-type"><a href="#ns-cert-type">ns-cert-type</a></h2> Syntax: <code>ns-cert-type</code> Removed in OpenVPN 2.5. The nsCertType field is no longer supported in recent SSL/TLS libraries. If your certificates does not include key usage and extended key usage fields, they must be upgraded and the <a href="#remote-cert-tls">remote-cert-tls</a> option should be used instead. <h2 id="passtos"><a href="#passtos">passtos</a></h2> Syntax: <code>passtos</code> Set the TOS field of the tunnel packet to what the payload's TOS is. <h2 id="peer-fingerprint"><a href="#peer-fingerprint">peer-fingerprint</a></h2> Syntax: <code>peer-fingerprint <var>args</var></code> Specify a SHA256 fingerprint or list of SHA256 fingerprints to verify the peer certificate against. The peer certificate must match one of the fingerprint or certificate verification will fail. The option can also be inlined Valid syntax: <pre class="literal-block"> peer-fingerprint AD:B0:95:D8:09:... </pre> or inline: <pre class="literal-block"> <peer-fingerprint> 00:11:22:33:44:55:66:77:88:99:aa:bb:cc:dd:ee:ff:00:11:22:33:44:55:66:77:88:99:aa:bb:cc:dd:ee:ff 11:22:33:44:55:66:77:88:99:aa:bb:cc:dd:ee:ff:00:11:22:33:44:55:66:77:88:99:aa:bb:cc:dd:ee:ff:00 </peer-fingerprint> </pre> When the peer-fingerprint option is used, specifying a CA with <a href="#ca">ca</a> or <a href="#capath">capath</a> is optional. This allows the he peer-fingerprint to be used as alternative to a PKI with self-signed certificates for small setups. See the examples section for such a setup. <h2 id="persist-key"><a href="#persist-key">persist-key</a></h2> Syntax: <code>persist-key</code> Don't re-read key files across <code>SIGUSR1</code> or <a href="#ping-restart">ping-restart</a>. This option can be combined with user to allow restarts triggered by the <code>SIGUSR1</code> signal. Normally if you drop root privileges in OpenVPN, the daemon cannot be restarted since it will now be unable to re-read protected key files. This option solves the problem by persisting keys across <code>SIGUSR1</code> resets, so they don't need to be re-read. <h2 id="persist-local-ip"><a href="#persist-local-ip">persist-local-ip</a></h2> Syntax: <code>persist-local-ip</code> Preserve initially resolved local IP address and port number across SIGUSR1 or <a href="#ping-restart">ping-restart</a> restarts. <h2 id="persist-remote-ip"><a href="#persist-remote-ip">persist-remote-ip</a></h2> Syntax: <code>persist-remote-ip</code> Preserve most recently authenticated remote IP address and port number across <code>SIGUSR1</code> or <a href="#ping-restart">ping-restart</a> restarts. <h2 id="persist-tun"><a href="#persist-tun">persist-tun</a></h2> Syntax: <code>persist-tun</code> Don't close and reopen TUN/TAP device or run up/down scripts across <code>SIGUSR1</code> or <a href="#ping-restart">ping-restart</a> restarts. <code>SIGUSR1</code> is a restart signal similar to <code>SIGHUP</code>, but which offers finer-grained control over reset options. <h2 id="ping"><a href="#ping">ping</a></h2> Syntax: <code>ping <var>n</var></code> Ping remote over the TCP/UDP control channel if no packets have been sent for at least n seconds (specify ping on both peers to cause ping packets to be sent in both directions since OpenVPN ping packets are not echoed like IP ping packets). When used in one of OpenVPN's secure modes (where <a href="#secret">secret</a>, tls-server or <a href="#tls-client">tls-client</a> is specified), the ping packet will be cryptographically secure. This option has two intended uses: Compatibility with stateful firewalls. The periodic ping will ensure that a stateful firewall rule which allows OpenVPN UDP packets to pass will not time out. To provide a basis for the remote to test the existence of its peer using the <a href="#ping-exit">ping-exit</a> option. When using OpenVPN in server mode see also <a href="#keepalive">keepalive</a>. <h2 id="ping-exit"><a href="#ping-exit">ping-exit</a></h2> Syntax: <code>ping-exit <var>n</var></code> Causes OpenVPN to exit after n seconds pass without reception of a ping or other packet from remote. This option can be combined with <a href="#inactive">inactive</a>, <a href="#ping">ping</a> and ping-exit to create a two-tiered inactivity disconnect. For example, <pre class="literal-block"> openvpn [options...] <a href="#inactive">inactive</a> 3600 <a href="#ping">ping</a> 10 ping-exit 60 </pre> when used on both peers will cause OpenVPN to exit within 60 seconds if its peer disconnects, but will exit after one hour if no actual tunnel data is exchanged. <h2 id="ping-restart"><a href="#ping-restart">ping-restart</a></h2> Syntax: <code>ping-restart <var>n</var></code> Similar to <a href="#ping-exit">ping-exit</a>, but trigger a <code>SIGUSR1</code> restart after n seconds pass without reception of a ping or other packet from remote. This option is useful in cases where the remote peer has a dynamic IP address and a low-TTL DNS name is used to track the IP address using a service such as https://www.nsupdate.info/ + a dynamic DNS client such as ddclient. If the peer cannot be reached, a restart will be triggered, causing the hostname used with <a href="#remote">remote</a> to be re-resolved (if <a href="#resolv-retry">resolv-retry</a> is also specified). In server mode, ping-restart, <a href="#inactive">inactive</a> or any other type of internally generated signal will always be applied to individual client instance objects, never to whole server itself. Note also in server mode that any internally generated signal which would normally cause a restart, will cause the deletion of the client instance object instead. In client mode, the ping-restart parameter is set to 120 seconds by default. This default will hold until the client pulls a replacement value from the server, based on the <a href="#keepalive">keepalive</a> setting in the server configuration. To disable the 120 second default, set ping-restart 0 on the client. See the signals section below for more information on <code>SIGUSR1</code>. Note that the behavior of SIGUSR1 can be modified by the <a href="#persist-tun">persist-tun</a>, <a href="#persist-key">persist-key</a>, <a href="#persist-local-ip">persist-local-ip</a> and <a href="#persist-remote-ip">persist-remote-ip</a> options. Also note that <a href="#ping-exit">ping-exit</a> and ping-restart are mutually exclusive and cannot be used together. <h2 id="pkcs11-cert-private"><a href="#pkcs11-cert-private">pkcs11-cert-private</a></h2> Syntax: <code>pkcs11-cert-private <var>args</var></code> Set if access to certificate object should be performed after login. Every provider has its own setting. Valid syntaxes: <pre class="last literal-block"> pkcs11-cert-private 0 pkcs11-cert-private 1 </pre> <h2 id="pkcs11-id"><a href="#pkcs11-id">pkcs11-id</a></h2> Syntax: <code>pkcs11-id <var>name</var></code> Specify the serialized certificate id to be used. The id can be gotten by the standalone show-pkcs11-ids option. See also the description of <a href="#pkcs11-providers">pkcs11-providers</a> option. <h2 id="pkcs11-pin-cache"><a href="#pkcs11-pin-cache">pkcs11-pin-cache</a></h2> Syntax: <code>pkcs11-pin-cache <var>seconds</var></code> Specify how many seconds the PIN can be cached, the default is until the token is removed. <h2 id="pkcs11-private-mode"><a href="#pkcs11-private-mode">pkcs11-private-mode</a></h2> Syntax: <code>pkcs11-private-mode <var>mode</var></code> Specify which method to use in order to perform private key operations. A different mode can be specified for each provider. Mode is encoded as hex number, and can be a mask one of the following: <code>0</code> (default) Try to determine automatically. <code>1</code> Use sign. <code>2</code> Use sign recover. <code>4</code> Use decrypt. <code>8</code> Use unwrap. <h2 id="pkcs11-protected-authentication"><a href="#pkcs11-protected-authentication">pkcs11-protected-authentication</a></h2> Syntax: <code>pkcs11-protected-authentication <var>args</var></code> Use PKCS#11 protected authentication path, useful for biometric and external keypad devices. Every provider has its own setting. Valid syntaxes: <pre class="last literal-block"> pkcs11-protected-authentication 0 pkcs11-protected-authentication 1 </pre> <h2 id="pkcs11-providers"><a href="#pkcs11-providers">pkcs11-providers</a></h2> Syntax: <code>pkcs11-providers <var>providers</var></code> Specify an RSA Security Inc. PKCS #11 Cryptographic Token Interface (Cryptoki) providers to load. A space-separated list of one or more provider library names may be specified. This option along with <a href="#pkcs11-id">pkcs11-id</a> or pkcs11-id-management can be used instead of <a href="#cert">cert</a> and <a href="#key">key</a> or <a href="#pkcs12">pkcs12</a>. If p11-kit is present on the system and was enabled during build, its <code>p11-kit-proxy.so</code> module will be loaded by default if either the <a href="#pkcs11-id">pkcs11-id</a> or pkcs11-id-management options is present without pkcs11-providers. If default loading is not enabled in the build and no providers are specified, the former options will be ignored. <h2 id="pkcs12"><a href="#pkcs12">pkcs12</a></h2> Syntax: <code>pkcs12 <var>file</var></code> Specify a PKCS #12 file containing local private key, local certificate, and root CA certificate. This option can be used instead of <a href="#ca">ca</a>, <a href="#cert">cert</a>, and <a href="#key">key</a>. Not available with mbed TLS. <h2 id="port"><a href="#port">port</a></h2> Syntax: <code>port <var>port</var></code> TCP/UDP port number or port name for both local and remote (sets both <a href="#lport">lport</a> and <a href="#rport">rport</a> options to given port). The current default of 1194 represents the official IANA port number assignment for OpenVPN and has been used since version 2.0-beta17. Previous versions used port 5000 as the default. <h2 id="proto"><a href="#proto">proto</a></h2> Syntax: <code>proto <var>p</var></code> Use protocol p for communicating with remote host. p can be <code>udp</code>, <code>tcp-client</code>, or <code>tcp-server</code>. You can also limit OpenVPN to use only IPv4 or only IPv6 by specifying p as <code>udp4</code>, <code>tcp4-client</code>, <code>tcp4-server</code> or <code>udp6</code>, <code>tcp6-client</code>, <code>tcp6-server</code>, respectively. The default protocol is <code>udp</code> when proto is not specified. For UDP operation, proto udp should be specified on both peers. For TCP operation, one peer must use proto tcp-server and the other must use proto tcp-client. A peer started with <code>tcp-server</code> will wait indefinitely for an incoming connection. A peer started with <code>tcp-client</code> will attempt to connect, and if that fails, will sleep for 5 seconds (adjustable via the <a href="#connect-retry">connect-retry</a> option) and try again infinite or up to N retries (adjustable via the <a href="#connect-retry-max">connect-retry-max</a> option). Both TCP client and server will simulate a SIGUSR1 restart signal if either side resets the connection. OpenVPN is designed to operate optimally over UDP, but TCP capability is provided for situations where UDP cannot be used. In comparison with UDP, TCP will usually be somewhat less efficient and less robust when used over unreliable or congested networks. This article outlines some of problems with tunneling IP over TCP: http://sites.inka.de/sites/bigred/devel/tcp-tcp.html There are certain cases, however, where using TCP may be advantageous from a security and robustness perspective, such as tunneling non-IP or application-level UDP protocols, or tunneling protocols which don't possess a built-in reliability layer. <h2 id="proto-force"><a href="#proto-force">proto-force</a></h2> Syntax: <code>proto-force <var>p</var></code> When iterating through connection profiles, only consider profiles using protocol p (<code>tcp</code> | <code>udp</code>). Note that this specifically only filters by the transport layer protocol, i.e. UDP or TCP. This does not affect whether IPv4 or IPv6 is used as IP protocol. For implementation reasons the option accepts the <code>4</code> and <code>6</code> suffixes when specifying the protocol (i.e. <code>udp4</code> / <code>udp6</code> / <code>tcp4</code> / <code>tcp6</code>). However, these behave the same as without the suffix and should be avoided to prevent confusion. <h2 id="providers"><a href="#providers">providers</a></h2> Syntax: <code>providers <var>providers</var></code> Load the list of (OpenSSL) providers. This is mainly useful for using an external provider for key management like tpm2-openssl or to load the legacy provider with <pre class="literal-block"> providers legacy default </pre> Behaviour of changing this option between <code>SIGHUP</code> might not be well behaving. If you need to change/add/remove this option, fully restart OpenVPN. <h2 id="pull"><a href="#pull">pull</a></h2> Syntax: <code>pull</code> This option must be used on a client which is connecting to a multi-client server. It indicates to OpenVPN that it should accept options pushed by the server, provided they are part of the legal set of pushable options (note that the pull option is implied by client ). In particular, pull allows the server to push routes to the client, so you should not use pull or client in situations where you don't trust the server to have control over the client's routing table. <h2 id="pull-filter"><a href="#pull-filter">pull-filter</a></h2> Syntax: <code>pull-filter <var>args</var></code> Filter options on the client pushed by the server to the client. Valid syntaxes: <pre class="literal-block"> pull-filter accept text pull-filter ignore text pull-filter reject text </pre> Filter options received from the server if the option starts with <code>text</code>. The action flag <code>accept</code> allows the option, <code>ignore</code> removes it and <code>reject</code> flags an error and triggers a <code>SIGUSR1</code> restart. The filters may be specified multiple times, and each filter is applied in the order it is specified. The filtering of each option stops as soon as a match is found. Unmatched options are accepted by default. Prefix comparison is used to match <code>text</code> against the received option so that <pre class="literal-block"> pull-filter ignore "route" </pre> would remove all pushed options starting with route which would include, for example, route-gateway. Enclose text in quotes to embed spaces. <pre class="literal-block"> pull-filter accept "route 192.168.1." pull-filter ignore "route " </pre> would remove all routes that do not start with 192.168.1. Note that <code>reject</code> may result in a repeated cycle of failure and reconnect, unless multiple remotes are specified and connection to the next remote succeeds. To silently ignore an option pushed by the server, use <code>ignore</code>. <h2 id="push"><a href="#push">push</a></h2> Syntax: <code>push <var>option</var></code> Push a config file option back to the client for remote execution. Note that option must be enclosed in double quotes (<code>""</code>). The client must specify <a href="#pull">pull</a> in its config file. The set of options which can be pushed is limited by both feasibility and security. Some options such as those which would execute scripts are banned, since they would effectively allow a compromised server to execute arbitrary code on the client. Other options such as TLS or MTU parameters cannot be pushed because the client needs to know them before the connection to the server can be initiated. This is a partial list of options which can currently be pushed: <a href="#route">route</a>, <a href="#route-gateway">route-gateway</a>, <a href="#route-delay">route-delay</a>, <a href="#redirect-gateway">redirect-gateway</a>, <a href="#ip-win32">ip-win32</a>, <a href="#dhcp-option">dhcp-option</a>, <a href="#dns">dns</a>, <a href="#inactive">inactive</a>, <a href="#ping">ping</a>, <a href="#ping-exit">ping-exit</a>, <a href="#ping-restart">ping-restart</a>, <a href="#setenv">setenv</a>, auth-token, <a href="#persist-key">persist-key</a>, <a href="#persist-tun">persist-tun</a>, <a href="#echo">echo</a>, <a href="#comp-lzo">comp-lzo</a>, <a href="#socket-flags">socket-flags</a>, <a href="#sndbuf">sndbuf</a>, <a href="#rcvbuf">rcvbuf</a>, <a href="#session-timeout">session-timeout</a> <h2 id="push-peer-info"><a href="#push-peer-info">push-peer-info</a></h2> Syntax: <code>push-peer-info</code> Push additional information about the client to server. The following data is always pushed to the server: <code>IV_VER=<version></code> The client OpenVPN version <code>IV_PLAT=[linux|solaris|openbsd|mac|netbsd|freebsd|win]</code> The client OS platform <code>IV_PROTO</code> Details about protocol extensions that the peer supports. The variable is a bitfield and the bits are defined as follows: bit 0: Reserved, should always be zero bit 1: The peer supports peer-id floating mechanism bit 2: The client expects a push-reply and the server may send this reply without waiting for a push-request first. bit 3: The client is capable of doing key derivation using RFC5705 key material exporter. bit 4: The client is capable of accepting additional arguments to the AUTH_PENDING message. bit 5: The client supports doing feature negotiation in P2P mode bit 6: The client is capable of parsing and receiving the <a href="#dns">dns</a> pushed option bit 7: The client is capable of sending exit notification via control channel using EXIT message. Also, the client is accepting the protocol-flags pushed option for the EKM capability bit 8: The client is capable of accepting AUTH_FAILED,TEMP messages bit 9: The client is capable of dynamic tls-crypt <code>IV_NCP=2</code> Negotiable ciphers, client supports <a href="#cipher">cipher</a> pushed by the server, a value of 2 or greater indicates client supports AES-GCM-128 and AES-GCM-256. IV_NCP is deprecated in favor of IV_CIPHERS. <code>IV_CIPHERS=<data-ciphers></code> The client announces the list of supported ciphers configured with the <a href="#data-ciphers">data-ciphers</a> option to the server. <code>IV_MTU=<max_mtu></code> The client announces the support of pushable MTU and the maximum MTU it is willing to accept. <code>IV_GUI_VER=<gui_id> <version></code> The UI version of a UI if one is running, for example <code>de.blinkt.openvpn 0.5.47</code> for the Android app. This may be set by the client UI/GUI using <a href="#setenv">setenv</a>. <code>IV_SSO=[crtext,][openurl,][proxy_url]</code> Additional authentication methods supported by the client. This may be set by the client UI/GUI using <a href="#setenv">setenv</a>. The following flags depend on which compression formats are compiled in and whether compression is allowed by options. See Protocol options for more details. <code>IV_LZO=1</code> If client supports LZO compression. <code>IV_LZO_STUB=1</code> If client was built with LZO stub capability. This is only sent if IV_LZO=1 is not sent. This means the client can talk to a server configured with <a href="#comp-lzo">comp-lzo</a> no. <code>IV_LZ4=1</code> and <code>IV_LZ4v2=1</code> If the client supports LZ4 compression. <code>IV_COMP_STUB=1</code> and <code>IV_COMP_STUBv2=1</code> If the client supports stub compression. This means the client can talk to a server configured with <a href="#compress">compress</a>. When push-peer-info is enabled the additional information consists of the following data: <code>IV_HWADDR=<string></code> This is intended to be a unique and persistent ID of the client. The string value can be any readable ASCII string up to 64 bytes. OpenVPN 2.x and some other implementations use the MAC address of the client's interface used to reach the default gateway. If this string is generated by the client, it should be consistent and preserved across independent sessions and preferably re-installations and upgrades. <code>IV_SSL=<version string></code> The ssl library version used by the client, e.g. <code>OpenSSL 1.0.2f 28 Jan 2016</code>. <code>IV_PLAT_VER=x.y</code> The version of the operating system, e.g. 6.1 for Windows 7. This may be set by the client UI/GUI using <a href="#setenv">setenv</a>. On Windows systems it is automatically determined by openvpn itself. <code>UV_<name>=<value></code> Client environment variables whose names start with <code>UV_</code> <h2 id="rcvbuf"><a href="#rcvbuf">rcvbuf</a></h2> Syntax: <code>rcvbuf <var>size</var></code> Set the TCP/UDP socket receive buffer size. Defaults to operating system default. <h2 id="redirect-gateway"><a href="#redirect-gateway">redirect-gateway</a></h2> Syntax: <code>redirect-gateway <var>flags</var></code> Automatically execute routing commands to cause all outgoing IP traffic to be redirected over the VPN. This is a client-side option. This option performs three steps: Create a static route for the <a href="#remote">remote</a> address which forwards to the pre-existing default gateway. This is done so that (3) will not create a routing loop. Delete the default gateway route. Set the new default gateway to be the VPN endpoint address (derived either from <a href="#route-gateway">route-gateway</a> or the second parameter to <a href="#ifconfig">ifconfig</a> when dev tun is specified). When the tunnel is torn down, all of the above steps are reversed so that the original default route is restored. Option flags: <code>local</code> Add the <code>local</code> flag if both OpenVPN peers are directly connected via a common subnet, such as with wireless. The <code>local</code> flag will cause step (1) above to be omitted. <code>autolocal</code> Try to automatically determine whether to enable <code>local</code> flag above. <code>def1</code> Use this flag to override the default gateway by using <code>0.0.0.0/1</code> and <code>128.0.0.0/1</code> rather than <code>0.0.0.0/0</code>. This has the benefit of overriding but not wiping out the original default gateway. <code>bypass-dhcp</code> Add a direct route to the DHCP server (if it is non-local) which bypasses the tunnel (Available on Windows clients, may not be available on non-Windows clients). <code>bypass-dns</code> Add a direct route to the DNS server(s) (if they are non-local) which bypasses the tunnel (Available on Windows clients, may not be available on non-Windows clients). <code>block-local</code> Block access to local LAN when the tunnel is active, except for the LAN gateway itself. This is accomplished by routing the local LAN (except for the LAN gateway address) into the tunnel. <code>ipv6</code> Redirect IPv6 routing into the tunnel. This works similar to the <code>def1</code> flag, that is, more specific IPv6 routes are added (<code>2000::/4</code>, <code>3000::/4</code>), covering the whole IPv6 unicast space. <code>!ipv4</code> Do not redirect IPv4 traffic - typically used in the flag pair <code>ipv6 !ipv4</code> to redirect IPv6-only. <h2 id="redirect-private"><a href="#redirect-private">redirect-private</a></h2> Syntax: <code>redirect-private <var>flags</var></code> Like <a href="#redirect-gateway">redirect-gateway</a>, but omit actually changing the default gateway. Useful when pushing private subnets. <h2 id="register-dns"><a href="#register-dns">register-dns</a></h2> Syntax: <code>register-dns</code> Run <code>ipconfig /flushdns</code> and <code>ipconfig /registerdns</code> on connection initiation. This is known to kick Windows into recognizing pushed DNS servers. <h2 id="remap-usr1"><a href="#remap-usr1">remap-usr1</a></h2> Syntax: <code>remap-usr1 <var>signal</var></code> Control whether internally or externally generated <code>SIGUSR1</code> signals are remapped to <code>SIGHUP</code> (restart without persisting state) or <code>SIGTERM</code> (exit). signal can be set to <code>SIGHUP</code> or <code>SIGTERM</code>. By default, no remapping occurs. <h2 id="remote"><a href="#remote">remote</a></h2> Syntax: <code>remote <var>args</var></code> Remote host name or IP address, port and protocol. Valid syntaxes: <pre class="literal-block"> remote host remote host port remote host port proto </pre> The port and proto arguments are optional. The OpenVPN client will try to connect to a server at host:port. The proto argument indicates the protocol to use when connecting with the remote, and may be <code>tcp</code> or <code>udp</code>. To enforce IPv4 or IPv6 connections add a <code>4</code> or <code>6</code> suffix; like <code>udp4</code> / <code>udp6</code> / <code>tcp4</code> / <code>tcp6</code>. On the client, multiple remote options may be specified for redundancy, each referring to a different OpenVPN server, in the order specified by the list of remote options. Specifying multiple remote options for this purpose is a special case of the more general connection-profile feature. See the <connection> documentation below. The client will move on to the next host in the list, in the event of connection failure. Note that at any given time, the OpenVPN client will at most be connected to one server. Examples: <pre class="literal-block"> remote server1.example.net remote server1.example.net 1194 remote server2.example.net 1194 tcp </pre> Note: Since UDP is connectionless, connection failure is defined by the <a href="#ping">ping</a> and <a href="#ping-restart">ping-restart</a> options. Also, if you use multiple remote options, AND you are dropping root privileges on the client with user and/or group AND the client is running a non-Windows OS, if the client needs to switch to a different server, and that server pushes back different TUN/TAP or route settings, the client may lack the necessary privileges to close and reopen the TUN/TAP interface. This could cause the client to exit with a fatal error. If remote is unspecified, OpenVPN will listen for packets from any IP address, but will not act on those packets unless they pass all authentication tests. This requirement for authentication is binding on all potential peers, even those from known and supposedly trusted IP addresses (it is very easy to forge a source IP address on a UDP packet). When used in TCP mode, remote will act as a filter, rejecting connections from any host which does not match host. If host is a DNS name which resolves to multiple IP addresses, OpenVPN will try them in the order that the system getaddrinfo() presents them, so priorization and DNS randomization is done by the system library. Unless an IP version is forced by the protocol specification (4/6 suffix), OpenVPN will try both IPv4 and IPv6 addresses, in the order getaddrinfo() returns them. <h2 id="remote-cert-eku"><a href="#remote-cert-eku">remote-cert-eku</a></h2> Syntax: <code>remote-cert-eku <var>oid</var></code> Require that peer certificate was signed with an explicit extended key usage. This is a useful security option for clients, to ensure that the host they connect to is a designated server. The extended key usage should be encoded in oid notation, or OpenSSL symbolic representation. <h2 id="remote-cert-ku"><a href="#remote-cert-ku">remote-cert-ku</a></h2> Syntax: <code>remote-cert-ku <var>key-usage</var></code> Require that peer certificate was signed with an explicit key-usage. If present in the certificate, the <code>keyUsage</code> value is validated by the TLS library during the TLS handshake. Specifying this option without arguments requires this extension to be present (so the TLS library will verify it). If key-usage is a list of usage bits, the <code>keyUsage</code> field must have at least the same bits set as the bits in one of the values supplied in the key-usage list. The key-usage values in the list must be encoded in hex, e.g. <pre class="last literal-block"> remote-cert-ku a0 </pre> <h2 id="remote-cert-tls"><a href="#remote-cert-tls">remote-cert-tls</a></h2> Syntax: <code>remote-cert-tls <var>type</var></code> Require that peer certificate was signed with an explicit key usage and extended key usage based on RFC3280 TLS rules. Valid syntaxes: <pre class="literal-block"> remote-cert-tls server remote-cert-tls client </pre> This is a useful security option for clients, to ensure that the host they connect to is a designated server. Or the other way around; for a server to verify that only hosts with a client certificate can connect. The remote-cert-tls client option is equivalent to <pre class="literal-block"> remote-cert-ku remote-cert-eku "TLS Web Client Authentication" </pre> The remote-cert-tls server option is equivalent to <pre class="literal-block"> remote-cert-ku remote-cert-eku "TLS Web Server Authentication" </pre> This is an important security precaution to protect against a man-in-the-middle attack where an authorized client attempts to connect to another client by impersonating the server. The attack is easily prevented by having clients verify the server certificate using any one of remote-cert-tls, <a href="#verify-x509-name">verify-x509-name</a>, <a href="#peer-fingerprint">peer-fingerprint</a> or <a href="#tls-verify">tls-verify</a>. <h2 id="remote-random"><a href="#remote-random">remote-random</a></h2> Syntax: <code>remote-random</code> When multiple <a href="#remote">remote</a> address/ports are specified, or if connection profiles are being used, initially randomize the order of the list as a kind of basic load-balancing measure. <h2 id="remote-random-hostname"><a href="#remote-random-hostname">remote-random-hostname</a></h2> Syntax: <code>remote-random-hostname</code> Prepend a random string (6 bytes, 12 hex characters) to hostname to prevent DNS caching. For example, "foo.bar.gov" would be modified to "<random-chars>.foo.bar.gov". <h2 id="reneg-bytes"><a href="#reneg-bytes">reneg-bytes</a></h2> Syntax: <code>reneg-bytes <var>n</var></code> Renegotiate data channel key after n bytes sent or received (disabled by default with an exception, see below). OpenVPN allows the lifetime of a key to be expressed as a number of bytes encrypted/decrypted, a number of packets, or a number of seconds. A key renegotiation will be forced if any of these three criteria are met by either peer. If using ciphers with cipher block sizes less than 128-bits, reneg-bytes is set to 64MB by default, unless it is explicitly disabled by setting the value to <code>0</code>, but this is HIGHLY DISCOURAGED as this is designed to add some protection against the SWEET32 attack vector. For more information see the <a href="#cipher">cipher</a> option. <h2 id="reneg-pkts"><a href="#reneg-pkts">reneg-pkts</a></h2> Syntax: <code>reneg-pkts <var>n</var></code> Renegotiate data channel key after n packets sent and received (disabled by default). <h2 id="reneg-sec"><a href="#reneg-sec">reneg-sec</a></h2> Syntax: <code>reneg-sec <var>args</var></code> Renegotiate data channel key after at most max seconds (default <code>3600</code>) and at least min seconds (default is 90% of max for servers, and equal to max for clients). <pre class="literal-block"> reneg-sec max [min] </pre> The effective reneg-sec value used is per session pseudo-uniform-randomized between min and max. With the default value of <code>3600</code> this results in an effective per session value in the range of <code>3240</code> .. <code>3600</code> seconds for servers, or just 3600 for clients. When using dual-factor authentication, note that this default value may cause the end user to be challenged to reauthorize once per hour. Also, keep in mind that this option can be used on both the client and server, and whichever uses the lower value will be the one to trigger the renegotiation. A common mistake is to set reneg-sec to a higher value on either the client or server, while the other side of the connection is still using the default value of <code>3600</code> seconds, meaning that the renegotiation will still occur once per <code>3600</code> seconds. The solution is to increase reneg-sec on both the client and server, or set it to <code>0</code> on one side of the connection (to disable), and to your chosen value on the other side. <h2 id="replay-persist"><a href="#replay-persist">replay-persist</a></h2> Syntax: <code>replay-persist <var>file</var></code> Persist replay-protection state across sessions using file to save and reload the state. This option will keep a disk copy of the current replay protection state (i.e. the most recent packet timestamp and sequence number received from the remote peer), so that if an OpenVPN session is stopped and restarted, it will reject any replays of packets which were already received by the prior session. This option only makes sense when replay protection is enabled (the default) and you are using either <a href="#secret">secret</a> (shared-secret key mode) or TLS mode with <a href="#tls-auth">tls-auth</a>. <h2 id="replay-window"><a href="#replay-window">replay-window</a></h2> Syntax: <code>replay-window <var>args</var></code> Modify the replay protection sliding-window size and time window. Valid syntaxes: <pre class="literal-block"> replay-window n replay-window n t </pre> Use a replay protection sliding-window of size n and a time window of t seconds. By default n is <code>64</code> (the IPSec default) and t is <code>15</code> seconds. This option is only relevant in UDP mode, i.e. when either <a href="#proto">proto</a> udp is specified, or no <a href="#proto">proto</a> option is specified. When OpenVPN tunnels IP packets over UDP, there is the possibility that packets might be dropped or delivered out of order. Because OpenVPN, like IPSec, is emulating the physical network layer, it will accept an out-of-order packet sequence, and will deliver such packets in the same order they were received to the TCP/IP protocol stack, provided they satisfy several constraints. The packet cannot be a replay (unless no-replay is specified, which disables replay protection altogether). If a packet arrives out of order, it will only be accepted if the difference between its sequence number and the highest sequence number received so far is less than n. If a packet arrives out of order, it will only be accepted if it arrives no later than t seconds after any packet containing a higher sequence number. If you are using a network link with a large pipeline (meaning that the product of bandwidth and latency is high), you may want to use a larger value for n. Satellite links in particular often require this. If you run OpenVPN at <a href="#verb">verb</a> 4, you will see the message "PID_ERR replay-window backtrack occurred [x]" every time the maximum sequence number backtrack seen thus far increases. This can be used to calibrate n. There is some controversy on the appropriate method of handling packet reordering at the security layer. Namely, to what extent should the security layer protect the encapsulated protocol from attacks which masquerade as the kinds of normal packet loss and reordering that occur over IP networks? The IPSec and OpenVPN approach is to allow packet reordering within a certain fixed sequence number window. OpenVPN adds to the IPSec model by limiting the window size in time as well as sequence space. OpenVPN also adds TCP transport as an option (not offered by IPSec) in which case OpenVPN can adopt a very strict attitude towards message deletion and reordering: Don't allow it. Since TCP guarantees reliability, any packet loss or reordering event can be assumed to be an attack. In this sense, it could be argued that TCP tunnel transport is preferred when tunneling non-IP or UDP application protocols which might be vulnerable to a message deletion or reordering attack which falls within the normal operational parameters of IP networks. So I would make the statement that one should never tunnel a non-IP protocol or UDP application protocol over UDP, if the protocol might be vulnerable to a message deletion or reordering attack that falls within the normal operating parameters of what is to be expected from the physical IP layer. The problem is easily fixed by simply using TCP as the VPN transport layer. <h2 id="resolv-retry"><a href="#resolv-retry">resolv-retry</a></h2> Syntax: <code>resolv-retry <var>n</var></code> If hostname resolve fails for <a href="#remote">remote</a>, retry resolve for n seconds before failing. Set n to <code>infinite</code> to retry indefinitely. By default, resolv-retry infinite is enabled. You can disable by setting n=0. <h2 id="route"><a href="#route">route</a></h2> Syntax: <code>route <var>args</var></code> Add route to routing table after connection is established. Multiple routes can be specified. Routes will be automatically torn down in reverse order prior to TUN/TAP device close. Valid syntaxes: <pre class="literal-block"> route network/IP route network/IP netmask route network/IP netmask gateway route network/IP netmask gateway metric </pre> This option is intended as a convenience proxy for the route(8) shell command, while at the same time providing portable semantics across OpenVPN's platform space. netmask defaults to <code>255.255.255.255</code> when not given gateway default taken from <a href="#route-gateway">route-gateway</a> or the second parameter to <a href="#ifconfig">ifconfig</a> when dev tun is specified. metric default taken from <a href="#route-metric">route-metric</a> if set, otherwise <code>0</code>. The default can be specified by leaving an option blank or setting it to <code>default</code>. The network and gateway parameters can also be specified as a DNS or <code>/etc/hosts</code> file resolvable name, or as one of three special keywords: <code>vpn_gateway</code> The remote VPN endpoint address (derived either from <a href="#route-gateway">route-gateway</a> or the second parameter to <a href="#ifconfig">ifconfig</a> when dev tun is specified). <code>net_gateway</code> The pre-existing IP default gateway, read from the routing table (not supported on all OSes). <code>remote_host</code> The <a href="#remote">remote</a> address if OpenVPN is being run in client mode, and is undefined in server mode. <h2 id="route-delay"><a href="#route-delay">route-delay</a></h2> Syntax: <code>route-delay <var>args</var></code> Valid syntaxes: <pre class="literal-block"> route-delay route-delay n route-delay n w </pre> Delay n seconds (default <code>0</code>) after connection establishment, before adding routes. If n is <code>0</code>, routes will be added immediately upon connection establishment. If route-delay is omitted, routes will be added immediately after TUN/TAP device open and <a href="#up">up</a> script execution, before any user or group privilege downgrade (or chroot execution.) This option is designed to be useful in scenarios where DHCP is used to set tap adapter addresses. The delay will give the DHCP handshake time to complete before routes are added. On Windows, route-delay tries to be more intelligent by waiting w seconds (default <code>30</code>) for the TAP-Win32 adapter to come up before adding routes. <h2 id="route-gateway"><a href="#route-gateway">route-gateway</a></h2> Syntax: <code>route-gateway <var>arg</var></code> Specify a default gateway for use with <a href="#route">route</a>. If <code>dhcp</code> is specified as the parameter, the gateway address will be extracted from a DHCP negotiation with the OpenVPN server-side LAN. Valid syntaxes: <pre class="last literal-block"> route-gateway gateway route-gateway dhcp </pre> <h2 id="route-ipv6"><a href="#route-ipv6">route-ipv6</a></h2> Syntax: <code>route-ipv6 <var>args</var></code> Setup IPv6 routing in the system to send the specified IPv6 network into OpenVPN's tun. Valid syntax: <pre class="literal-block"> route-ipv6 ipv6addr/bits [gateway] [metric] </pre> The gateway parameter is only used for IPv6 routes across tap devices, and if missing, the ipv6remote field from <a href="#ifconfig-ipv6">ifconfig-ipv6</a> or <a href="#route-ipv6-gateway">route-ipv6-gateway</a> is used. <h2 id="route-ipv6-gateway"><a href="#route-ipv6-gateway">route-ipv6-gateway</a></h2> Syntax: <code>route-ipv6-gateway <var>gw</var></code> Specify a default gateway gw for use with <a href="#route-ipv6">route-ipv6</a>. <h2 id="route-method"><a href="#route-method">route-method</a></h2> Syntax: <code>route-method <var>m</var></code> Which method m to use for adding routes on Windows? <code>adaptive</code> (default) Try IP helper API first. If that fails, fall back to the route.exe shell command. <code>ipapi</code> Use IP helper API. <code>exe</code> Call the route.exe shell command. <h2 id="route-metric"><a href="#route-metric">route-metric</a></h2> Syntax: <code>route-metric <var>m</var></code> Specify a default metric m for use with <a href="#route">route</a>. <h2 id="route-nopull"><a href="#route-nopull">route-nopull</a></h2> Syntax: <code>route-nopull</code> When used with client or <a href="#pull">pull</a>, accept options pushed by server EXCEPT for routes, block-outside-dns and dhcp options like DNS servers. When used on the client, this option effectively bars the server from adding routes to the client's routing table, however note that this option still allows the server to set the TCP/IP properties of the client's TUN/TAP interface. <h2 id="route-pre-down"><a href="#route-pre-down">route-pre-down</a></h2> Syntax: <code>route-pre-down <var>cmd</var></code> Run command cmd before routes are removed upon disconnection. cmd consists of a path to a script (or executable program), optionally followed by arguments. The path and arguments may be single- or double-quoted and/or escaped using a backslash, and should be separated by one or more spaces. See the Environmental Variables section below for additional parameters passed as environmental variables. <h2 id="route-up"><a href="#route-up">route-up</a></h2> Syntax: <code>route-up <var>cmd</var></code> Run command cmd after routes are added, subject to <a href="#route-delay">route-delay</a>. cmd consists of a path to a script (or executable program), optionally followed by arguments. The path and arguments may be single- or double-quoted and/or escaped using a backslash, and should be separated by one or more spaces. See the Environmental Variables section below for additional parameters passed as environmental variables. <h2 id="rport"><a href="#rport">rport</a></h2> Syntax: <code>rport <var>port</var></code> Set TCP/UDP port number or name used by the <a href="#remote">remote</a> option. The port can also be set directly using the <a href="#remote">remote</a> option. <h2 id="script-security"><a href="#script-security">script-security</a></h2> Syntax: <code>script-security <var>level</var></code> This directive offers policy-level control over OpenVPN's usage of external programs and scripts. Lower level values are more restrictive, higher values are more permissive. Settings for level: <code>0</code> Strictly no calling of external programs. <code>1</code> (Default) Only call built-in executables such as ifconfig, ip, route, or netsh. <code>2</code> Allow calling of built-in executables and user-defined scripts. <code>3</code> Allow passwords to be passed to scripts via environmental variables (potentially unsafe). OpenVPN releases before v2.3 also supported a method flag which indicated how OpenVPN should call external commands and scripts. This could be either <code>execve</code> or <code>system</code>. As of OpenVPN 2.3, this flag is no longer accepted. In most *nix environments the execve() approach has been used without any issues. Some directives such as <a href="#up">up</a> allow options to be passed to the external script. In these cases make sure the script name does not contain any spaces or the configuration parser will choke because it can't determine where the script name ends and script options start. To run scripts in Windows in earlier OpenVPN versions you needed to either add a full path to the script interpreter which can parse the script or use the system flag to run these scripts. As of OpenVPN 2.3 it is now a strict requirement to have full path to the script interpreter when running non-executables files. This is not needed for executable files, such as .exe, .com, .bat or .cmd files. For example, if you have a Visual Basic script, you must use this syntax now: <pre class="literal-block"> <a href="#up">up</a> 'C:\\Windows\\System32\\wscript.exe C:\\Program\ Files\\OpenVPN\\config\\my-up-script.vbs' </pre> Please note the single quote marks and the escaping of the backslashes (\) and the space character. The reason the support for the <code>system</code> flag was removed is due to the security implications with shell expansions when executing scripts via the <code>system()</code> call. <h2 id="secret"><a href="#secret">secret</a></h2> Syntax: <code>secret <var>args</var></code> DEPRECATED Enable Static Key encryption mode (non-TLS). Use pre-shared secret file which was generated with genkey. Valid syntaxes: <pre class="literal-block"> secret file secret file direction </pre> The optional direction parameter enables the use of 4 distinct keys (HMAC-send, cipher-encrypt, HMAC-receive, cipher-decrypt), so that each data flow direction has a different set of HMAC and cipher keys. This has a number of desirable security properties including eliminating certain kinds of DoS and message replay attacks. When the direction parameter is omitted, 2 keys are used bidirectionally, one for HMAC and the other for encryption/decryption. The direction parameter should always be complementary on either side of the connection, i.e. one side should use <code>0</code> and the other should use <code>1</code>, or both sides should omit it altogether. The direction parameter requires that file contains a 2048 bit key. While pre-1.5 versions of OpenVPN generate 1024 bit key files, any version of OpenVPN which supports the direction parameter, will also support 2048 bit key file generation using the genkey option. Static key encryption mode has certain advantages, the primary being ease of configuration. There are no certificates or certificate authorities or complicated negotiation handshakes and protocols. The only requirement is that you have a pre-existing secure channel with your peer (such as ssh) to initially copy the key. This requirement, along with the fact that your key never changes unless you manually generate a new one, makes it somewhat less secure than TLS mode (see below). If an attacker manages to steal your key, everything that was ever encrypted with it is compromised. Contrast that to the perfect forward secrecy features of TLS mode (using Diffie Hellman key exchange), where even if an attacker was able to steal your private key, he would gain no information to help him decrypt past sessions. Another advantageous aspect of Static Key encryption mode is that it is a handshake-free protocol without any distinguishing signature or feature (such as a header or protocol handshake sequence) that would mark the ciphertext packets as being generated by OpenVPN. Anyone eavesdropping on the wire would see nothing but random-looking data. <h2 id="server-poll-timeout"><a href="#server-poll-timeout">server-poll-timeout</a></h2> Syntax: <code>server-poll-timeout <var>n</var></code> When connecting to a remote server do not wait for more than n seconds for a response before trying the next server. The default value is <code>120</code>. This timeout includes proxy and TCP connect timeouts. <h2 id="session-timeout"><a href="#session-timeout">session-timeout</a></h2> Syntax: <code>session-timeout <var>n</var></code> Raises <code>SIGTERM</code> for the client instance after n seconds since the beginning of the session, forcing OpenVPN to disconnect. In client mode, OpenVPN will disconnect and exit, while in server mode all client sessions are terminated. This option can also be specified in a client instance config file using client-config-dir or dynamically generated using a client-connect script. In these cases, only the related client session is terminated. <h2 id="setenv"><a href="#setenv">setenv</a></h2> Syntax: <code>setenv <var>args</var></code> Set a custom environmental variable <code>name=value</code> to pass to script. Valid syntaxes: <pre class="literal-block"> setenv name value setenv FORWARD_COMPATIBLE 1 setenv opt config_option </pre> By setting <code>FORWARD_COMPATIBLE</code> to <code>1</code>, the config file syntax checking is relaxed so that unknown directives will trigger a warning but not a fatal error, on the assumption that a given unknown directive might be valid in future OpenVPN versions. This option should be used with caution, as there are good security reasons for having OpenVPN fail if it detects problems in a config file. Having said that, there are valid reasons for wanting new software features to gracefully degrade when encountered by older software versions. It is also possible to tag a single directive so as not to trigger a fatal error if the directive isn't recognized. To do this, prepend the following before the directive: setenv opt Versions prior to OpenVPN 2.3.3 will always ignore options set with the setenv opt directive. See also <a href="#ignore-unknown-option">ignore-unknown-option</a> <h2 id="setenv-safe"><a href="#setenv-safe">setenv-safe</a></h2> Syntax: <code>setenv-safe <var>args</var></code> Set a custom environmental variable <code>OPENVPN_name</code> to <code>value</code> to pass to scripts. Valid syntaxes: <pre class="literal-block"> setenv-safe name value </pre> This directive is designed to be pushed by the server to clients, and the prepending of <code>OPENVPN_</code> to the environmental variable is a safety precaution to prevent a <code>LD_PRELOAD</code> style attack from a malicious or compromised server. <h2 id="shaper"><a href="#shaper">shaper</a></h2> Syntax: <code>shaper <var>n</var></code> Limit bandwidth of outgoing tunnel data to n bytes per second on the TCP/UDP port. Note that this will only work if mode is set to <code>p2p</code>. If you want to limit the bandwidth in both directions, use this option on both peers. OpenVPN uses the following algorithm to implement traffic shaping: Given a shaper rate of n bytes per second, after a datagram write of b bytes is queued on the TCP/UDP port, wait a minimum of (b / n) seconds before queuing the next write. It should be noted that OpenVPN supports multiple tunnels between the same two peers, allowing you to construct full-speed and reduced bandwidth tunnels at the same time, routing low-priority data such as off-site backups over the reduced bandwidth tunnel, and other data over the full-speed tunnel. Also note that for low bandwidth tunnels (under 1000 bytes per second), you should probably use lower MTU values as well (see above), otherwise the packet latency will grow so large as to trigger timeouts in the TLS layer and TCP connections running over the tunnel. OpenVPN allows n to be between 100 bytes/sec and 100 Mbytes/sec. <h2 id="single-session"><a href="#single-session">single-session</a></h2> Syntax: <code>single-session</code> After initially connecting to a remote peer, disallow any new connections. Using this option means that a remote peer cannot connect, disconnect, and then reconnect. If the daemon is reset by a signal or <a href="#ping-restart">ping-restart</a>, it will allow one new connection. single-session can be used with <a href="#ping-exit">ping-exit</a> or <a href="#inactive">inactive</a> to create a single dynamic session that will exit when finished. <h2 id="sndbuf"><a href="#sndbuf">sndbuf</a></h2> Syntax: <code>sndbuf <var>size</var></code> Set the TCP/UDP socket send buffer size. Defaults to operating system default. <h2 id="socket-flags"><a href="#socket-flags">socket-flags</a></h2> Syntax: <code>socket-flags <var>flags</var></code> Apply the given flags to the OpenVPN transport socket. Currently, only <code>TCP_NODELAY</code> is supported. The <code>TCP_NODELAY</code> socket flag is useful in TCP mode, and causes the kernel to send tunnel packets immediately over the TCP connection without trying to group several smaller packets into a larger packet. This can result in a considerably improvement in latency. This option is pushable from server to client, and should be used on both client and server for maximum effect. <h2 id="socks-proxy"><a href="#socks-proxy">socks-proxy</a></h2> Syntax: <code>socks-proxy <var>args</var></code> Connect to remote host through a Socks5 proxy. A required server argument is needed. Optionally a port (default <code>1080</code>) and authfile can be given. The authfile is a file containing a username and password on 2 lines, or <code>stdin</code> can be used to prompt from console. <h2 id="static-challenge"><a href="#static-challenge">static-challenge</a></h2> Syntax: <code>static-challenge <var>args</var></code> Enable static challenge/response protocol Valid syntax: <pre class="literal-block"> static-challenge text echo </pre> The text challenge text is presented to the user which describes what information is requested. The echo flag indicates if the user's input should be echoed on the screen. Valid echo values are <code>0</code> or <code>1</code>. See management-notes.txt in the OpenVPN distribution for a description of the OpenVPN challenge/response protocol. <h2 id="status"><a href="#status">status</a></h2> Syntax: <code>status <var>args</var></code> Write operational status to file every n seconds. n defaults to <code>60</code> if not specified. Valid syntaxes: <pre class="literal-block"> status file status file n </pre> Status can also be written to the syslog by sending a <code>SIGUSR2</code> signal. With multi-client capability enabled on a server, the status file includes a list of clients and a routing table. The output format can be controlled by the <a href="#status-version">status-version</a> option in that case. For clients or instances running in point-to-point mode, it will contain the traffic statistics. <h2 id="status-version"><a href="#status-version">status-version</a></h2> Syntax: <code>status-version <var>n</var></code> Set the status file format version number to n. This only affects the status file on servers with multi-client capability enabled. Valid status version values: <code>1</code> Traditional format (default). The client list contains the following fields comma-separated: Common Name, Real Address, Bytes Received, Bytes Sent, Connected Since. <code>2</code> A more reliable format for external processing. Compared to version <code>1</code>, the client list contains some additional fields: Virtual Address, Virtual IPv6 Address, Username, Client ID, Peer ID, Data Channel Cipher. Future versions may extend the number of fields. <code>3</code> Identical to <code>2</code>, but fields are tab-separated. <h2 id="tap-sleep"><a href="#tap-sleep">tap-sleep</a></h2> Syntax: <code>tap-sleep <var>n</var></code> Cause OpenVPN to sleep for n seconds immediately after the TAP-Win32 adapter state is set to "connected". This option is intended to be used to troubleshoot problems with the <a href="#ifconfig">ifconfig</a> and <a href="#ip-win32">ip-win32</a> options, and is used to give the TAP-Win32 adapter time to come up before Windows IP Helper API operations are applied to it. <h2 id="tcp-queue-limit"><a href="#tcp-queue-limit">tcp-queue-limit</a></h2> Syntax: <code>tcp-queue-limit <var>n</var></code> Maximum number of output packets queued before TCP (default <code>64</code>). When OpenVPN is tunneling data from a TUN/TAP device to a remote client over a TCP connection, it is possible that the TUN/TAP device might produce data at a faster rate than the TCP connection can support. When the number of output packets queued before sending to the TCP socket reaches this limit for a given client connection, OpenVPN will start to drop outgoing packets directed at this client. <h2 id="tls-auth"><a href="#tls-auth">tls-auth</a></h2> Syntax: <code>tls-auth <var>args</var></code> Add an additional layer of HMAC authentication on top of the TLS control channel to mitigate DoS attacks and attacks on the TLS stack. Valid syntaxes: <pre class="literal-block"> tls-auth file tls-auth file 0 tls-auth file 1 </pre> In a nutshell, tls-auth enables a kind of "HMAC firewall" on OpenVPN's TCP/UDP port, where TLS control channel packets bearing an incorrect HMAC signature can be dropped immediately without response. file (required) is a file in OpenVPN static key format which can be generated by genkey. Older versions (up to OpenVPN 2.3) supported a freeform passphrase file. This is no longer supported in newer versions (v2.4+). See the <a href="#secret">secret</a> option for more information on the optional direction parameter. tls-auth is recommended when you are running OpenVPN in a mode where it is listening for packets from any IP address, such as when <a href="#remote">remote</a> is not specified, or <a href="#remote">remote</a> is specified with <a href="#float">float</a>. The rationale for this feature is as follows. TLS requires a multi-packet exchange before it is able to authenticate a peer. During this time before authentication, OpenVPN is allocating resources (memory and CPU) to this potential peer. The potential peer is also exposing many parts of OpenVPN and the OpenSSL library to the packets it is sending. Most successful network attacks today seek to either exploit bugs in programs (such as buffer overflow attacks) or force a program to consume so many resources that it becomes unusable. Of course the first line of defense is always to produce clean, well-audited code. OpenVPN has been written with buffer overflow attack prevention as a top priority. But as history has shown, many of the most widely used network applications have, from time to time, fallen to buffer overflow attacks. So as a second line of defense, OpenVPN offers this special layer of authentication on top of the TLS control channel so that every packet on the control channel is authenticated by an HMAC signature and a unique ID for replay protection. This signature will also help protect against DoS (Denial of Service) attacks. An important rule of thumb in reducing vulnerability to DoS attacks is to minimize the amount of resources a potential, but as yet unauthenticated, client is able to consume. tls-auth does this by signing every TLS control channel packet with an HMAC signature, including packets which are sent before the TLS level has had a chance to authenticate the peer. The result is that packets without the correct signature can be dropped immediately upon reception, before they have a chance to consume additional system resources such as by initiating a TLS handshake. tls-auth can be strengthened by adding the <a href="#replay-persist">replay-persist</a> option which will keep OpenVPN's replay protection state in a file so that it is not lost across restarts. It should be emphasized that this feature is optional and that the key file used with tls-auth gives a peer nothing more than the power to initiate a TLS handshake. It is not used to encrypt or authenticate any tunnel data. Use <a href="#tls-crypt">tls-crypt</a> instead if you want to use the key file to not only authenticate, but also encrypt the TLS control channel. <h2 id="tls-cert-profile"><a href="#tls-cert-profile">tls-cert-profile</a></h2> Syntax: <code>tls-cert-profile <var>profile</var></code> Set the allowed cryptographic algorithms for certificates according to profile. The following profiles are supported: <code>insecure</code> Identical for mbed TLS to legacy <code>legacy</code> (default) SHA1 and newer, RSA 2048-bit+, any elliptic curve. <code>preferred</code> SHA2 and newer, RSA 2048-bit+, any elliptic curve. <code>suiteb</code> SHA256/SHA384, ECDSA with P-256 or P-384. This option is only fully supported for mbed TLS builds. OpenSSL builds use the following approximation: <code>insecure</code> sets "security level 0" <code>legacy</code> (default) sets "security level 1" <code>preferred</code> sets "security level 2" <code>suiteb</code> sets "security level 3" and <a href="#tls-cipher">tls-cipher</a> "SUITEB128". OpenVPN will migrate to 'preferred' as default in the future. Please ensure that your keys already comply. <h2 id="tls-cipher"><a href="#tls-cipher">tls-cipher</a></h2> Syntax: <code>tls-cipher <var>l</var></code> A list l of allowable TLS ciphers delimited by a colon ("<code>:</code>"). These setting can be used to ensure that certain cipher suites are used (or not used) for the TLS connection. OpenVPN uses TLS to secure the control channel, over which the keys that are used to protect the actual VPN traffic are exchanged. The supplied list of ciphers is (after potential OpenSSL/IANA name translation) simply supplied to the crypto library. Please see the OpenSSL and/or mbed TLS documentation for details on the cipher list interpretation. For OpenSSL, the tls-cipher is used for TLS 1.2 and below. Use show-tls to see a list of TLS ciphers supported by your crypto library. The default for tls-cipher is to use mbed TLS's default cipher list when using mbed TLS or <code>DEFAULT:!EXP:!LOW:!MEDIUM:!kDH:!kECDH:!DSS:!PSK:!SRP:!kRSA</code> when using OpenSSL. <h2 id="tls-ciphersuites"><a href="#tls-ciphersuites">tls-ciphersuites</a></h2> Syntax: <code>tls-ciphersuites <var>l</var></code> Same as <a href="#tls-cipher">tls-cipher</a> but for TLS 1.3 and up. mbed TLS has no TLS 1.3 support yet and only the <a href="#tls-cipher">tls-cipher</a> setting is used. The default for tls-ciphersuites is to use the crypto library's default. <h2 id="tls-client"><a href="#tls-client">tls-client</a></h2> Syntax: <code>tls-client</code> Enable TLS and assume client role during TLS handshake. <h2 id="tls-crypt"><a href="#tls-crypt">tls-crypt</a></h2> Syntax: <code>tls-crypt <var>keyfile</var></code> Encrypt and authenticate all control channel packets with the key from keyfile. (See <a href="#tls-auth">tls-auth</a> for more background.) Encrypting (and authenticating) control channel packets: provides more privacy by hiding the certificate used for the TLS connection, makes it harder to identify OpenVPN traffic as such, provides "poor-man's" post-quantum security, against attackers who will never know the pre-shared key (i.e. no forward secrecy). In contrast to <a href="#tls-auth">tls-auth</a>, tls-crypt does not require the user to set <a href="#key-direction">key-direction</a>. Security Considerations All peers use the same tls-crypt pre-shared group key to authenticate and encrypt control channel messages. To ensure that IV collisions remain unlikely, this key should not be used to encrypt more than 2^48 client-to-server or 2^48 server-to-client control channel messages. A typical initial negotiation is about 10 packets in each direction. Assuming both initial negotiation and renegotiations are at most 2^16 (65536) packets (to be conservative), and (re)negotiations happen each minute for each user (24/7), this limits the tls-crypt key lifetime to 8171 years divided by the number of users. So a setup with 1000 users should rotate the key at least once each eight years. (And a setup with 8000 users each year.) If IV collisions were to occur, this could result in the security of tls-crypt degrading to the same security as using <a href="#tls-auth">tls-auth</a>. That is, the control channel still benefits from the extra protection against active man-in-the-middle-attacks and DoS attacks, but may no longer offer extra privacy and post-quantum security on top of what TLS itself offers. For large setups or setups where clients are not trusted, consider using <a href="#tls-crypt-v2">tls-crypt-v2</a> instead. That uses per-client unique keys, and thereby improves the bounds to 'rotate a client key at least once per 8000 years'. <h2 id="tls-crypt-v2"><a href="#tls-crypt-v2">tls-crypt-v2</a></h2> Syntax: <code>tls-crypt-v2 <var>keyfile</var></code> Valid syntax: <pre class="literal-block"> tls-crypt-v2 keyfile tls-crypt-v2 keyfile force-cookie tls-crypt-v2 keyfile allow-noncookie </pre> Use client-specific tls-crypt keys. For clients, keyfile is a client-specific tls-crypt key. Such a key can be generated using the <code>genkey tls-crypt-v2-client</code> option. For servers, keyfile is used to unwrap client-specific keys supplied by the client during connection setup. This key must be the same as the key used to generate the client-specific key (see <code>genkey tls-crypt-v2-client</code>). On servers, this option can be used together with the <a href="#tls-auth">tls-auth</a> or <a href="#tls-crypt">tls-crypt</a> option. In that case, the server will detect whether the client is using client-specific keys, and automatically select the right mode. The optional parameters <code>force-cookie</code> allows only tls-crypt-v2 clients that support a cookie based stateless three way handshake that avoids replay attacks and state exhaustion on the server side (OpenVPN 2.6 and later). The option <code>allow-noncookie</code> explicitly allows older tls-crypt-v2 clients. The default is (currently) <code>allow-noncookie</code>. <h2 id="tls-crypt-v2-verify"><a href="#tls-crypt-v2-verify">tls-crypt-v2-verify</a></h2> Syntax: <code>tls-crypt-v2-verify <var>cmd</var></code> Run command cmd to verify the metadata of the client-specific tls-crypt-v2 key of a connecting client. This allows server administrators to reject client connections, before exposing the TLS stack (including the notoriously dangerous X.509 and ASN.1 stacks) to the connecting client. OpenVPN supplies the following environment variables to the command (and only these variables. The normal environment variables available for other scripts are NOT present): <code>script_type</code> is set to <code>tls-crypt-v2-verify</code> <code>metadata_type</code> is set to <code>0</code> if the metadata was user supplied, or <code>1</code> if it's a 64-bit unix timestamp representing the key creation time. <code>metadata_file</code> contains the filename of a temporary file that contains the client metadata. The command can reject the connection by exiting with a non-zero exit code. <h2 id="tls-exit"><a href="#tls-exit">tls-exit</a></h2> Syntax: <code>tls-exit</code> Exit on TLS negotiation failure. This option can be useful when you only want to make one attempt at connecting, e.g. in a test or monitoring script. (OpenVPN's own test suite uses it this way.) <h2 id="tls-export-cert"><a href="#tls-export-cert">tls-export-cert</a></h2> Syntax: <code>tls-export-cert <var>dir</var></code> Adds an environment variable peer_cert when calling the <a href="#tls-verify">tls-verify</a> script or executing the OPENVPN_PLUGIN_TLS_VERIFY plugin hook to verify the certificate. The environment variable contains the path to a PEM encoded certificate of the current peer certificate in the directory dir. <h2 id="tls-groups"><a href="#tls-groups">tls-groups</a></h2> Syntax: <code>tls-groups <var>list</var></code> A list of allowable groups/curves in order of preference. Set the allowed elliptic curves/groups for the TLS session. These groups are allowed to be used in signatures and key exchange. mbedTLS currently allows all known curves per default. OpenSSL 1.1+ restricts the list per default to <pre class="literal-block"> "X25519:secp256r1:X448:secp521r1:secp384r1". </pre> If you use certificates that use non-standard curves, you might need to add them here. If you do not force the ecdh curve by using <a href="#ecdh-curve">ecdh-curve</a>, the groups for ecdh will also be picked from this list. OpenVPN maps the curve name secp256r1 to prime256v1 to allow specifying the same tls-groups option for mbedTLS and OpenSSL. Warning: this option not only affects elliptic curve certificates but also the key exchange in TLS 1.3 and using this option improperly will disable TLS 1.3. <h2 id="tls-timeout"><a href="#tls-timeout">tls-timeout</a></h2> Syntax: <code>tls-timeout <var>n</var></code> Packet retransmit timeout on TLS control channel if no acknowledgment from remote within n seconds (default <code>2</code>). When OpenVPN sends a control packet to its peer, it will expect to receive an acknowledgement within n seconds or it will retransmit the packet, subject to a TCP-like exponential backoff algorithm. This parameter only applies to control channel packets. Data channel packets (which carry encrypted tunnel data) are never acknowledged, sequenced, or retransmitted by OpenVPN because the higher level network protocols running on top of the tunnel such as TCP expect this role to be left to them. <h2 id="tls-verify"><a href="#tls-verify">tls-verify</a></h2> Syntax: <code>tls-verify <var>cmd</var></code> Run command cmd to verify the X509 name of a pending TLS connection that has otherwise passed all other tests of certification (except for revocation via <a href="#crl-verify">crl-verify</a> directive; the revocation test occurs after the tls-verify test). cmd should return <code>0</code> to allow the TLS handshake to proceed, or <code>1</code> to fail. cmd consists of a path to a script (or executable program), optionally followed by arguments. The path and arguments may be single- or double-quoted and/or escaped using a backslash, and should be separated by one or more spaces. When cmd is executed two arguments are appended after any arguments specified in cmd, as follows: <pre class="literal-block"> cmd certificate_depth subject </pre> These arguments are, respectively, the current certificate depth and the X509 subject distinguished name (dn) of the peer. This feature is useful if the peer you want to trust has a certificate which was signed by a certificate authority who also signed many other certificates, where you don't necessarily want to trust all of them, but rather be selective about which peer certificate you will accept. This feature allows you to write a script which will test the X509 name on a certificate and decide whether or not it should be accepted. For a simple perl script which will test the common name field on the certificate, see the file verify-cn in the OpenVPN distribution. See the Environmental Variables section below for additional parameters passed as environmental variables. <h2 id="tls-version-max"><a href="#tls-version-max">tls-version-max</a></h2> Syntax: <code>tls-version-max <var>version</var></code> Set the maximum TLS version we will use (default is the highest version supported). Examples for version include <code>1.0</code>, <code>1.1</code>, or <code>1.2</code>. <h2 id="tls-version-min"><a href="#tls-version-min">tls-version-min</a></h2> Syntax: <code>tls-version-min <var>args</var></code> Sets the minimum TLS version we will accept from the peer (default in 2.6.0 and later is "1.2"). Valid syntax: <pre class="literal-block"> tls-version-min version ['or-highest'] </pre> Examples for version include <code>1.0</code>, <code>1.1</code>, or <code>1.2</code>. If <code>or-highest</code> is specified and version is not recognized, we will only accept the highest TLS version supported by the local SSL implementation. <h2 id="topology"><a href="#topology">topology</a></h2> Syntax: <code>topology <var>mode</var></code> Configure virtual addressing topology when running in dev tun mode. This directive has no meaning in dev tap mode, which always uses a <code>subnet</code> topology. If you set this directive on the server, the server and server-bridge directives will automatically push your chosen topology setting to clients as well. This directive can also be manually pushed to clients. Like the dev directive, this directive must always be compatible between client and server. mode can be one of: <code>net30</code> Use a point-to-point topology, by allocating one /30 subnet per client. This is designed to allow point-to-point semantics when some or all of the connecting clients might be Windows systems. This is the default. <code>p2p</code> Use a point-to-point topology where the remote endpoint of the client's tun interface always points to the local endpoint of the server's tun interface. This mode allocates a single IP address per connecting client. Only use when none of the connecting clients are Windows systems. <code>subnet</code> Use a subnet rather than a point-to-point topology by configuring the tun interface with a local IP address and subnet mask, similar to the topology used in dev tap and ethernet bridging mode. This mode allocates a single IP address per connecting client and works on Windows as well. Note: Using topology subnet changes the interpretation of the arguments of <a href="#ifconfig">ifconfig</a> to mean "address netmask", no longer "local remote". <h2 id="tran-window"><a href="#tran-window">tran-window</a></h2> Syntax: <code>tran-window <var>n</var></code> Transition window -- our old key can live this many seconds after a new a key renegotiation begins (default <code>3600</code> seconds). This feature allows for a graceful transition from old to new key, and removes the key renegotiation sequence from the critical path of tunnel data forwarding. <h2 id="tun-max-mtu"><a href="#tun-max-mtu">tun-max-mtu</a></h2> Syntax: <code>tun-max-mtu <var>maxmtu</var></code> This configures the maximum MTU size that a server can push to maxmtu, by configuring the internal buffers to allow at least this packet size. The default for maxmtu is 1600. Currently, only increasing beyond 1600 is possible, and attempting to reduce max-mtu below 1600 will be ignored. <h2 id="tun-mtu"><a href="#tun-mtu">tun-mtu</a></h2> Syntax: <code>tun-mtu <var>args</var></code> Valid syntaxes: <pre class="literal-block"> tun-mtu tun-mtu tun-mtu tun-mtu occ-mtu </pre> Take the TUN device MTU to be tun-mtu and derive the link MTU from it. In most cases, you will probably want to leave this parameter set to its default value. The default for <code>tun-mtu</code> is 1500. The OCC MTU can be used to avoid warnings about mismatched MTU from clients. If <code>occ-mtu</code> is not specified, it will to default to the tun-mtu. The MTU (Maximum Transmission Units) is the maximum datagram size in bytes that can be sent unfragmented over a particular network path. OpenVPN requires that packets on the control and data channels be sent unfragmented. MTU problems often manifest themselves as connections which hang during periods of active usage. It's best to use the <a href="#fragment">fragment</a> and/or <a href="#mssfix">mssfix</a> options to deal with MTU sizing issues. Note: Depending on the platform, the operating system allows one to receive packets larger than tun-mtu (e.g. Linux and FreeBSD) but other platforms (like macOS) limit received packets to the same size as the MTU. <h2 id="tun-mtu-extra"><a href="#tun-mtu-extra">tun-mtu-extra</a></h2> Syntax: <code>tun-mtu-extra <var>n</var></code> Assume that the TUN/TAP device might return as many as n bytes more than the <a href="#tun-mtu">tun-mtu</a> size on read. This parameter defaults to 0, which is sufficient for most TUN devices. TAP devices may introduce additional overhead in excess of the MTU size, and a setting of 32 is the default when TAP devices are used. This parameter only controls internal OpenVPN buffer sizing, so there is no transmission overhead associated with using a larger value. <h2 id="up"><a href="#up">up</a></h2> Syntax: <code>up <var>cmd</var></code> Run command cmd after successful TUN/TAP device open (pre user UID change). cmd consists of a path to a script (or executable program), optionally followed by arguments. The path and arguments may be single- or double-quoted and/or escaped using a backslash, and should be separated by one or more spaces. The up command is useful for specifying route commands which route IP traffic destined for private subnets which exist at the other end of the VPN connection into the tunnel. For dev tun execute as: <pre class="literal-block"> cmd tun_dev tun_mtu 0 ifconfig_local_ip ifconfig_remote_ip [init | restart] </pre> For dev tap execute as: <pre class="literal-block"> cmd tap_dev tap_mtu 0 ifconfig_local_ip ifconfig_netmask [init | restart] </pre> See the Environmental Variables section below for additional parameters passed as environmental variables. The 0 argument used to be link_mtu which is no longer passed to scripts - to keep the argument order, it was replaced with 0. Note that if cmd includes arguments, all OpenVPN-generated arguments will be appended to them to build an argument list with which the executable will be called. Typically, cmd will run a script to add routes to the tunnel. Normally the up script is called after the TUN/TAP device is opened. In this context, the last command line parameter passed to the script will be init. If the <a href="#up-restart">up-restart</a> option is also used, the up script will be called for restarts as well. A restart is considered to be a partial reinitialization of OpenVPN where the TUN/TAP instance is preserved (the <a href="#persist-tun">persist-tun</a> option will enable such preservation). A restart can be generated by a SIGUSR1 signal, a <a href="#ping-restart">ping-restart</a> timeout, or a connection reset when the TCP protocol is enabled with the <a href="#proto">proto</a> option. If a restart occurs, and <a href="#up-restart">up-restart</a> has been specified, the up script will be called with restart as the last parameter. NOTE: On restart, OpenVPN will not pass the full set of environment variables to the script. Namely, everything related to routing and gateways will not be passed, as nothing needs to be done anyway - all the routing setup is already in place. Additionally, the up-restart script will run with the downgraded UID/GID settings (if configured). The following standalone example shows how the up script can be called in both an initialization and restart context. (NOTE: for security reasons, don't run the following example unless UDP port 9999 is blocked by your firewall. Also, the example will run indefinitely, so you should abort with control-c). <pre class="literal-block"> openvpn dev tun <a href="#port">port</a> 9999 <a href="#verb">verb</a> 4 <a href="#ping-restart">ping-restart</a> 10 \ up 'echo up' <a href="#down">down</a> 'echo down' <a href="#persist-tun">persist-tun</a> \ <a href="#up-restart">up-restart</a> </pre> Note that OpenVPN also provides the <a href="#ifconfig">ifconfig</a> option to automatically ifconfig the TUN device, eliminating the need to define an up script, unless you also want to configure routes in the up script. If <a href="#ifconfig">ifconfig</a> is also specified, OpenVPN will pass the ifconfig local and remote endpoints on the command line to the up script so that they can be used to configure routes such as: <pre class="last literal-block"> route add -net 10.0.0.0 netmask 255.255.255.0 gw $5 </pre> <h2 id="up-delay"><a href="#up-delay">up-delay</a></h2> Syntax: <code>up-delay</code> Delay TUN/TAP open and possible <a href="#up">up</a> script execution until after TCP/UDP connection establishment with peer. In <a href="#proto">proto</a> udp mode, this option normally requires the use of <a href="#ping">ping</a> to allow connection initiation to be sensed in the absence of tunnel data, since UDP is a "connectionless" protocol. On Windows, this option will delay the TAP-Win32 media state transitioning to "connected" until connection establishment, i.e. the receipt of the first authenticated packet from the peer. <h2 id="up-restart"><a href="#up-restart">up-restart</a></h2> Syntax: <code>up-restart</code> Enable the <a href="#up">up</a> and <a href="#down">down</a> scripts to be called for restarts as well as initial program start. This option is described more fully above in the <a href="#up">up</a> option documentation. <h2 id="use-prediction-resistance"><a href="#use-prediction-resistance">use-prediction-resistance</a></h2> Syntax: <code>use-prediction-resistance</code> Enable prediction resistance on mbed TLS's RNG. Enabling prediction resistance causes the RNG to reseed in each call for random. Reseeding this often can quickly deplete the kernel entropy pool. If you need this option, please consider running a daemon that adds entropy to the kernel pool. <h2 id="verb"><a href="#verb">verb</a></h2> Syntax: <code>verb <var>n</var></code> Set output verbosity to n (default <code>1</code>). Each level shows all info from the previous levels. Level <code>3</code> is recommended if you want a good summary of what's happening without being swamped by output. <code>0</code> No output except fatal errors. <code>1</code> to <code>4</code> Normal usage range. <code>5</code> Outputs <code>R</code> and <code>W</code> characters to the console for each packet read and write, uppercase is used for TCP/UDP packets and lowercase is used for TUN/TAP packets. <code>6</code> to <code>11</code> Debug info range (see <code>errlevel.h</code> in the source code for additional information on debug levels). <h2 id="verify-hash"><a href="#verify-hash">verify-hash</a></h2> Syntax: <code>verify-hash <var>args</var></code> DEPRECATED Specify SHA1 or SHA256 fingerprint for level-1 cert. Valid syntax: <pre class="literal-block"> verify-hash hash [algo] </pre> The level-1 cert is the CA (or intermediate cert) that signs the leaf certificate, and is one removed from the leaf certificate in the direction of the root. When accepting a connection from a peer, the level-1 cert fingerprint must match hash or certificate verification will fail. Hash is specified as XX:XX:... For example: <pre class="literal-block"> AD:B0:95:D8:09:C8:36:45:12:A9:89:C8:90:09:CB:13:72:A6:AD:16 </pre> The algo flag can be either <code>SHA1</code> or <code>SHA256</code>. If not provided, it defaults to <code>SHA1</code>. This option can also be inlined <pre class="last literal-block"> <verify-hash> 00:11:22:33:44:55:66:77:88:99:aa:bb:cc:dd:ee:ff:00:11:22:33:44:55:66:77:88:99:aa:bb:cc:dd:ee:ff 11:22:33:44:55:66:77:88:99:aa:bb:cc:dd:ee:ff:00:11:22:33:44:55:66:77:88:99:aa:bb:cc:dd:ee:ff:00 </verify-hash> </pre> <h2 id="verify-x509-name"><a href="#verify-x509-name">verify-x509-name</a></h2> Syntax: <code>verify-x509-name <var>args</var></code> Accept connections only if a host's X.509 name is equal to name. The remote host must also pass all other tests of verification. Valid syntax: <pre class="literal-block"> verify-x509 name type </pre> Which X.509 name is compared to name depends on the setting of type. type can be <code>subject</code> to match the complete subject DN (default), <code>name</code> to match a subject RDN or <code>name-prefix</code> to match a subject RDN prefix. Which RDN is verified as name depends on the <a href="#x509-username-field">x509-username-field</a> option. But it defaults to the common name (CN), e.g. a certificate with a subject DN <pre class="literal-block"> C=KG, ST=NA, L=Bishkek, CN=Server-1 </pre> would be matched by: <pre class="literal-block"> verify-x509-name 'C=KG, ST=NA, L=Bishkek, CN=Server-1' verify-x509-name Server-1 name verify-x509-name Server- name-prefix </pre> The last example is useful if you want a client to only accept connections to <code>Server-1</code>, <code>Server-2</code>, etc. verify-x509-name is a useful replacement for the <a href="#tls-verify">tls-verify</a> option to verify the remote host, because verify-x509-name works in a chroot environment without any dependencies. Using a name prefix is a useful alternative to managing a CRL (Certificate Revocation List) on the client, since it allows the client to refuse all certificates except for those associated with designated servers. NOTE: Test against a name prefix only when you are using OpenVPN with a custom CA certificate that is under your control. Never use this option with type <code>name-prefix</code> when your client certificates are signed by a third party, such as a commercial web CA. <h2 id="windows-driver"><a href="#windows-driver">windows-driver</a></h2> Syntax: <code>windows-driver <var>drv</var></code> Specifies which tun driver to use. Values are <code>ovpn-dco</code> (default), <code>tap-windows6</code> and <code>wintun</code>. <code>ovpn-dco</code> and <code>wintun</code> require dev tun. <code>wintun</code> also requires OpenVPN process to run elevated, or be invoked using the Interactive Service. <h2 id="x509-track"><a href="#x509-track">x509-track</a></h2> Syntax: <code>x509-track <var>attribute</var></code> Save peer X509 attribute value in environment for use by plugins and management interface. Prepend a <code>+</code> to attribute to save values from full cert chain. Otherwise the attribute will only be exported for the leaf cert (i.e. depth <code>0</code> of the cert chain). Values will be encoded as <code>X509_<depth>_<attribute>=<value></code>. Multiple x509-track options can be defined to track multiple attributes. attribute can be any part of the X509 Subject field or any X509v3 extension (RFC 3280). X509v3 extensions might not be supported when not using the default TLS backend library (OpenSSL). You can also request the SHA1 and SHA256 fingerprints of the cert, but that is always exported as <code>tls_digest_{n}</code> and <code>tls_digest_sha256_{n}</code> anyway. Note that by default all parts of the X509 Subject field are exported in the environment for the whole cert chain. If you use x509-track at least once only the attributes specified by these options are exported. Examples: <pre class="last literal-block"> x509-track CN # exports only X509_0_CN x509-track +CN # exports X509_{n}_CN for chain x509-track basicConstraints # exports value of "X509v3 Basic Constraints" x509-track SHA256 # exports SHA256 fingerprint </pre> <h2 id="x509-username-field"><a href="#x509-username-field">x509-username-field</a></h2> Syntax: <code>x509-username-field <var>args</var></code> Fields in the X.509 certificate subject to be used as the username (default <code>CN</code>). If multiple fields are specified their values will be concatenated into the one username using <code>_</code> symbol as a separator. Valid syntax: <pre class="literal-block"> x509-username-field [ext:]fieldname [[ext:]fieldname...] </pre> Typically, this option is specified with fieldname arguments as either of the following: <pre class="literal-block"> x509-username-field emailAddress x509-username-field ext:subjectAltName x509-username-field CN serialNumber </pre> The first example uses the value of the <code>emailAddress</code> attribute in the certificate's Subject field as the username. The second example uses the <code>ext:</code> prefix to signify that the X.509 extension fieldname <code>subjectAltName</code> be searched for an rfc822Name (email) field to be used as the username. In cases where there are multiple email addresses in <code>ext:fieldname</code>, the last occurrence is chosen. The last example uses the value of the <code>CN</code> attribute in the Subject field, combined with the <code>_</code> separator and the hexadecimal representation of the certificate's <code>serialNumber</code>. When this option is used, the <a href="#verify-x509-name">verify-x509-name</a> option will match against the chosen fieldname instead of the Common Name. Only the <code>subjectAltName</code> and <code>issuerAltName</code> X.509 extensions and <code>serialNumber</code> X.509 attribute are supported. Please note: This option has a feature which will convert an all-lowercase fieldname to uppercase characters, e.g., <code>ou</code> -> <code>OU</code>. A mixed-case fieldname or one having the <code>ext:</code> prefix will be left as-is. This automatic upcasing feature is deprecated and will be removed in a future release. Non-compliant symbols are being replaced with the <code>_</code> symbol, same as the field separator, so concatenating multiple fields with such or <code>_</code> symbols can potentially lead to username collisions. The above list of OpenVPN commands is a rendered version of the OpenVPN man page, which is licensed under the <a href="/company/legal/thirdparty/">GPLv2</a>. This man page can be <a href="openvpn">downloaded from here.</a> </div> </div> <div class="col-md-4" role="complementary"> <nav class="bs-docs-sidebar hidden-print hidden-xs hidden-sm"> <h4 style="padding-left:18px;">Contents</h4> <ul class="nav bs-docs-sidenav"> <li><a href="#advanced-configuration-commands">Advanced Configuration Commands</a> </li> <li><a href="#specifying-advanced-configuration-commands">Specifying Advanced Configuration Commands</a> </li> <li><a href="#advanced-viscosity-commands">Advanced Viscosity Commands</a> <ul class="nav"> <li><a href="#static-challenge-password">static-challenge-password </a></li> <li><a href="#static-challenge-acknowledge">static-challenge-acknowledge </a></li> <li><a href="#system-identity-domain">system-identity-domain </a></li> <li><a href="#proxy-automatic">proxy-automatic </a></li> <li><a href="#proxy-http">proxy-http </a></li> <li><a href="#proxy-https">proxy-https </a></li> <li><a href="#proxy-socks">proxy-socks </a></li> </ul> </li> <li><a href="#advanced-openvpn-commands">Advanced OpenVPN Commands</a> <ul class="nav"> <li><a href="#allow-compression">allow-compression</a></li> <li><a href="#allow-pull-fqdn">allow-pull-fqdn</a></li> <li><a href="#allow-recursive-routing">allow-recursive-routing</a></li> <li><a href="#askpass">askpass</a></li> <li><a href="#auth">auth</a></li> <li><a href="#auth-nocache">auth-nocache</a></li> <li><a href="#auth-retry">auth-retry</a></li> <li><a href="#auth-token-user">auth-token-user</a></li> <li><a href="#auth-user-pass">auth-user-pass</a></li> <li><a href="#bcast-buffers">bcast-buffers</a></li> <li><a href="#bind">bind</a></li> <li><a href="#bind-dev">bind-dev</a></li> <li><a href="#block-ipv6">block-ipv6</a></li> <li><a href="#ca">ca</a></li> <li><a href="#capath">capath</a></li> <li><a href="#ccd-exclusive">ccd-exclusive</a></li> <li><a href="#cd">cd</a></li> <li><a href="#cert">cert</a></li> <li><a href="#cipher">cipher</a></li> <li><a href="#client-nat">client-nat</a></li> <li><a href="#comp-lzo">comp-lzo</a></li> <li><a href="#comp-noadapt">comp-noadapt</a></li> <li><a href="#compat-mode">compat-mode</a></li> <li><a href="#compress">compress</a></li> <li><a href="#connect-retry">connect-retry</a></li> <li><a href="#connect-retry-max">connect-retry-max</a></li> <li><a href="#connect-timeout">connect-timeout</a></li> <li><a href="#crl-verify">crl-verify</a></li> <li><a href="#cryptoapicert">cryptoapicert</a></li> <li><a href="#data-ciphers">data-ciphers</a></li> <li><a href="#data-ciphers-fallback">data-ciphers-fallback</a></li> <li><a href="#dhcp-option">dhcp-option</a></li> <li><a href="#dhcp-release">dhcp-release</a></li> <li><a href="#dhcp-renew">dhcp-renew</a></li> <li><a href="#disable-occ">disable-occ</a></li> <li><a href="#dns">dns</a></li> <li><a href="#down">down</a></li> <li><a href="#down-pre">down-pre</a></li> <li><a href="#ecdh-curve">ecdh-curve</a></li> <li><a href="#echo">echo</a></li> <li><a href="#engine">engine</a></li> <li><a href="#explicit-exit-notify">explicit-exit-notify</a></li> <li><a href="#extra-certs">extra-certs</a></li> <li><a href="#fast-io">fast-io</a></li> <li><a href="#float">float</a></li> <li><a href="#fragment">fragment</a></li> <li><a href="#hand-window">hand-window</a></li> <li><a href="#hash-size">hash-size</a></li> <li><a href="#http-proxy">http-proxy</a></li> <li><a href="#http-proxy-option">http-proxy-option</a></li> <li><a href="#http-proxy-user-pass">http-proxy-user-pass</a></li> <li><a href="#ifconfig">ifconfig</a></li> <li><a href="#ifconfig-ipv6">ifconfig-ipv6</a></li> <li><a href="#ifconfig-noexec">ifconfig-noexec</a></li> <li><a href="#ifconfig-nowarn">ifconfig-nowarn</a></li> <li><a href="#ignore-unknown-option">ignore-unknown-option</a></li> <li><a href="#inactive">inactive</a></li> <li><a href="#ip-win32">ip-win32</a></li> <li><a href="#ipchange">ipchange</a></li> <li><a href="#iproute">iproute</a></li> <li><a href="#keepalive">keepalive</a></li> <li><a href="#key">key</a></li> <li><a href="#key-direction">key-direction</a></li> <li><a href="#key-method">key-method</a></li> <li><a href="#link-mtu">link-mtu</a></li> <li><a href="#lladdr">lladdr</a></li> <li><a href="#local">local</a></li> <li><a href="#lport">lport</a></li> <li><a href="#mark">mark</a></li> <li><a href="#max-packet-size">max-packet-size</a></li> <li><a href="#mssfix">mssfix</a></li> <li><a href="#mtu-test">mtu-test</a></li> <li><a href="#mute">mute</a></li> <li><a href="#mute-replay-warnings">mute-replay-warnings</a></li> <li><a href="#nobind">nobind</a></li> <li><a href="#ns-cert-type">ns-cert-type</a></li> <li><a href="#passtos">passtos</a></li> <li><a href="#peer-fingerprint">peer-fingerprint</a></li> <li><a href="#persist-key">persist-key</a></li> <li><a href="#persist-local-ip">persist-local-ip</a></li> <li><a href="#persist-remote-ip">persist-remote-ip</a></li> <li><a href="#persist-tun">persist-tun</a></li> <li><a href="#ping">ping</a></li> <li><a href="#ping-exit">ping-exit</a></li> <li><a href="#ping-restart">ping-restart</a></li> <li><a href="#pkcs11-cert-private">pkcs11-cert-private</a></li> <li><a href="#pkcs11-id">pkcs11-id</a></li> <li><a href="#pkcs11-pin-cache">pkcs11-pin-cache</a></li> <li><a href="#pkcs11-private-mode">pkcs11-private-mode</a></li> <li><a href="#pkcs11-protected-authentication">pkcs11-protected-authentication</a></li> <li><a href="#pkcs11-providers">pkcs11-providers</a></li> <li><a href="#pkcs12">pkcs12</a></li> <li><a href="#port">port</a></li> <li><a href="#proto">proto</a></li> <li><a href="#proto-force">proto-force</a></li> <li><a href="#providers">providers</a></li> <li><a href="#pull">pull</a></li> <li><a href="#pull-filter">pull-filter</a></li> <li><a href="#push">push</a></li> <li><a href="#push-peer-info">push-peer-info</a></li> <li><a href="#rcvbuf">rcvbuf</a></li> <li><a href="#redirect-gateway">redirect-gateway</a></li> <li><a href="#redirect-private">redirect-private</a></li> <li><a href="#register-dns">register-dns</a></li> <li><a href="#remap-usr1">remap-usr1</a></li> <li><a href="#remote">remote</a></li> <li><a href="#remote-cert-eku">remote-cert-eku</a></li> <li><a href="#remote-cert-ku">remote-cert-ku</a></li> <li><a href="#remote-cert-tls">remote-cert-tls</a></li> <li><a href="#remote-random">remote-random</a></li> <li><a href="#remote-random-hostname">remote-random-hostname</a></li> <li><a href="#reneg-bytes">reneg-bytes</a></li> <li><a href="#reneg-pkts">reneg-pkts</a></li> <li><a href="#reneg-sec">reneg-sec</a></li> <li><a href="#replay-persist">replay-persist</a></li> <li><a href="#replay-window">replay-window</a></li> <li><a href="#resolv-retry">resolv-retry</a></li> <li><a href="#route">route</a></li> <li><a href="#route-delay">route-delay</a></li> <li><a href="#route-gateway">route-gateway</a></li> <li><a href="#route-ipv6">route-ipv6</a></li> <li><a href="#route-ipv6-gateway">route-ipv6-gateway</a></li> <li><a href="#route-method">route-method</a></li> <li><a href="#route-metric">route-metric</a></li> <li><a href="#route-nopull">route-nopull</a></li> <li><a href="#route-pre-down">route-pre-down</a></li> <li><a href="#route-up">route-up</a></li> <li><a href="#rport">rport</a></li> <li><a href="#script-security">script-security</a></li> <li><a href="#secret">secret</a></li> <li><a href="#server-poll-timeout">server-poll-timeout</a></li> <li><a href="#session-timeout">session-timeout</a></li> <li><a href="#setenv">setenv</a></li> <li><a href="#setenv-safe">setenv-safe</a></li> <li><a href="#shaper">shaper</a></li> <li><a href="#single-session">single-session</a></li> <li><a href="#sndbuf">sndbuf</a></li> <li><a href="#socket-flags">socket-flags</a></li> <li><a href="#socks-proxy">socks-proxy</a></li> <li><a href="#static-challenge">static-challenge</a></li> <li><a href="#status">status</a></li> <li><a href="#status-version">status-version</a></li> <li><a href="#tap-sleep">tap-sleep</a></li> <li><a href="#tcp-queue-limit">tcp-queue-limit</a></li> <li><a href="#tls-auth">tls-auth</a></li> <li><a href="#tls-cert-profile">tls-cert-profile</a></li> <li><a href="#tls-cipher">tls-cipher</a></li> <li><a href="#tls-ciphersuites">tls-ciphersuites</a></li> <li><a href="#tls-client">tls-client</a></li> <li><a href="#tls-crypt">tls-crypt</a></li> <li><a href="#tls-crypt-v2">tls-crypt-v2</a></li> <li><a href="#tls-crypt-v2-verify">tls-crypt-v2-verify</a></li> <li><a href="#tls-exit">tls-exit</a></li> <li><a href="#tls-export-cert">tls-export-cert</a></li> <li><a href="#tls-groups">tls-groups</a></li> <li><a href="#tls-timeout">tls-timeout</a></li> <li><a href="#tls-verify">tls-verify</a></li> <li><a href="#tls-version-max">tls-version-max</a></li> <li><a href="#tls-version-min">tls-version-min</a></li> <li><a href="#topology">topology</a></li> <li><a href="#tran-window">tran-window</a></li> <li><a href="#tun-max-mtu">tun-max-mtu</a></li> <li><a href="#tun-mtu">tun-mtu</a></li> <li><a href="#tun-mtu-extra">tun-mtu-extra</a></li> <li><a href="#up">up</a></li> <li><a href="#up-delay">up-delay</a></li> <li><a href="#up-restart">up-restart</a></li> <li><a href="#use-prediction-resistance">use-prediction-resistance</a></li> <li><a href="#verb">verb</a></li> <li><a href="#verify-hash">verify-hash</a></li> <li><a href="#verify-x509-name">verify-x509-name</a></li> <li><a href="#windows-driver">windows-driver</a></li> <li><a href="#x509-track">x509-track</a></li> <li><a href="#x509-username-field">x509-username-field</a></li> </ul> </li> </ul> <a class="back-to-top" href="#top">Back to top</a> </nav> </div> </div> </div> </div>  <script src="/static/js/jquery-3.3.1.min.js"></script> <footer class="bs-docs-footer">  <div class="contact-bar"> <div class="container"> <div class="row vertical-align sl_paddedcell_top"> <div class="col-xs-1"></div> <div class="col-xs-2 text-center"> </div> <div class="col-xs-7"> <h3 style="color:#fff;">Search Knowledge Base</h3> Search our knowledge base for guides and documentation. <form id="kbsearch" name="kbsearch" method="post" action="/support/kb/search/"> <div class="input-group"> <input name="query" type="text" class="form-control" placeholder="Search for..."> <button class="btn btn-default" type="submit">Search</button> </div> </form> </div> </div> </div> </div>   <div class="sl_row_gradient"> <div class="container"> <div class="row sl_paddedrow"> <div class="col-md-6 text-left"> <div class="list-group"> <li class="list-group-item"><h4>Other Articles In This Category</h4></li> <a href="/support/kb/article/advanced-configuration-commands/" class="list-group-item">   Advanced Configuration Commands</a> <a href="/support/kb/article/connection-settings/" class="list-group-item">   Connection Settings</a> <a href="/support/kb/article/getting-started-with-viscosity-mac/" class="list-group-item">   Getting Started With Viscosity (Mac)</a> <a href="/support/kb/article/getting-started-with-viscosity-windows/" class="list-group-item">   Getting Started With Viscosity (Windows)</a> <a href="/support/kb/article/installing-viscosity-mac/" class="list-group-item">   Installing Viscosity (Mac)</a> <a href="/support/kb/category/documentation/" class="list-group-item">12   View All</a> </div> </div> <div class="col-md-6"> <div class="list-group"> <li class="list-group-item"><h4>Related Articles</h4></li> <a href="/support/kb/article/advanced-configuration-commands/" class="list-group-item">   Advanced Configuration Commands</a> <a href="/support/kb/article/connection-settings/" class="list-group-item">   Connection Settings</a> <a href="/support/kb/article/getting-started-with-viscosity-mac/" class="list-group-item">   Getting Started With Viscosity (Mac)</a> <a href="/support/kb/article/getting-started-with-viscosity-windows/" class="list-group-item">   Getting Started With Viscosity (Windows)</a> <a href="/support/kb/article/installing-viscosity-mac/" class="list-group-item">   Installing Viscosity (Mac)</a> <a href="/support/kb/article/installing-viscosity-windows/" class="list-group-item">   Installing Viscosity (Windows)</a> </div> </div> </div> </div>  </div>  <div style="background-color:#34373a;"> <div class="container"> <div class="row footer_twitter_row"> <div class="col-md-1"> <img src="/static/img/bsky-logo.svg" height=22px style="opacity:0.4;margin-top:14px;" /> </div> <div class="col-md-9"> Follow us on Bluesky <a href="https://bsky.app/profile/sparklabs.com"> @sparklabs.com </a>  —  Viscosity 1.11.4 is now available for macOS! This update restores the performance of TAP VPN connections on macOS 15.0.1+, includes an updated version of OpenSSL, general performance improvements, and small bug fixes and enhancements. www.sparklabs.com/blog/viscosi... </div> <div class="col-md-2"> (<script>document.write(moment("1733234858.0", "X").fromNow());</script>) </div> </div> </div> </div> <div style="background-color:#191a1b;"> <div class="container"> <div class="row"> <div class="col-md-12"> <div class="row footer_link_row"> <div class="col-sm-4 col-md-2 columns" style="color:#555;"><h5>Apps</h5><ul style="list-style:none;padding-left:0;margin-left:0;"><li><a href="/viscosity/">Viscosity</a></li></ul> </div> <div class="col-sm-4 col-md-2 columns" style="color:#555;"><h5>Company</h5><ul style="list-style:none;padding-left:0;margin-left:0;"><li><a href="/company/">About</a></li><li><a href="/blog/">Blog</a></li><li><a href="/support/">Support</a></li><li><a href="/store/">Store</a></li></ul> </div> <div class="col-sm-4 col-md-2 columns" style="color:#555;"><h5>Support</h5><ul style="list-style:none;padding-left:0;margin-left:0;"><li><a href="/support/">Support Home</a></li><li><a href="/support/kb/">Knowledge Base</a></li><li><a href="/forum/">Forum</a></li><li><a href="/support/#contact">Contact Us</a></li></ul> </div> <div class="col-sm-2 col-md-2 columns" style="color:#555;"> </div> <div class="col-sm-12 col-md-4 columns" style="color:#555;"><h5>Stay Updated</h5><ul style="list-style:none;padding-left:0;margin-left:0;"><li class="text-justify">Keep up with the latest important SparkLabs news and updates with our (very) occasional newsletter.</li><li> <div class="input-group" style="padding-top:1em;"> <input type="text" class="form-control" placeholder="Email address" style="background-color:#333;border:0;color:#666;width:100%;" name="email" id="footer-emailinput"> <button class="btn btn-default" data-toggle="modal" data-target="#newsletter" style="background:transparent;border-color:#333;color:#666;">Subscribe</button> </div> </li></ul> </div> </div> </div> </div> <div class="row"> <div class="col-md-12 text-center"> <hr style="border:0;height:0;border-bottom:1px solid #222;"> </div> </div> <div class="row" style="padding-top:1em;padding-bottom:2em;"> <div class="col-md-12 text-center"> © SparkLabs Pty Ltd. SparkLabs & Viscosity are registered trademarks of SparkLabs Pty Ltd. <a href="/company/legal/#privacy" style="padding-left:2em;padding-right:2em;color:#444;">Privacy Policy</a> </div> </div> </div> </div> <div class="modal fade" id="newsletter" tabindex="-1" role="dialog" aria-labelledby="newsletter-label" aria-hidden="true"> <div class="modal-dialog"> <div class="modal-content"> <div class="modal-header"> <h4 class="modal-title">SparkLabs Newsletter</h4> </div> <div class="modal-header"> <div id="reissue-confirmmessage"> <div id="message">Thank you for being interested in keeping up with the latest news from us! Please double-check your email address below and then click the Subscribe button.</div> <form method="post" action="/newsletter/"> <input name="email" type="text" class="form-control" placeholder="Email address" id="news-emailinput"> <div class="g-recaptcha" data-sitekey="6LcyR74ZAAAAAKIOAPXwb7Sn-9Nwx-NLrQ05gHwy"></div> <button type="submit" class="btn btn-default" id="news-confirmbutton">Subscribe</button> </form> </div> </div> </div> </div> </div> <script type="text/javascript" charset="utf-8"> $('#newsletter').on('show.bs.modal', function(e) { $('#news-emailinput').val($('#footer-emailinput').val()); }); </script> </footer> </div> <script src="/static/js/bootstrap.min.js"></script> <script src="https://www.google.com/recaptcha/api.js" async defer></script> <script src="/static/js/docs.min.js"></script> <script src="/static/js/bootstrap-datepicker.min.js"></script> <script src="/static/js/lity.min.js"></script> <script src="/static/js/ostype.js"></script> <script type="text/javascript" charset="utf-8"> function screenShotButton(event) { var button = $(event.currentTarget); var target = $("#" + button.data('screenshot')) if (button.hasClass("screenshot_button_fullscreen")) { var platform = target.data("screenshot-platform"); if (!platform) { platform = "mac"; } var image = target.data("screenshot-" + platform); if (!image) { platform = "mac"; image = target.data("screenshot-" + platform); } var lightbox = lity("#screenshot-" + image); } else { target.data("screenshot-platform", button.data('platform')); renderScreenshots(); } }; function renderScreenshots() { $(".screenshot_image").each(function() { var target = $(this); var platform = target.data("screenshot-platform"); if (!platform) { platform = "mac"; } var image = target.data("screenshot-" + platform); if (!image) { platform = "mac"; image = target.data("screenshot-" + platform); } var zoom = target.data("screenshot-zoom"); target.empty(); target.append('<a href="#screenshot-' + image + '" data-lity><img src="' + image + '/embed" style="margin:0;display:none;" onload="this.width*=' + zoom + ';this.onload=null;this.style.display=\'inline\'" class="img-responsive" /></a>'); }); }; jQuery(document).ready(function($){ if (getOS().name == "Windows") { $(".screenshot_image").each(function() { $(this).data("screenshot-platform", "win"); }); } renderScreenshots(); $('.screenshot_button').on('click', function(event){ event.preventDefault(); screenShotButton(event); }); }); </script> </body> </html>