Jump to content
  • EN

Template:Networking rut manual vpn: Difference between revisions

Template:Networking rut manual vpn (view source)

Revision as of 11:09, 24 October 2023

17,134 bytes removed ,  24 October 2023
m
Text replacement - "\{\{Template: Networking_rutos_manual_fw_disclosure (.*) (.*) (.*) (.*) \}\}" to "{{Template: Networking_device_manual_fw_disclosure | series = {{{series}}} | name = {{{name}}} | fw_version ={{Template: Networking_device_manual_latest_fw | series = {{{series}}} | name = {{{name}}} }} }}"
VisualWikitext
No edit summary
m (Text replacement - "\{\{Template: Networking_rutos_manual_fw_disclosure (.*) (.*) (.*) (.*) \}\}" to "{{Template: Networking_device_manual_fw_disclosure | series = {{{series}}} | name = {{{name}}} | fw_version ={{Template: Networking_device_manual_latest_fw | series = {{{series}}} | name = {{{name}}} }} }}")
 
(87 intermediate revisions by 10 users not shown)
Line 1: Line 1:
{{Template: Networking_device_manual_fw_disclosure
| series = {{{series}}}
| name  = {{{name}}}
| fw_version ={{Template: Networking_device_manual_latest_fw
| series = {{{series}}}
| name  = {{{name}}}
}}
}}
==Summary==
==Summary==


<b>Virtual Private Network</b> (<b>VPN</b>) is a method of connecting multiple private networks across the Internet. VPNs can serve to achieve many different goals, but some of its main purposes are:
<b>Virtual Private Network</b> (<b>VPN</b>) is a method of connecting multiple private networks across the Internet. VPNs can serve to achieve many different goals, but some of its main purposes are:
<ul>
<ul>
     <li>access between remote private networks;</li>
     <li>providing access between remote private networks;</li>
     <li>data encryption;</li>
     <li>providing data encryption and anonymity when browsing the Internet.</li>
    <li>anonymity when browsing the Internet.</li>
</ul>
</ul>


This page is an overview of different types of VPNs supported by {{{name}}} routers.
This chapter of the user manual provides an overview of the Firewall page for {{{name}}} devices.


==OpenVPN==
==OpenVPN==
Line 18: Line 26:
===OpenVPN client===
===OpenVPN client===
----
----
An <b>OpenVPN client</b> is an entity that initiates a connection to an OpenVPN server. To create a new client instance, go to the <i>Services → VPN → OpenVPN</i> section, select <i>Role: Client</i>, enter a custom name and click the 'Add New' button. An OpenVPN client instance with the given name will appear in the "OpenVPN Configuration" list. A maximum of six OpenVPN client instances are allowed to be added.
An <b>OpenVPN client</b> is an entity that initiates a connection to an OpenVPN server. To create a new client instance, go to the '''<i>Services → VPN → OpenVPN</i>''' section, select '''<i>Role: Client</i>''', enter a custom name and click the 'Add New' button. An OpenVPN client instance with the given name will appear in the "OpenVPN Configuration" list. A maximum of six OpenVPN client instances are allowed to be added.


To begin configuration, click the 'Edit' button next to the client instance. Refer to the figure and table below for information on the OpenVPN client's configuration fields:
To begin configuration, click the 'Edit' button next to the client instance. Refer to the figure and table below for information on the OpenVPN client's configuration fields:


[[File:{{{file_openvpn_client_config}}}]]
[[File:{{{file_openvpn_client_config}}}|border|class=tlt-border]]


<table class="nd-mantable">
<table class="nd-mantable">
Line 29: Line 37:
       <th>Value</th>
       <th>Value</th>
       <th>Description</th>
       <th>Description</th>
    </tr>
    <tr>
      <td>Enable OpenVPN config from file</td>
      <td>yes | no; default: <b>no</b></td>
      <td>Enables custom OpenVPN configuration from file.</td>
     </tr>
     </tr>
     <tr>
     <tr>
Line 64: Line 77:
       <td>yes | no; default: <b>no</b></td>
       <td>yes | no; default: <b>no</b></td>
       <td>Turns LZO data compression on or off.</td>
       <td>Turns LZO data compression on or off.</td>
    </tr>
    <tr>
      <td>Encryption</td>
      <td>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: <b>BF-CBC 128</b></td>
      <td>Algorithm used for packet encryption.</td>
     </tr>
     </tr>
     <tr>
     <tr>
Line 87: Line 95:
             </ul>
             </ul>
         </td>
         </td>
    </tr>
    <tr>
      <td>Encryption</td>
      <td>DES-CBC 64 | RC2-CBC 128 | DES-EDE-CBC 128 | DES-EDE3-CBC 192 | DESX-CBC 192 | RC2-40-CBC 40 | CAST5-CBC 128 | RC2-64-CBC 64 | AES-128-CFB 128 | AES-128-CFB1 128 | AES-128-CFB8 128 | AES-128-OFB 128 | AES-128-CBC 128 | AES-128-GCM 128 | AES-192-CFB 192 | AES-192-CFB1 192 | AES-192-CFB8 192 | AES-192-OFB 192 | AES-192-CBC 192 | AES-192-GCM 192 | AES-256-CFB 256 | AES-256-CFB1 256 | AES-256-CFB8 256 | AES-256-OFB 256 | AES-256-CBC 256 | AES-256-GCM 256 | none ; default: <b>BF-CBC 128</b></td>
      <td>Algorithm used for packet encryption.</td>
     </tr>
     </tr>
     <tr>
     <tr>
Line 147: Line 160:
         <td>string; default: <b>none</b></td>
         <td>string; default: <b>none</b></td>
         <td>Extra OpenVPN options to be used by the OpenVPN instance.</td>
         <td>Extra OpenVPN options to be used by the OpenVPN instance.</td>
    </tr>
    <tr>
    <td>Use PKCS #12 format</td>
        <td>yes | no; default: <b>no</b></td>
        <td>Use PKCS #12 archive file format to bundle all the members of a chain of trust.</td>
    </tr>
    <tr>
    <td>PKCS #12 passphrase</td>
        <td>string; default: <b>none</b></td>
        <td>Passphrase to decrypt PKCS #12 certificates.</td>
    </tr>
    <tr>
    <td>PKCS #12 certificate chain</td>
        <td>string; default: <b>none</b></td>
        <td>Uploads PKCS #12 certificate chain file.</td>
     </tr>
     </tr>
     <tr>
     <tr>
Line 155: Line 183:
     <tr>
     <tr>
       <td><span style="color: red;">TLS</span>/<span style="color: #0054a6;">Password:</span> Additional HMAC authentication</td>
       <td><span style="color: red;">TLS</span>/<span style="color: #0054a6;">Password:</span> Additional HMAC authentication</td>
       <td>yes | no; default: <b>no</b></td>
       <td>none | Authentication only (tls-auth) | Authentication and encryption (tls-crypt); default: <b>none</b></td>
       <td>An additional layer of HMAC authentication on top of the TLS control channel to protect against DoS attacks.</td>
       <td>An additional layer of HMAC authentication on top of the TLS control channel to protect against DoS attacks.</td>
     </tr>
     </tr>
Line 171: Line 199:
       <td><span style="color: red;">TLS</span>/<span style="color: #0054a6;">Password:</span> Certificate authority</td>
       <td><span style="color: red;">TLS</span>/<span style="color: #0054a6;">Password:</span> Certificate authority</td>
       <td>.ca file; default: <b>none</b></td>
       <td>.ca file; default: <b>none</b></td>
       <td>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.</td>
       <td>Certificate authority (CA) is an entity that issues digital certificates. A digital certificate certifies the ownership of a public key by the named subject of the certificate.</td>
     </tr>
     </tr>
     <tr>
     <tr>
Line 215: Line 243:
To begin configuration, click the 'Edit' button next to the server instance. Refer to the figure and table below for information on the OpenVPN server's configuration fields:
To begin configuration, click the 'Edit' button next to the server instance. Refer to the figure and table below for information on the OpenVPN server's configuration fields:


[[File:{{{file_openvpn_server_config}}}]]
[[File:{{{file_openvpn_server_config}}}|border|class=tlt-border]]


<table class="nd-mantable">
<table class="nd-mantable">
Line 222: Line 250:
       <th>Value</th>
       <th>Value</th>
       <th>Description</th>
       <th>Description</th>
    </tr>
    <tr>
      <td>Enable OpenVPN config from file</td>
      <td>yes | no; default: <b>no</b></td>
      <td>Enables custom OpenVPN configuration from file.</td>
     </tr>
     </tr>
     <tr>
     <tr>
Line 257: Line 290:
       <td>yes | no; default: <b>no</b></td>
       <td>yes | no; default: <b>no</b></td>
       <td>Turns LZO data compression on or off.</td>
       <td>Turns LZO data compression on or off.</td>
    </tr>
    <tr>
      <td>Encryption</td>
      <td>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: <b>BF-CBC 128</b></td>
      <td>Algorithm used for packet encryption.</td>
     </tr>
     </tr>
     <tr>
     <tr>
Line 279: Line 307:
             </ul>
             </ul>
         </td>
         </td>
    </tr>
    <tr>
      <td>Encryption</td>
      <td>DES-CBC 64 | RC2-CBC 128 | DES-EDE-CBC 128 | DES-EDE3-CBC 192 | DESX-CBC 192 | RC2-40-CBC 40 | CAST5-CBC 128 | RC2-64-CBC 64 | AES-128-CFB 128 | AES-128-CFB1 128 | AES-128-CFB8 128 | AES-128-OFB 128 | AES-128-CBC 128 | AES-128-GCM 128 | AES-192-CFB 192 | AES-192-CFB1 192 | AES-192-CFB8 192 | AES-192-OFB 192 | AES-192-CBC 192 | AES-192-GCM 192 | AES-256-CFB 256 | AES-256-CFB1 256 | AES-256-CFB8 256 | AES-256-OFB 256 | AES-256-CBC 256 | AES-256-GCM 256 | none ; default: <b>BF-CBC 128</b></td>
      <td>Algorithm used for packet encryption.</td>
     </tr>
     </tr>
     <tr>
     <tr>
Line 339: Line 372:
         <td>yes | no; default: <b>no</b></td>
         <td>yes | no; default: <b>no</b></td>
         <td>When enabled allows multiple clients to connect using the same certificates.</td>
         <td>When enabled allows multiple clients to connect using the same certificates.</td>
    </tr>
      <tr>
    <td>Use PKCS #12 format</td>
        <td>yes | no; default: <b>no</b></td>
        <td>Use PKCS #12 archive file format to bundle all the members of a chain of trust.</td>
    </tr>
    <tr>
    <td>PKCS #12 passphrase</td>
        <td>string; default: <b>none</b></td>
        <td>Passphrase to decrypt PKCS #12 certificates.</td>
    </tr>
    <tr>
    <td>PKCS #12 certificate chain</td>
        <td>string; default: <b>none</b></td>
        <td>Uploads PKCS #12 certificate chain file.</td>
     </tr>
     </tr>
     <tr>
     <tr>
Line 379: Line 427:
         <td>.pem file | .crl file; default: <b>none</b></td>
         <td>.pem file | .crl file; default: <b>none</b></td>
         <td>A certificate revocation list (CRL) file is a list of certificates that have been revoked by the certificate authority (CA). It indicates which certificates are no longer acccepted by the CA and therefore cannot be authenticated to the server.</td>
         <td>A certificate revocation list (CRL) file is a list of certificates that have been revoked by the certificate authority (CA). It indicates which certificates are no longer acccepted by the CA and therefore cannot be authenticated to the server.</td>
    </tr>
    <tr>
    <td><span style="color: red;">TLS</span>/<span style="color: #0054a6;">TLS/Password:</span> Enable manual ccd upload</td>
        <td>yes | no; default: <b>no</b></td>
        <td>Enable manual upload of client-config-dir files.</td>
     </tr>
     </tr>
</table>
</table>
Line 400: Line 453:
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 click the 'Add' button. Refer to the figure and table below for information on the TLS Clients' configuration fields:
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 click the 'Add' button. Refer to the figure and table below for information on the TLS Clients' configuration fields:


[[File:{{{file_openvpn_tls_clients_config}}}]]
[[File:{{{file_openvpn_tls_clients_config}}}|border|class=tlt-border]]


<table class="nd-mantable">
<table class="nd-mantable">
Line 407: Line 460:
       <th>Value</th>
       <th>Value</th>
       <th>Description</th>
       <th>Description</th>
    </tr>
    <tr>
      <td>VPN instance name</td>
      <td>string; default: <b>none</b></td>
      <td>Indicates which OpenVPN instance the TLS Client will be associated with. When left empty, this field is filled automatically.</td>
     </tr>
     </tr>
     <tr>
     <tr>
Line 445: Line 493:
</table>
</table>


==IPsec==
{{#ifeq:{{{series}}}|RUT9XX||{{Template:Networking_rut2xx_manual_vpn_ipsec
| file_ipsec_config          = {{{file_ipsec_config}}}
| file_ipsec_phase          = {{{file_ipsec_phase}}}
| file_ipsec_main_mode      = {{{file_ipsec_main_mode}}}
| file_ipsec_aggressive_mode = {{{file_ipsec_aggressive_mode}}}
| file_ipsec_psk            = {{{file_ipsec_psk}}}
}}}}


To create a new IPsec instance, go to the <i>Services → VPN → IPsec</i> section, enter a custom name and click "Add". An IPsec instance with the given name will appear in the "IPsec Configuration" list.
{{#ifeq:{{{series}}}|RUT2XX||{{Template:Networking_rut9xx_manual_vpn_ipsec
| file_ipsec_config          = {{{file_ipsec_config}}}
| file_ipsec_phase          = {{{file_ipsec_phase}}}
| file_ipsec_main_mode      = {{{file_ipsec_main_mode}}}
| file_ipsec_aggressive_mode = {{{file_ipsec_aggressive_mode}}}
| file_ipsec_psk            = {{{file_ipsec_psk}}}
}}}}


To begin configuration, click the 'Edit' button located next to the instance.
{{#ifeq:{{{series}}}|RUT9XX||{{Template:Networking_rutxxx_manual_vpn_gre
| file_gre_config_main      = {{{file_gre_config_main}}}
| file_gre_config_routing  = {{{file_gre_config_routing}}}
}}}}


===IPsec configuration===
{{#ifeq:{{{series}}}|RUT2XX||{{Template:Networking_rut9xx_manual_vpn_gre
----
| file_gre_config_main      = {{{file_gre_config_main}}}
The <b>IPsec configuration</b> section is used to configure the main parameters of an IPsec connection. Refer to the figure and table below for information on the configuration fields located in the general settings section.
| file_gre_config_routing  = {{{file_gre_config_routing}}}
 
}}}}
[[File:{{{file_ipsec_config}}}]]
 
<table class="nd-mantable">
    <tr>
        <th>Field</th>
      <th>Value</th>
      <th>Description</th>
    </tr>
    <tr>
    <td>Enable</td>
        <td>yes | no; default: <b>no</b></td>
        <td>Turns the IPsec instance on or off.</td>
    </tr>
    <tr>
    <td>IKE version</td>
        <td>IKEv1 | IKEv2; default: <b>IKEv1</b></td>
        <td>Internet Key Exchange (IKE) version used for key exchange.
            <ul>
                <li><b>IKEv1</b> - more commonly used but contains known issues, for example, dealing with NAT.</li>
                <li><b>IKEv2</b> - updated version with increased and improved capabilities, such as integrated NAT support, supported multihosting, deprecated exchange modes (does not use main or aggressive mode; only 4 messages required to establish a connection).</li>
            </ul>
        </td>
    </tr>
    <tr>
      <td>Mode</td>
      <td>Main | Aggressive; default: <b>Main</b></td>
      <td>Internet Security and Key Management Protocol (ISAKMP) phase 1 exchange mode.
            <ul>
                <li><b>Main</b> - performs three two-way exchanges between the initiator and the receiver (a total of 9 messages).</li>
                <li><b>Aggressive</b> - performs fewer exchanges than main mode (a total of 6 messages) by storing most data into the first exchange. In aggressive mode, the information is exchanged before there is a secure channel, making it less secure but faster than main mode.</li>
            </ul>
        </td>
    </tr>
    <tr>
      <td>Type</td>
      <td>Tunnel | Transport; default: <b>Tunnel</b></td>
      <td>Type of connection.
            <ul>
                <li><b>Tunnel</b> - protects internal routing information by encapsulating the entire IP packet (IP header and payload); commonly used in site-to-site VPN connections; supports NAT traversal.</li>
                <li><b>Transport</b> - only encapsulates IP payload data; used in client-to-site VPN connections; does not support NAT traversal; usually implemented with other tunneling protocols (for example, L2TP).</li>
            </ul>
        </td>
    </tr>
    <tr>
    <td>My identifier type</td>
        <td>FQDN | User FQDN | Address; default: <b>FQDN</b></td>
        <td>Defines the type of identity used in user (IPsec instance) authentication.
            <ul>
                <li><b>FQDN</b> - identity defined by fully qualified domain name. It is the complete domain name for a host (for example, <i>something.somedomain.com</i>). Only supported with IKEv2.</li>
                <li><b>User FQDN</b> - identity defined by fully qualified username string (for example, <i>[email protected]</i>). Only supported with IKEv2.</li>
                <li><b>Address</b> - identity by IP address.</li>
            </ul>
        </td>
    </tr>
    <tr>
    <td>On startup</td>
        <td>Ignore | Add | Route | Start; default: <b>Start</b></td>
        <td>Defines how the instance should act on router startup.
            <ul>
                <li><b>Ignore</b> - does not start the tunnel.</li>
                <li><b>Add</b> - loads a connection without starting it.</li>
                <li><b>Route</b> - starts the tunnel only if there is traffic.</li>
                <li><b>Start</b> - starts the tunnel on router startup.</li>
            </ul>
        </td>
    </tr>
    <tr>
    <td>My identifier</td>
        <td>ip | string; default: <b>none</b></td>
        <td>Defines how the user (IPsec instance) will be identified during authentication.</td>
    </tr>
    <tr>
      <td><span style="color: red;">Tunnel:</span> Local IP address/Subnet mask</td>
      <td>ip/netmask | default: <b>none</b></td>
      <td>Local IP address and subnet mask used to determine which part of the network can be accessed in the VPN network. Netmask range [0..32]. If left empty, IP address will be selected automatically.</td>
    </tr>
    <tr>
      <td>Left firewall</td>
      <td>off | on; default: <b>on</b></td>
      <td>Adds neccessary firewall rules to allow traffic of this IPsec instance on this router.</td>
    </tr>
    <tr>
    <td>Force encapsulation</td>
        <td>yes | no; default: <b>no</b></td>
        <td>Forces UDP encapsulation for ESP packets even if a "no NAT" situation is detected.</td>
    </tr>
    <tr>
    <td>Dead Peer Detection</td>
        <td>yes | no; default: <b>no</b></td>
        <td>A function used during Internet Key Exchange (IKE) to detect a "dead" peer. It used to reduce traffic by minimizing the number of messages when the opposite peer in unavailable and as failover mechanism.</td>
    </tr>
    <tr>
    <td><span style="color: #0054a6;">Dead Peer Detection:</span> Delay (sec)</td>
        <td>integer; default: <b>none</b></td>
        <td>The frequency of checking whether a peer is still availaible or not.</td>
    </tr>
    <tr>
    <td><span style="color: #0054a6;">Dead Peer Detection:</span> Timeout (sec)</td>
        <td>integer; default: <b>none</b></td>
        <td>Time limit after which the IPsec instance will stop checking the availability of a peer and determine it to be "dead" if no response is received.</td>
    </tr>
    <tr>
      <td>Remote VPN endpoint</td>
      <td>host | ip; default: <b>none</b></td>
      <td>IP address or hostname of the remote IPsec instance.</td>
    </tr>
    <tr>
    <td><span style="color: red;">Tunnel:</span> Remote IP address/subnet mask</td>
        <td>ip/netmask; default: <b>none</b></td>
        <td>Remote network IP address and subnet mask used to determine which part of the network can be accessed in the VPN network. Netmask range [0..32]. This value must differ from the device’s LAN IP.</td>
    </tr>
    <tr>
    <td>Right firewall</td>
        <td>yes | no; default: <b>yes</b></td>
        <td>Adds neccessary firewall rules to allow traffic of from the opposite IPsec instance on this router.</td>
    </tr>
    <tr>
    <td><span style="color: purple;">Transport:</span> Use with DMVPN</td>
        <td>yes | no; default: <b>no</b></td>
        <td>Adds several necessary options to make DMVPN work.</td>
    </tr>
    <tr>
      <td>Enable keepalive</td>
      <td>yes | no; default: <b>no</b></td>
      <td>When enabled, the instance sends ICMP packets to the specified host at the specified frequency. If no response is received, the router will attempt to restart the connection.</td>
    </tr>
    <tr>
      <td>Host</td>
      <td>host | ip; default: <b>none</b></td>
      <td>Hostname or IP address to which keepalive ICMP packets will be sent to.</td>
    </tr>
    <tr>
    <td>Ping period (sec)</td>
        <td>integer [0..9999999]; default: <b>none</b></td>
        <td>The frequency at which keepalive ICMP packets will be sent to the specified host or IP address.</td>
    </tr>
    <tr>
    <td>Allow WebUI access</td>
        <td>yes | no; default: <b>no</b></td>
        <td>Allows WebUI access for hosts in the VPN network.</td>
    </tr>
    <tr>
    <td>Custom options</td>
        <td>ipsec options; default: <b>none</b></td>
        <td>Provides the possibility to further customize the connection by adding extra IPsec options.</td>
    </tr>
</table>
 
<b>Additional notes</b>:
<ul>
    <li>Some configuration fields become available only when certain other parameters are selected. The names of the parameters are followed by a prefix that specifies the authentication type under which they become visible. Different color codes are used for different prefixes:
        <ul>
            <li>Red for <span style="color: red;">Type: Tunnel</span></li>
            <li>Purple for <span style="color: purple;">Type: Transport</span></li>
            <li>Blue for <span style="color: #0054a6;">Dead Peer Detection: Enabled</span></li>
        </ul>
    </li>
    <li>After changing any of the parameters, don't forget to click the <b>Save</b> button located at the bottom-right side of the page.</li>
</ul>
 
===Phase settings===
----
IKE (Internet Key Exchange) is a protocol used to set up security associations (SAs) for the IPsec connection. This process is required before the IPsec tunnel can be established. It is done in two phases:
 
<table border=1; style="border-collapse: collapse;">
    <tr>
        <th width=400><span style="color: #0054A6;">Phase</span></th>
        <th colspan="2"><span style="color: #0054A6;">Mode</span></th>
    </tr>
    <tr style="vertical-align: top;">
        <td><b>Phase 1</b>
            <ul>
                <li>Establishes a secure channel between peers</li>
                <li>Authenticates peers</li>
                <li>Negotiates SA policy</li>
                <li>Shares secret keys</li>
                <li>Establishes secure tunnel for phase 2</li>
            </ul>
        </td>
        <td width=350>Main mode (figure 1)
            <ul>
                <li>6 packets exchanged</li>
                <li>Identity protected during exchange</li>
            </ul>
        </td>
        <td width=350>Aggressive mode (figure 2)
            <ul>
                <li>3 packets exchanged</li>
                <li>Identity information exchanged before a secure channel is established</li>
            </ul>
        </td>
    </tr>
    <tr style="vertical-align: top;">
        <td><b>Phase 2</b>
            <ul>
                <li>Sets up matching IPsec SAs</li>
                <li>Periodically renegotiates IPsec SAs</li>
            </ul>
        </td>
        <td colspan="2">Quick mode
            <ul>
                <li>3 packets exchanged</li>
                <li>IPsec SA parameters (ESP/AH, SHA/MD5) established</li>
                <li>SA lifetime set</li>
            </ul>
        </td>
    </tr>
</table>
<br>
<table>
    <tr>
        <td><b>Figure 1</b></td>
        <td><b>Figure 2</b></td>
    </tr>
    <tr>
        <td width=500>[[File:{{{file_ipsec_main_mode}}}]]</td>
        <td width=500>[[File:{{{file_ipsec_aggressive_mode}}}]]</td>
    </tr>
</table>
----
[[File:{{{file_ipsec_phase}}}]]
 
<table class="nd-mantable">
    <tr>
        <th>Field</th>
      <th>Value</th>
      <th>Description</th>
    </tr>
    <tr>
    <td>Encryption algorithm</td>
        <td>DES | 3DES | AES128 | AES192 | AES256; default: <b>3DES</b></td>
        <td>Algorithm used for data encryption.</td>
    </tr>
    <tr>
    <td>Authentication/Hash algorithm</td>
        <td>MD5 | SHA1 | SHA256 | SHA384 | SHA512; default: <b>SHA1</b></td>
        <td>Algorithm used for exchanging authentication and hash information.</td>
    </tr>
    <tr>
    <td>DH group/PFS group</td>
        <td>MODP768 | MODP1024 | MODP1536 | MODP2048 | MODP3072 | MODP4096; default: <b>MODP1536</b></td>
        <td>Diffie-Hellman (DH) group used in the key exchange process. Higher group numbers provide more security, but take longer and use more resources to compute the key.</td>
    </tr>
    <tr>
    <td>Lifetime</td>
        <td>integer; default: <b>8 hours</b></td>
        <td>Defines a time period after which the phase will re-initiate its exchange of information.</td>
    </tr>
</table>
 
===Pre-shared keys===
----
A <b>pre-shared key</b> is a secret password used for authentication between IPsec peers before a secure tunnel is established. To create a new key, click the 'Add' button.
 
The figure below is an example of the Pre-shared keys section and the table below provides information on configuration fields contained in that section:
 
[[File:{{{file_ipsec_psk}}}]]
 
<table class="nd-mantable">
    <tr>
        <th>Field</th>
      <th>Value</th>
      <th>Description</th>
    </tr>
    <tr>
    <td>Pre-shared key</td>
        <td>string; default: <b>none</b></td>
        <td>A shared password used for authentication between IPsec peers before a secure channel is established.</td>
    </tr>
    <tr>
    <td>Secret's ID selector</td>
        <td>string; default: <b>none</b></td>
        <td>Each secret can be preceded by a list of optional ID selectors. A selector is an IP address, a Fully Qualified Domain Name, user@FQDN or %any.<br><b>NOTE</b>: IKEv1 only supports IP address ID selector.</td>
    </tr>
</table>
 
==GRE Tunnel==
 
<b>Generic Routing Encapsulation</b> (<b>GRE</b>) is a tunneling protocol used to establish point-to-point connections between remote private networks. GRE tunnels encapsulate data packets in order to route other protocols over IP networks.
 
===GRE: main & tunnel settings===
----
To create a new GRE Tunnel instance, go to the <i>Services → VPN → GRE Tunnel</i> section, enter a custom name and click the 'Add' button. A GRE instance with the given name will appear in the "GRE Configuration" list.
 
To begin configuration, click the 'Edit' button located next to the instance. Refer to the figure and table below for information on the fields located in the GRE Tunnel instance configuration section.
 
[[File:{{{file_gre_config_main}}}]]
 
<table class="nd-mantable">
    <tr>
        <th>Field</th>
      <th>Value</th>
      <th>Description</th>
    </tr>
    <tr>
    <td>Enabled</td>
        <td>yes | no; default: <b>no</b></td>
        <td>Turns the GRE Tunnel instance on or off.</td>
    </tr>
    <tr>
      <td>Tunnel source</td>
      <td>network interface; default: <b>none</b></td>
      <td>Network interface used to establish the GRE Tunnel.</td>
    </tr>
    <tr>
    <td>Remote endpoint IP address</td>
        <td>ip; default: <b>none</b></td>
        <td>External IP address of another GRE instance used to establish the initial connection between peers.</td>
    </tr>
    <tr>
      <td>MTU</td>
      <td>integer; default: <b>1476</b></td>
      <td>Sets the maximum transmission unit (MTU) size. It is the largest size of a protocol data unit (PDU) that can be transmitted in a single network layer transaction.</td>
    </tr>
    <tr>
    <td>TTL</td>
        <td>integer [0..255]; default: <b>255</b></td>
        <td>Sets a custom TTL (Time to Live) value for encapsulated packets. TTL is a field in the IP packet header which is initially set by the sender and decreased by 1 on each hop. When it reaches 0 it is dropped and the last host to receive the packet sends an ICMP "Time Exceeded" message back to the source.</td>
    </tr>
    <tr>
    <td>Outbound key</td>
        <td>integer [0..65535]; default: <b>none</b></td>
        <td>A key used to identify outgoing packets. A This value should match the "Inbound key" value set on the opposite GRE instance or both key values should be omitted on both sides.</td>
    </tr>
    <tr>
    <td>Inbound key</td>
        <td>integer [0..65535]; default: <b>none</b></td>
        <td>A key used to identify incoming packets. This value should match the "Outbound key" value set on the opposite GRE instance or both key values should be omitted on both sides.</td>
    </tr>
    <tr>
    <td>Don't fragment</td>
        <td>yes | no; default: <b>yes</b></td>
        <td>When unchecked, sets the <i>nopmtudisc</i> option for tunnel. Can not be used together with the TTL option.</td>
    </tr>
    <tr>
    <td>Keep alive</td>
        <td>yes | no; default: <b>no</b></td>
        <td>Turns "keep alive" on or off. The "keep alive" feature sends packets to the remote instance in order to determine the health of the connection. If no response is received, the device will attempt to re-establish the tunnel.</td>
    </tr>
    <tr>
    <td>Keep alive interval</td>
        <td>integer [0..255]; default: <b>none</b></td>
        <td>Frequency (in seconds) at which "keep alive" packets are sent to the remote instance.</td>
    </tr>
    <tr>
    <td>Local GRE interface IP address</td>
        <td>ip; default: <b>none</b></td>
        <td>IP address of the local GRE Tunnel network interface.</td>
    </tr>
    <tr>
    <td>Local GRE interface netmask</td>
        <td>netmask; default: <b>none</b></td>
        <td>Subnet mask of the local GRE Tunnel network interface.</td>
    </tr>
</table>
 
===GRE: routing settings===
----
<b>Routing settings</b> are used to configure routes to networks that are behind the device that hosts the opposite GRE instance. To add a new route, simply click the 'Add' button. For information on configuring the route refer to the figure and table below.
 
[[File:{{{file_gre_config_routing}}}]]
 
<table class="nd-mantable">
    <tr>
        <th>Field</th>
      <th>Value</th>
      <th>Description</th>
    </tr>
    <tr>
    <td>Remote subnet IP address</td>
        <td>ip; default: <b>none</b></td>
        <td>IP address of the network behind the device that hosts the remote GRE instance.</td>
    </tr>
    <tr>
    <td>Remote subnet netmask</td>
        <td>netmask; default: <b>none</b></td>
        <td>Subnet mask of the network behind the device that hosts the remote GRE instance.</td>
    </tr>
</table>


==PPTP==
==PPTP==
Line 884: Line 568:
     </tr>
     </tr>
</table>
</table>
[[Category:{{{name}}} WebUI]]


===PPTP server===
===PPTP server===
Line 925: Line 607:
     <tr>
     <tr>
       <td>User name</td>
       <td>User name</td>
       <td>string; default: <b>user</b></td>
       <td>string; default: <b>youruser</b></td>
       <td>Username used for authentication to this PPTP server.</td>
       <td>Username used for authentication to this PPTP server.</td>
     </tr>
     </tr>
     <tr>
     <tr>
       <td>Password</td>
       <td>Password</td>
       <td>string; default: <b>pass</b></td>
       <td>string; default: <b>yourpass</b></td>
       <td>Password used for authentication to this PPTP server.</td>
       <td>Password used for authentication to this PPTP server.</td>
     </tr>
     </tr>
Line 942: Line 624:
==L2TP==
==L2TP==


In computer networking, <b>Layer 2 Tunneling Protocol</b> (<b>L2TP</b>) is a tunneling protocol used to support virtual private networks (VPNs). It is more secure than PPTP but, because it encapsulates the transferred data twice, but it is slower and uses more CPU power.
In computer networking, <b>Layer 2 Tunneling Protocol</b> (<b>L2TP</b>) is a tunneling protocol  
used to support virtual private networks (VPNs). It is more secure than PPTP but, because  
it encapsulates the transferred data twice, but it is slower and uses more CPU power.


===L2TP client===
===L2TP client===
----
----
An <b>L2TP client</b> is an entity that initiates a connection to an L2TP server. To create a new client instance, go to the <i>Services → VPN → L2TP</i> section, select <i>Role: Client</i>, enter a custom name and click the 'Add New' button. An L2TP client instance with the given name will appear in the "L2TP Configuration" list.
An <b>L2TP client</b> is an entity that initiates a connection to an L2TP server. To  
create a new client instance, go to the <i>Services → VPN → L2TP</i> section, select  
<i>Role: Client</i>, enter a custom name and click the 'Add New' button. An L2TP client  
instance with the given name will appear in the "L2TP Configuration" list.


To begin configuration, click the 'Edit button located next to the client instance. Refer to the figure and table below for information on the L2TP client's configuration fields:
To begin configuration, click the 'Edit button located next to the client instance. Refer  
to the figure and table below for information on the L2TP client's configuration fields:


[[File:{{{file_l2tp_client_config}}}]]
[[File:Networking_{{lc:{{{series}}}}}_vpn_l2tp_client_configuration_v1.png|border|class=tlt-border]]


<table class="nd-mantable">
<table class="nd-mantable">
Line 971: Line 659:
       <td>Username</td>
       <td>Username</td>
       <td>string; default: <b>none</b></td>
       <td>string; default: <b>none</b></td>
       <td>Username used for authentication to the L2TP server.</td>
       <td>Username used in authorization to the L2TP server.</td>
     </tr>
     </tr>
     <tr>
     <tr>
       <td>Password</td>
       <td>Password</td>
       <td>string; default: <b>none</b></td>
       <td>string; default: <b>none</b></td>
       <td>Password used for authentication to the L2TP server.</td>
       <td>Password used in authorization to the L2TP server.</td>
    </tr>
    <tr>
      <td>Authentication</td>
      <td>string; default: <b>none</b></td>
      <td>Optional. Password used in L2TP tunnel CHAP authentication.</td>
     </tr>
     </tr>
     <tr>
     <tr>
Line 989: Line 682:
     </tr>
     </tr>
</table>
</table>
[[Category:{{{name}}} WebUI]]


===L2TP server===
===L2TP server===
Line 1,000: Line 691:
To begin configuration, click the 'Edit' button located next to the server instance. Refer to the figure and table below for information on the L2TP server's configuration fields:
To begin configuration, click the 'Edit' button located next to the server instance. Refer to the figure and table below for information on the L2TP server's configuration fields:


[[File:{{{file_l2tp_server_config}}}]]
[[File:Networking_rutxxx_vpn_l2tp_server_configuration_v1.png]]


<table class="nd-mantable">
<table class="nd-mantable">
Line 1,045: Line 736:
</table>
</table>


==Stunnel==
==SSTP==


<b>Stunnel</b> is an open-source a proxy service that adds TLS encryption to clients and servers already existing on a VPN network. TLS encryption provided by Stunnel can be used as an additional layer of encryption for data sent by OpenVPN. This procedure increases the security of the established connection and provides higher chances of passing a Deep packet inspection (DPI) check.  
<b>Secure Socket Tunneling Protocol</b> (<b>SSTP</b>) is a VPN protocol designed to transport PPP traffic via a secure SSL/TLS channel.


For a more in-depth Stunnel configuration example visit this page: [[OpenVPN over Stunnel {{{name}}}|OpenVPN over Stunnel]].
===SSTP configuration===
----
To create a new SSTP instance, go to the <i>Services → VPN → SSTP</i> section, enter a custom name and click the 'Add' button. An SSTP instance with the given name will appear in the "SSTP Configuration" list.


===Stunnel Globals===
To begin configuration, click the 'Edit' button located next to the instance. Refer to the figure and table below for information on the SSTP instance's configuration fields:
----
The <b>Stunnel Globals</b> section is used to manage the Stunnel service as a whole. Refer to the figure and table below for information on the field contained in the Stunnel Globals section.


[[File:{{{file_stunnel_globals}}}]]
[[File:{{{file_sstp_config}}}]]


<table class="nd-mantable">
<table class="nd-mantable">
     <tr>
     <tr>
         <th>Field Name</th>
         <th>Field</th>
         <th>Value</th>
         <th>Value</th>
         <th>Description</th>
         <th>Description</th>
Line 1,066: Line 757:
         <td>Enabled</td>
         <td>Enabled</td>
         <td>yes | no; default: <b>no</b></td>
         <td>yes | no; default: <b>no</b></td>
         <td>Turns the Stunnel service on or off. If this is unchecked, Stunnel instances will not start (even if they are enabled individually); therefore, iti is necessary to check this field in order to make Stunnel active on the router.</td>
         <td>Turns the SSTP instance on or off.</td>
     </tr>
     </tr>
     <tr>
     <tr>
         <td>Debug Level</td>
         <td>Use as default gateway</td>
        <td>integer [0..7]; default: <b>5</b></td>
        <td>Debugging to log output level.
       
Level is one of the syslog level names or numbers emerg (0), alert (1), crit (2), err (3), warning (4), notice (5), info (6), or debug (7). All logs for the specified level and all levels numerically less than it will be shown. Use '''7''' for greatest debugging output.</td>
    </tr>
    <tr>
        <td>Use alternative config</td>
         <td>yes | no; default: <b>no</b></td>
         <td>yes | no; default: <b>no</b></td>
         <td>Turns the possibility to upload an external Stunnel configuration file on or off.if you turn this on, other Stunnel configurations present in the router will become inactive.</td>
         <td>When turned on, this connection will become the router's default route. This means that all traffic directed to the Internet will go through the L2TP server and the server's IP address will be seen as this device's source IP to other hosts on the Internet.<br><b>NOTE</b>: this can only be used when [[{{{name}}} _WAN#Operation_Modes|WAN Failover]] is turned off.</td>
    </tr>
    <tr>
        <td>Upload alternative config</td>
        <td>file; default: <b>none</b></td>
        <td>Uploads an Stunnel configuration file.</td>
     </tr>
     </tr>
</table>
===Stunnel client/server===
----
[[File:{{{file_stunnel_client_server_config}}}]]
<table class="nd-mantable">
     <tr>
     <tr>
         <th>Field</th>
         <td>Server IP address</td>
         <th>Value</th>
         <td>ip | host; default: <b>none</b></td>
         <th>Description</th>
         <td>IP address or hostname of an SSTP server.</td>
     </tr>
     </tr>
     <tr>
     <tr>
         <td>Enable</td>
         <td>Username</td>
        <td>yes | no; default: <b>no</b></td>
        <td>Turns the Stunnel instance on or off.</td>
    </tr>
    <tr>
        <td>Operating Mode</td>
        <td>Server | Client; default: <b>Server</b></td>
        <td>Selects the Stunnel instance's role.
            <ul>
                <li><b>Server</b> - </li>
                <li><b>Client</b> - </li>
            </ul>
        </td>
    </tr>
    <tr>
        <td>Listen IP</td>
        <td>ip; default: <b>none</b></td>
        <td>Makes the instance "listen" for incoming connections on the specified IP address. When left empty, the value of this field defaults to <i>localhost</i> (<i>127.0.0.1</i>).</td>
    </tr>
    <tr>
        <td>Listen Port</td>
        <td>integer [0..65535]; default: <b>none</b></td>
        <td>Makes the instance "listen" for incoming connections on the specified TCP port. Make sure you chose a port that is not being used by another service. You will also have to allow traffic on the specified port. You can do this via the <b>Network → Firewall → Traffic Rulles → [[{{{name}}}_Firewall#Open_Ports_On_Router|Open Ports On Router]]</b> section.</td>
    </tr>
    <tr>
        <td>Connect IP's</td>
        <td>ip:port; default: <b>none</b></td>
        <td>Uses the standard host:port convetion (e.g. 127.0.0.1:6001; localhost:6001). Host part can be emmited - empty host part defaults to '''localhost'''.
 
Must contain at least one item. If multiple options are specified, remote address is chosen using a round-robin algorithm.</td>
    </tr>
    <tr>
        <td>TLS Cipher</td>
        <td>None | Secure | Custom; default: <b>None</b></td>
        <td>Packet encryption algorithm cipher.</td>
    </tr>
    <tr>
        <td>Allowed TLS Ciphers</td>
         <td>string; default: <b>none</b></td>
         <td>string; default: <b>none</b></td>
         <td>A list of TLS ciphers accepted for this connection.</td>
         <td>Username used for authentication to the SSTP server.</td>
     </tr>
     </tr>
     <tr>
     <tr>
         <td>Application Protocol</td>
         <td>Password</td>
        <td>Connect | SMTP | Not specified; default: <b>Not specified</b></td>
        <td>This option enables initial, protocol-specific negotiation of the TLS encryption. The protocol option should not be used with TLS encryption on a separate port.</td>
    </tr>
    <tr>
        <td>Protocol Authentication</td>
        <td><b>Connect</b>: Basic | NTLM; default: <b>Basic</b><br><b>SMTP</b>: Plain | Login; default: <b>Plain</b></td>
        <td>Authentication type for the protocol negotiations.</td>
    </tr>
    <tr>
        <td>Protocol Domain</td>
         <td>string; default: <b>none</b></td>
         <td>string; default: <b>none</b></td>
         <td>Domain for the protocol negotiations.</td>
         <td>Password used for authentication to the SSTP server.</td>
    </tr>
    <tr>
        <td>Protocol Host</td>
        <td>host:port; default: <b>none</b></td>
        <td>Specifies the final TLS server to be connected to by the proxy, and not the proxy server directly connected by Stunnel. The proxy server should be specified along with the <i>connect</i> option.</td>
     </tr>
     </tr>
     <tr>
     <tr>
         <td>Protocol Username</td>
         <td>CA cert</td>
        <td>string; Default: <b>none</b></td>
        <td>Username for authentication to the protocol negotiations.</td>
    </tr>
    <tr>
        <td>Protocol Password</td>
        <td>string; default: <b>none</b></td>
        <td>Password for authentication to the protocol negotiations.</td>
    </tr>
    <tr>
        <td>Certificate File</td>
         <td>.crt file; default: <b>none</b></td>
         <td>.crt file; default: <b>none</b></td>
         <td>TLS client or server certificate file.</td>
         <td>Uploads a Certificate authority (CA) file.</td>
    </tr>
    <tr>
        <td>Private Key</td>
        <td>.key file; default: <b>none</b></td>
        <td>TLS client or server key file.</td>
     </tr>
     </tr>
</table>
</table>


{{#ifeq:{{{series}}}|RUT2xx||{{Template:Networking_rutxxx_manual_vpn_dmvpn
{{#ifeq:{{{series}}}|RUT2XX||{{Template:Networking_rut9xx_manual_vpn_stunnel
| file_stunnel_globals    = {{{file_stunnel_globals}}}
| file_stunnel_client_server_config  = {{{file_stunnel_client_server_config}}}
| name = {{{name}}}
}}}}
 
{{#ifeq:{{{series}}}|RUT9XX||{{Template:Networking_rut2xx_manual_vpn_stunnel
| file_stunnel_globals    = {{{file_stunnel_globals}}}
| file_stunnel_client_server_config  = {{{file_stunnel_client_server_config}}}
| name = {{{name}}}
}}}}
 
{{#ifeq:{{{series}}}|RUT2XX||{{Template:Networking_rutxxx_manual_vpn_dmvpn
| file_dmvpn_config      = {{{file_dmvpn_config}}}
| file_dmvpn_config      = {{{file_dmvpn_config}}}
| file_dmvpn_gre_config  = {{{file_dmvpn_gre_config}}}
| file_dmvpn_gre_config  = {{{file_dmvpn_gre_config}}}
Line 1,189: Line 805:
}}}}
}}}}


[[Category:{{{name}}} WebUI]]
{{Template:Networking_rutxxx_manual_vpn_zerotier
| name                  = {{{name}}}
| file_zerotier_general = {{{file_zerotier_general}}}
| file_zerotier_vpn    = {{{file_zerotier_vpn}}}
}}
 
[[Category:{{{name}}} Services section]]
Retrieved from "https://wiki.teltonika-networks.com/view/Special:MobileDiff/39213...115112"