31,703
edits
Changes
→OpenVPN Client
| style="text-align: left; vertical-align: top;" | .key file; Default: " "
| style="text-align: left; vertical-align: top;" | .key file; Default: " "
| style="text-align: left; vertical-align: top;" | Authenticates the client to the server and establishes precisely who they are
| style="text-align: left; vertical-align: top;" | Authenticates the client to the server and establishes precisely who they are
|-
|}
After setting any of these parameters press the '''Save''' button or else the changes will not be applied. Some of the selected parameters will be shown in the configuration list table. You should also be aware of the fact that the router will launch a separate OpenVPN service for every configuration entry (if it is defined as active at the time, of course) so the router has the ability to act as server and client at the same time.
===OpenVPN Server===
This section is overview of OpenVPN Client configuration.
[[Image:Services vpn openvpn server.PNG]]
The figure above is an exampled of a configured OpenVPN Server instance that uses the UDP protocol and TLS authentication. As you can see, the configuration is similar to OpenVPN Client but with a few key differences. Comprehensible explanations on how to configure each field are presented in the table below.
{| class="wikitable"
|+
! style="width: 250px; background: black; color: white;" | Field name
! style="width: 250px; background: black; color: white;" | Value
! style="width: 1200px; background: black; color: white;" | Description
|-
! style="text-align: left; vertical-align: top;" | Enable
| style="text-align: left; vertical-align: top;" | yes {{!}} no; Default: '''no'''
| style="text-align: left; vertical-align: top;" | Enables the OpenVPN instance
|-
! style="text-align: left; vertical-align: top;" | TUN/TAP
| style="text-align: left; vertical-align: top;" | TUN (tunnel) {{!}} TAP (bridged); Default: '''TUN (tunnel)'''
| style="text-align: left; vertical-align: top;" | OpenVPN interface type. '''TUN''' is most often in typical VPN connections, however, '''TAP''' is required in some Ethernet bridging configurations
|-
! style="text-align: left; vertical-align: top;" | Protocol
| style="text-align: left; vertical-align: top;" | UDP {{!}} TCP; Default: '''UDP'''
| style="text-align: left; vertical-align: top;" | The transfer protocol used by the OpenVPN connection. '''TCP''' is connection oriented – once a connection is established, data can be sent bidirectionally. '''UDP''' is a simpler, connectionless Internet protocol. '''UDP''' is usually faster but '''TCP''' has more security features. Choose the connection protocol according to your needs.
|-
! style="text-align: left; vertical-align: top;" | Port
| style="text-align: left; vertical-align: top;" | integer [0..65535]; Default: '''1194'''
| style="text-align: left; vertical-align: top;" | TCP/UDP Port number for both local and remote endpoints (make sure that the chosen port is allowed by firewall)
|-
! style="text-align: left; vertical-align: top;" | LZO
| style="text-align: left; vertical-align: top;" | yes {{!}} no; Default: '''no'''
| style="text-align: left; vertical-align: top;" | With LZO compression, your VPN connection will generate less network traffic. However, enabling this causes a higher CPU load. Use it carefully with a high traffic rate or low CPU resources
|-
! style="text-align: left; vertical-align: top;" | Encryption
| style="text-align: left; vertical-align: top;" | DES-CBC 64 {{!}} RC2-CBC 128 {{!}} DES-EDE-CBC 128 {{!}} DES-EDE3-CBC 192 {{!}} DESX-CBC 192 {{!}} BF-CBC 128 {{!}} RC2-40-CBC 40 {{!}} CAST5-CBC 128 {{!}} RC2-40CBC 40 {{!}} CAST5-CBC 128 {{!}} RC2-64-CBC 64{{!}} AES-128-CBC 128 {{!}} AES-192-CBC 192 {{!}} AES-256-CBC 256 {{!}} none; Default: '''BF-CBC 128'''
| style="text-align: left; vertical-align: top;" | Packet encryption algorithm
|-
! style="text-align: left; vertical-align: top;" | Authentication
| style="text-align: left; vertical-align: top;" | TLS {{!}} Static Key {{!}} Password {{!}} TLS/Password; Default: '''TLS'''
| style="text-align: left; vertical-align: top;" | Authentication mode, used to secure data sessions.
'''Static key''' is a secret key used for server–client authentication.
'''TLS''' authentication mode uses X.509 type certificates:
'''Certificate Authority (CA)''', '''Client certificate''', '''Client key'''.
All mentioned certificates can be generated using OpenVPN or Open SSL utilities on any type of host machine.
'''Password''' is a simple username/password based authentication where the owner of the OpenVPN server provides the login data.
'''TLS/Password''' uses both TLS and Password authentication
|-
! style="text-align: left; vertical-align: top;" | TLS cipher
| style="text-align: left; vertical-align: top;" | all {{!}} DHE+RSA {{!}} custom; Default: '''all'''
| style="text-align: left; vertical-align: top;" | Packet encryption algorithm cipher
|-
! style="text-align: left; vertical-align: top;" | Client to client
| style="text-align: left; vertical-align: top;" | yes {{!}} no; Default: '''no'''
| style="text-align: left; vertical-align: top;" | Enables client to client communication in the Virtual network. In order for Client to client to work, the TLS Clients section most be utilized
|-
! style="text-align: left; vertical-align: top;" | Keep alive
| style="text-align: left; vertical-align: top;" | integer *space* integer; Default: " "
| style="text-align: left; vertical-align: top;" | Defines two time intervals: one is used to periodically send ICMP request to the OpenVPN server, the other defines a time window, which is used to restart the OpenVPN service, if no ICMP response is received during the window time slice.
'''Example:''' 10 60
|-
! style="text-align: left; vertical-align: top;" | Virtual network IP address
| style="text-align: left; vertical-align: top;" | ip; Default: " "
| style="text-align: left; vertical-align: top;" | IP address of the Virtual network, e.g., '''10.0.8.0'''
|-
! style="text-align: left; vertical-align: top;" | Virtual network IP netmask
| style="text-align: left; vertical-align: top;" | ip; Default: " "
| style="text-align: left; vertical-align: top;" | Subnet mask of the Virtual network
|-
! style="text-align: left; vertical-align: top;" | Push option
| style="text-align: left; vertical-align: top;" | string; Default: " "
| style="text-align: left; vertical-align: top;" | Push options are a way to “push” user defined routes to connecting clients’ routing tables. In the example above, the server will push the route of 192.168.1.0 network with the 255.255.255.0 netmask to connecting clients. Therefore, the client will be able to reach devices in the 192.168.1.0 network. This is useful when a client needs to reach devices located in the OpenVPN server’s LAN.
|-
! style="text-align: left; vertical-align: top;" | Allow duplicate certificates
| style="text-align: left; vertical-align: top;" | yes {{!}} no; Default: '''no'''
| style="text-align: left; vertical-align: top;" | If checked, the server allows clients to connect with identical certificates
|-
! style="text-align: left; vertical-align: top;" | Certificate authority
| style="text-align: left; vertical-align: top;" | .ca file; Default: " "
| style="text-align: left; vertical-align: top;" | Certificate authority is an entity that issues digital certificates. A digital certificate certifies the ownership of a public key by the named subject of the certificate
|-
! style="text-align: left; vertical-align: top;" | Server certificate
| style="text-align: left; vertical-align: top;" | .crt file; Default: " "
| style="text-align: left; vertical-align: top;" | Server certificate is a type of digital certificate that is used to identify the OpenVPN server
|-
! style="text-align: left; vertical-align: top;" | Server key
| style="text-align: left; vertical-align: top;" | .key file; Default: " "
| style="text-align: left; vertical-align: top;" | Authenticates clients to the server
|-
! style="text-align: left; vertical-align: top;" | Diffie Hellman parameters
| style="text-align: left; vertical-align: top;" | .pem file; Default: " "
| style="text-align: left; vertical-align: top;" | DH parameters define how OpenSSL performs the Diffie-Hellman (DH) key-exchange.
|-
|}
===TLS Clients===
TLS Clients is a way to more specifically differentiate clients by their '''Common Name (CN)''' found in the client certificate file. It can be used to assign specific VPN addresses to specific clients and bind them to their LAN addresses so that other device‘s in the client‘s LAN can be reached from the server or other clients.
The TLS Clients section can be found in the OpenVPN Server configuration window, provided that the OpenVPN server uses TLS or TLS/Password authentication methods. To create a new TLS client, type in the new client‘s name in the text field found bellow the TLS Clients tab and press the '''Add''' button.
[[Image:Services vpn openvpn tlsclients.PNG]]
{| class="wikitable"
|+
! style="width: 250px; background: black; color: white;" | Field name
! style="width: 250px; background: black; color: white;" | Value
! style="width: 1200px; background: black; color: white;" | Description
|-
! style="text-align: left; vertical-align: top;" | VPN instance name
| style="text-align: left; vertical-align: top;" | string; Default: " "
| style="text-align: left; vertical-align: top;" | With what VPN instance should the TLS Client be associated with
|-
! style="text-align: left; vertical-align: top;" | Endpoint name
| style="text-align: left; vertical-align: top;" | string; Default: " "
| style="text-align: left; vertical-align: top;" | Your endpoint name
|-
! style="text-align: left; vertical-align: top;" | Common name (CN)
| style="text-align: left; vertical-align: top;" | string; Default: " "
| style="text-align: left; vertical-align: top;" | Client’s Common Name (CN) found in the client’s certificate file
|-
! style="text-align: left; vertical-align: top;" | Virtual local endpoint
| style="text-align: left; vertical-align: top;" | ip; Default: " "
| style="text-align: left; vertical-align: top;" | Client’s virtual local address in the virtual network
|-
! style="text-align: left; vertical-align: top;" | Virtual remote endpoint
| style="text-align: left; vertical-align: top;" | ip; Default: " "
| style="text-align: left; vertical-align: top;" | Client’s virtual remote address in the virtual network
|-
! style="text-align: left; vertical-align: top;" | Private network
| style="text-align: left; vertical-align: top;" | ip; Default: " "
| style="text-align: left; vertical-align: top;" | Client’s private network (LAN) IP address
|-
! style="text-align: left; vertical-align: top;" | Private netmask
| style="text-align: left; vertical-align: top;" | ip; Default: " "
| style="text-align: left; vertical-align: top;" | Client’s private network (LAN) IP netmask
|-
|-
|}
|}
