Jump to content
  • EN

RUT950 VPN: Difference between revisions

RUT950 VPN (view source)

Revision as of 12:56, 19 July 2021

10,518 bytes removed ,  19 July 2021
Replaced content with "{{Template: Networking_rutos_manual_vpn <!------------------------DEVICE-----------------------> | name = RUT950 | series = RUT9 }}"
VisualWikitext
No edit summary
(Replaced content with "{{Template: Networking_rutos_manual_vpn <!------------------------DEVICE-----------------------> | name = RUT950 | series = RUT9 }}")
Tag: Replaced
(11 intermediate revisions by 5 users not shown)
Line 1: Line 1:
{{Template: Networking_rutxxx_manual_vpn
{{Template: Networking_rutos_manual_vpn
<!----------------------------DEVICE DETAILS---------------------------->
<!------------------------DEVICE----------------------->
| name                             = RUT950
| name   = RUT950
| series                           = RUT9xx
| series = RUT9
<!--------------------------------OPENVPN------------------------------->
| file_openvpn_client_config        = Networking_rutxxx_vpn_openvpn_client_configuration_v2.png
| file_openvpn_server_config        = Networking_rutxxx_vpn_openvpn_server_configuration_v2.png
| file_openvpn_tls_clients_config  = Networking_rutxxx_vpn_openvpn_tls_clients_configuration_v2.png
<!---------------------------------IPsec-------------------------------->
| file_ipsec_config                = Networking_rutxxx_vpn_ipsec_ipsec_configuration_v2.png
| file_ipsec_phase                  = Networking_rutxxx_vpn_ipsec_ipsec_configuration_phase_v2.png
| file_ipsec_psk                    = Networking_rutxxx_vpn_ipsec_pre-shared_keys_v2.png
| file_ipsec_main_mode              = Networking_device_vpn_ipsec_main_mode_scheme_v3.png
| file_ipsec_aggressive_mode        = Networking_device_vpn_ipsec_aggressive_mode_scheme_v4.png
<!-------------------------------GRE Tunnel----------------------------->
| file_gre_config_main              = Networking_rutxxx_vpn_gre_gre_configuration_main_settings_v1.png
| file_gre_config_routing          = Networking_rutxxx_vpn_gre_gre_configuration_routing_settings_v1.png
<!---------------------------------PPTP--------------------------------->
| file_pptp_client_config          = Networking_rutxxx_vpn_pptp_client_configuration_v1.png
| file_pptp_server_config          = Networking_rutxxx_vpn_pptp_server_configuration_v1.png
<!---------------------------------L2TP--------------------------------->
| file_l2tp_client_config          = Networking_rutxxx_vpn_l2tp_client_configuration_v1.png
| file_l2tp_server_config          = Networking_rutxxx_vpn_l2tp_server_configuration_v1.png
<!---------------------------------DMVPN-------------------------------->
| file_dmvpn_config                = Networking_rutx_vpn_dmvpn_dmvpn_parameters_configuration_v1.png
| file_dmvpn_gre_config            = Networking_rutxxx_vpn_dmvpn_gre_parameters_configuration_v1.png
| file_dmvpn_ipsec_config          = Networking_rutxxx_vpn_dmvpn_ipsec_parameters_configuration_v1.png
| file_dmvpn_nhrp_config            = Networking_rutxxx_vpn_dmvpn_nhrp_parameters_configuration_v1.png
}}
}}
==Stunnel Configuration==
Default Stunnel configuration:
[[Image:stunnel_default_config.png]]
Stunnel configuration field explanation table:
<table class="nd-mantable">
    <tr>
        <th>Field Name</th>
        <th>Value</th>
        <th>Description</th>
    </tr>
    <tr>
        <td>Enabled</td>
        <td>yes | no; Default: '''no'''</td>
        <td>Enables the Stunnel configuration.</td>
    </tr>
    <tr>
        <td>Operating Mode</td>
        <td>Client | Server; Default: ""</td>
        <td>Specifies whether this configuration will be used for Stunnel client or server.</td>
    </tr>
    <tr>
        <td>Listen IP</td>
        <td>ip | host; Default: ""</td>
        <td>'''OPTIONAL'''
Specifies which IP address or host should Stunnel listen to. If left empty, defaults to '''localhost'''.</td>
    </tr>
    <tr>
        <td>Listen Port</td>
        <td>port (integer [0..65535]); Default: ""</td>
        <td>Specifies TCP port which Stunnel should listen to. '''Port cannot be taken by another service!'''</td>
    </tr>
    <tr>
        <td>Connect IP's</td>
        <td>[host:]port; Default: ""</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</td>
        <td>Select permitted TLS ciphers (TLSv1.2 and below). If custom is selected, a new field appears to enter custom ciphers.</td>
    </tr>
    <tr>
        <td>Allowed TLS Ciphers</td>
        <td>Cipher[:Cipher]..; Default: ""</td>
        <td>''Only appears if a Custom TLS Cipher is selected''<br>
A colon-delimited TLS cipher list (e.g. DES-CBC3-SHA:IDEA-CBC-MD5)</td>
    </tr>
    <tr>
        <td>Application Protocol</td>
        <td>Not specified | Connect | SMTP; Default: '''Not specified'''</td>
        <td>'''CLIENT SIDE ONLY'''
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.
If ''Connect'' or ''SMTP'' is selected, more customization fields appear.</td>
    </tr>
    <tr>
        <td>Protocol Authentication</td>
        <td>'''Connect:''' Basic | NTLM; Default: '''Basic'''
            '''SMTP:''' Plain | Login; Default: '''Plain'''</td>
        <td>'''CLIENT SIDE ONLY'''
''Options depend on the selected protocol''
Authentication type for the protocol negotiations.</td>
    </tr>
    <tr>
        <td>Protocol Domain</td>
        <td>domain (text); Default: ""</td>
        <td>'''CLIENT SIDE ONLY'''
       
''Only appears if a Connect protocol is selected''
           
Domain for the protocol negotiations.</td>
    </tr>
    <tr>
        <td>Protocol Host</td>
        <td>host:port; Default: ""</td>
        <td>'''CLIENT SIDE ONLY'''
       
''Only appears if a Connect protocol is selected''
           
Destination address for the protocol negotiations.
           
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 with the '''connect''' option.</td>
    </tr>
    <tr>
        <td>Protocol Username</td>
        <td>username (text); Default: ""</td>
        <td>'''CLIENT SIDE ONLY'''
       
''Only appears if a protocol is selected''
           
Username for the protocol negotiations.</td>
    </tr>
    <tr>
        <td>Protocol Password</td>
        <td>password (text); Default: ""</td>
        <td>'''CLIENT SIDE ONLY'''
       
''Only appears if a protocol is selected''
           
Password for the protocol negotiations.</td>
    </tr>
    <tr>
        <td>Verification</td>
        <td>None | Verify Chain | Verify Peer; Default: '''None'''</td>
        <td>Verification type. '''Verify Chain''' verifies connections against a Certificate Authority (CA) file, while '''Verify Peer''' verifies connections against a list of approved certificates.</td>
    </tr>
    <tr>
        <td>Verification file</td>
        <td>file; Default: ""</td>
        <td>''Only appears if a verification type is selected''
       
File which is used to verify peer(s) or a peer chain. A different type of file is expected depending on the verification type selected:
           
'''Verify Chain:''' Expects a CA (Certificate Authority) file.
'''Verify Peer:''' Expects a file with one (or more, concatenated) peer certificate(s).</td>
    </tr>
    <tr>
        <td>Certificate File</td>
        <td>file; Default: ""</td>
        <td>'''Mandatory for a server configuration. Optional for a client configuration'''
       
The parameter specifies the file containing certificates used by stunnel to authenticate itself against the remote client or server.
       
The file should contain the whole certificate chain starting from the actual server/client certificate, and ending with the self-signed root CA certificate.
           
Can be a certificate only, or both certificate and private key concatenated into a single file.</td>
    </tr>
    <tr>
        <td>Private Key</td>
        <td>file; Default: '''Certificate File'''</td>
        <td>''Can be skipped if the Certificate File is appended with the private key''
       
''Must be uploaded if the Certificate File does not contain the private key''
           
A private key, required to authenticate the certificate owner.</td>
    </tr>
</table>
After setting the parameters, click the '''Save''' button; otherwise, changes will not be saved. Some parameters will be shown in the configuration list table.
===Stunnel Global Configuration===
----
Default Stunnel global configuration:
[[Image:stunnel_default_global_config.png]]
Stunnel global configuration field explanation table:
<table class="nd-mantable">
    <tr>
        <th>Field Name</th>
        <th>Value</th>
        <th>Description</th>
    </tr>
    <tr>
        <td>Enabled</td>
        <td>yes | no; Default: '''no'''</td>
        <td>Enables/activates all the enabled Stunnel configurations.</td>
    </tr>
    <tr>
        <td>Debug Level</td>
        <td>integer [0..7]; Default: '''5'''</td>
        <td>Debugging 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: '''no'''</td>
        <td>Enable alternative configuration option (Config upload).
       
Be aware that when using alternative configuration, all configurations in '''Stunnel Configuration''' section will be skipped.</td>
    </tr>
    <tr>
        <td>Upload alternative config</td>
        <td>file; Default: ""</td>
        <td>''Only appears if the "Use alternative config" is enabled''<br>
       
Upload the alternative Stunnel configuration file.</td>
    </tr>
</table>
'''''IMPORTANT:'''''
The router can have multiple configurations set up and enabled at the same time. Note that if at least one configuration is not set correctly, '''none of them will be enabled''', despite the "Enabled" flag being marked.
Also, you must mark the global "Enabled" flag to actually enable all the individually marked configurations.
==See also==
* Configuration examples for RUTxxx VPN services:
** [[OpenVPN configuration examples]]
** [[IPsec configuration examples]]
** [[GRE Tunnel configuration examples]]
** [[PPTP configuration examples]]
** [[L2TP configuration examples]]
** [[DMVPN configuration]]
* Configuration examples for third party VPN services
** [[expressvpn.com VPN configuration|expressvpn.com]]
** [[vpngate.net VPN configuration|vpngate.net]]
** [[Vpnbook.com VPN configuration|vpnbook.com]]
** [[hide.me VPN configuration|hide.me]]
* Other related examples:
** [[How to generate TLS certificates (Windows)?]]
** [[L2TP over IPsec]]
** [[OpenVPN traffic split]]
** [[OpenVPN client on Windows]]
Retrieved from "https://wiki.teltonika-networks.com/view/Special:MobileDiff/38824...82249"