Networking Cloud Virtualizations

Topic

This article discusses creating, accessing, and viewing networks for cloud virtualization in the new Recovery Launchpad.

Environment

  • Datto Partner Portal
  • New Recovery Launchpad

Description

The Datto Partner Portal lets you create a virtual private network (VPN) for use in a disaster recovery. You do not need to have a cloud virtualization mounted to set up a VPN. These two steps can be done separately and networks can be setup ahead of time if you prefer. For instructions on creating a cloud virtualization to access via your VPN, see Partner Portal: Performing a cloud virtualization. To create a VPN, first access the new Recovery Launchpad environment for your device.

Method 1

  1. In the Datto Partner Portal, click the Status tab, then select BCDR Status from the drop-down menu.



  1. In the section for the target device, click the ellipsis icon on the far right-hand side of the screen, then click Recovery Launchpad from the drop-down menu.



Method 2

  1. Alternatively, from the BCDR Status page, click the name of the Datto device.



  1. On the top right of the Device Details page, click Recovery Launchpad

Creating a VPN

  1. In the Virtualizations card on the Recovery page, click MANAGE NETWORKS.
    fig3.png

  2. On the Active Networks card, click ADD NEW NETWORK.
    fig4.png

  3. In the Add New Network dialog window, enter the Network Name and Network Address (IP scheme), and the Subnet Mask you want to use. Gateway IP is required and will be auto-populated based on the Network Address you entered, but should be overwritten to reflect your networking scheme. (0.0.0.0 is not permitted for the Gateway IP.

  4. Under Network Options, Internet Connection is checked by default. Uncheck this box if you don't need an internet connection.

  5. Click the Enable DHCP button if you require DHCP assignment of IP addresses to be provided by your cloud network.

    • Enter DHCP Pool Start and DHCP End IP addresses if you enabled DHCP.

    fig6.png

Restricted IP ranges

Your network scheme must be RFC-1918 compliant. Also, the following IP schemes are restricted and cannot be used:

  • 10.30.130.0/24
  • 10.40.40.0/24
  • 10.50.15.0/24
  • 10.82.16.0/24
  • 10.90.15.0/24
  • 10.110.15.0/24
  • 10.160.15.0/24
  • 10.162.15.0/24
  • 10.210.15.0/24
  • 192.168.122.0/24

Site to Site Configuration (optional)

The Site-to-Site Configuration allows you to establish secure connections over the Internet between your locations and the Datto Cloud via IPsec, so that your users can easily connect to cloud resources from remote offices.

IPsec tunnels can be added to Datto Cloud networks only AFTER you configure the tunnel on your router or firewall FIRST.

Warnings

  • Configuring Site-to-Site networks into the Datto Cloud requires some working knowledge of IPsec technology and will vary depending on your equipment at your location(s).
  • Incorrect configuration may result in unwanted network access.
  • Datto support can only provide minimal assistance in configuring these tunnels, due to the wide array of available networking equipment and configurations.
  • Site-to-Site configurations are not persisted for reuse outside of a network.
  • The Site to Site VPN feature is not available on SIRIS Private service plans

About VPN Tunnels

IPsec VPN negotiations happen in two distinct phases between the devices at each end of the tunnel. These negotiations are required to build the VPN tunnel, and include a series of messages about encryption and authentication in an attempt to agree on the required VPN parameters. In Phase 1, the devices set up a secure encrypted channel so that they can negotiate Phase 2, where they agree on an additional set of parameters that define what traffic can go through the VPN and how that traffic should be secured. The Phase 1 and Phase 2 configurations must match for the devices on either end of the tunnel.

Creating a Site-to-Site IPsec VPN Tunnels

  1. To use the site-to-site option, check the box labeled Enable Site-to-site VPN Connection. You will be taken to the Add Site-to-Site VPN Configuration view, where you will enter the settings for each IPsec tunnel.

  2. You'll need to specify the following parameters for each tunnel you configure:

    • Site-to-Site VPN Name: A name you define to identify this connection in the portal display. Up to 25 characters.
    • IPsec Mode (drop-down menu): Select the IKE Mode the client will use to connect (IKEv1 or IKEv2).
    • Pre-shared Key: Create a pre-shared key that will be used to communicate securely with the client. Any client you connect will need to communicate by using this key.
    • Local IKE ID: Based on your local router, enter the local IKE ID for the on-premises device.
    • On-Premises IP: The IPV4 address for your on-premises router (e.g. 8.8.8.8).
    • On-Premises Subnets: On-Premises Subnets: A comma-separated set of CIDR subnets that will access the connection. (the same restricted IP ranges as above apply)

  3. Ensure any identifier type selection on your firewall most closely matches the format of the value you have configured in the portal.

  4. The remaining fields are pre-selected with the recommended default settings. If needed, you have the option to change these IPsec policies and parameters for both Phase 1 and Phase 2. See the Phase 1 and Phase 2 parameters section below for an explanation of the settings. Otherwise, proceed to step 5.

  5. After you have reviewed your new network settings, click the CREATE NETWORK button at the bottom right of the dialog window.

  6. You'll now see your network listed under Active Networks on the Manage Networks page. If you wish to create additional IPsec tunnels to the same cloud network, select New Site-to-Site VPN. This will take you to the create IPsec screen explained above.

  7. If you want to add Site-to-Site VPN to an existing network, this can be done from the new Recovery Launchpad. Select Manage Networks.

  8. Choose a network from the list. In the Site to Site VPN Configuration panel, select New Site-to-Site VPN. This will take you to the create IPsec screen explained above.

Managing Your Site-to-Site IPsec Tunnels

You can view a summary and the status of existing tunnels from the Site-to-Site VPN Configuration View panel in the Network View.

Hovering over the options icon to access the following:

  • Reset Tunnel – resets the selected tunnel
  • Edit Tunnel – takes you to tunnel configuration view where you can adjust and save settings
  • Delete – removes the tunnel from the cloud network

You can also select Reset all tunnels to perform a network reset for all IPsec tunnels connected to the selected cloud network.

Additional Site-to-Site IPsec Tunnel information

Phase 1 and Phase 2 parameters (optional)

When creating a site to site VPN, these settings are set to their most common configuration by default. You may need to change these settings based on your particular router/firewall manufacturers' recommendations. If you need to change the settings, the following options are available:

  • Encryption Algorithm: Allows you to specify what encryption algorithm is used. The Triple Data Encryption Standard, AES-128, AES-192, and AES-256 are available.
  • Hash Algorithm: Allows you to specify what hash algorithm is used. SHA1, SHA256, SHA384, and SHA512 are available.
  • DH Group:Allows you to specify what Diffie-Hellman exchange (DH group) is used. The following groups and moduli are available: 

Regular Groups

  • Group 14: 2048 bit
  • Group 15: 3072 bit
  • Group 16: 4096 bit
  • Group 17: 6144 bit
  • Group 18: 8192 bit

     Prime Order with Prime Subgroups

    • Group 23: 224 bit
    • Group 24: 256 bit

     NIST Elliptic Curve Groups

    • Group 25: 192 bit
    • Group 19: 256 bit
    • Group 20: 384 bit
    • Group 21: 521 bit

     Brainpool Elliptic Curve Groups

    • Group 27: 224 bit
    • Group 28: 256 bit
    • Group 29: 384 bit
    • Group 30: 512 bit

  • Lifetime (seconds): Allows you to specify, in seconds, how often the IPsec tunnel is renegotiated. The default is 86,400 seconds.

  • Dead Peer Detection: Dead Peer Detection (DPD) is the method to detect the status of a peer in an IPsec connection. You can enter the time in seconds before the connection will be dropped due to an unresponsive peer.

NOTE  Check your specific router/firewall documentation before changing the default settings.

NOTE  In preparation for FIPS compliance, all non-FIPS approved algorithms and ciphers are being removed from Recovery Launchpad. If you have problems connecting to cloud restores, you should first verify that you are attempting to connect with FIPs compliant algorithms for encryption, hashing, and signing.

Additional Resources