Cloud Connector/en

Request configuration

You have the option of ordering the Cloud Connector for different connection types:

• Inline configuration

• In this variant, the cloud connector is installed in the network as a normal device with a network card (LAN2).
• In the Cloud Center, please select the following connection type:
  

Additional device

• Gateway configuration

• In this variant, the Cloud Connector acts as the primary router. Two network cards are used, one is connected to the Internet, the other to your internal network.
• In the Cloud Center you have the following options, depending on your requirements:
  

Primary Router - DHCP

Primary Router - VDSL

Primary Router - ADSL (PPPOE)

Primary router - static IP -

Subsequent configuration adjustment

In certain situations it may be necessary for us to recreate or adjust your Cloud Connector's configuration file. In this case, your support colleagues will refer you to the terra CLOUD_CC Konfig change form. This must be filled out by you and sent to us at support@terracloud.de.

• Please enter your data in the first part of the PDF.

• In the next part, the data of the end customer who will use the Cloud Connector is required.

• You will then be provided with information about the license you have booked for your Cloud Connector.

• The next part is about the network connection LAN1 and the connection type you want for your Cloud Connector.

The first field is about the connection type Additional device. Accordingly, the first network port is not required and you will only be asked for the gateway address of your network.

The next part is about the Gateway connection type. Accordingly, the exact connection type must be selected for the first network card.

• Finally, an IP address for your internal network is required for the LAN2 network card.

• Please enter your name and current date at the bottom.

Commissioning

Note:
To activate the satellite for the first time and subsequently configure it, it must be connected to an unrestricted internet connection.
Furthermore, the satellite software does not support proxy servers.

1. Connect your computer via Ethernet to interface A1 (formerly called LAN2) of the supplied UTM firewall
   
2. Assign your computer the IP address 192.168.175.100
   
3. Open the URL https://192.168.175.1:11115 in your browser
   
4. Log in with the username 'admin' and the password 'insecure'
   
5. Accept the license agreements and Then cancel the configuration wizard.
   
6. First, import the license (.crt file) under the menu item Extras -> Register.
   
7. Under Configuration -> Configuration Management -> Import Configuration, select the .utm file and import it.
   
8. Load the configuration using the "heart" icon and set it as the default configuration using the "star" icon.
   
9. You can then restart the firewall. The button for this is located at the very bottom of the menu bar.
   
10. Now assign your computer an IP address from your desired internal network and connect to the firewall's IP address, which you specified in the form, using your browser.
    
11. Under Authentication -> Users, you can change the administrator password.
    

Once the configuration has been imported, the administrator password is: Terra001

Please note that a corresponding route to the data center must be configured in the site's central gateway if you are using the Cloud Connector as an additional device.

Troubleshooting

No connection to CC

• You cannot connect to the CloudConnector after importing the configuration:
  

• Cause:
  

You have not changed your local IP address from 192.168.175.XX to an IP address within the new internal network.

• Solution:
  

Manually adjust the IP address in Windows.

• Cause:
  

The new internal network is not registered as an admin network in the CloudConnector.

• Solution:
  

Connect a keyboard and monitor directly to the CloudConnector and register the network as an admin via the console.

• Login: admin and Terra001 (or insecure, but then the configuration file appears not to have been imported correctly).
  
• Run "interface address get" to determine which network is on A1 (formerly called eth1). (Example: IP=192.168.144.1/24 ==> Network=192.168.144.0/24)
• Run "manager get" and check if the A1 network (formerly called eth1) is listed there.
• If not, add the network using "manager new NETZ".
• Run "system update rule" and "system config save".

Site2Site connection is not established

• The CC does not establish a connection
  

• Cause:
  

The CC has no internet connection

• Solution:
  

Under "Network ==> Network Tool" ping 8.8.8.8 ==> if this fails, the CC seems to have no internet connection

• Cause:

The SSL-VPN service is not started

• Solution:

Restart or start the SSL-VPN service under "Applications ==> Application Status"

No communication through the tunnel

• VPN is set up but the clients cannot communicate through the tunnel
  

• Cause:
  

If the CC is the primary device in the network, everything should be fine as far as the clients can ping the CC.

If the CC is in the network as a secondary device, there are two ways to set the routes:

• Solution:
  

1. The local route gets a central route that routes the internal network of the cloud FW towards the CC

2. Each client receives a local route for the Internet network of the cloud FW in the direction of the CC

• Cause:
  

You did not specify a network or an incorrect network when booking

• Solution:
  

Pass on to the support team support@terracloud.de or (-If you have booked several Cloud Connectors in one package, it may be that not all client profiles match the server profile were assigned.

• all profiles that can be seen under "openvpn remote get" should also be visible in the "remote" column when calling "openvpn get" in the line of the server with the name "ssl-s2s".