How to enable access to a VNC server via a web proxy

• 1 INSYS router, e. g. MOROS.neo-E.4G

• 1 suitable cellular antenna  

• 1 M2M SIM card in industrial quality

• 1 Ethernet cable

• 1 power supply unit or-power supply (12-24 V DC)

• 1 Configuration PC with browser (for initial setup, can also be the remote access PC)

• 1 Remote access PC with browser and PLC-specific software

1. If you do not already have an account for the icom Connectivity Suite, register on the portal. See this Configuration Guide.

2. Sign in to the portal.

3. Add the PC, from which you want to access the controller, to the VPN network. See this Configuration Guide.

   Please note!

   You do not have to set an accessible IP for the remote access PC, since access to the PC from the VPN network is not necessary.

4. Add the router, which you want to use to access the controller, to the VPN network. See this Configuration Guide.

   Please note!

   • If you assign a device code here, keep it in mind for the subsequent configuration of the router.

   • Enter as accessible IP the IP address, which the router should get in the network accessible from remote, in this case 192.168.22.1.

   • Check Netmapping.

   • Enter as Router/LAN IP the IP address, which the router should get in the local network, which also contains the controller, in this case 192.168.2.1.

   • Select under Device Configuration Type Assign nets to ports manually and assign the ports according to the desired configuration:

     • Continue to reserve port 1.1 as Configuration port.

     • Assign the ports 1.2 through 1.4 to the plant network.

   

To access the container on the router from outside the network, you must add a web proxy (endpoint) for this container in the icom Connectivity Suite.

To do this, follow the steps described here and use the following parameters:

You will need a PC with a free Ethernet socket. A DHCP client should be activated on the PC; otherwise you must set up a static IP address in the address range 192.168.1.0/24. The IP address 192.168.1.1 is already occupied by the router.

Use this Configuration Guide to set up a Windows PC for a connection to the icom Connectivity Suite - VPN. Proceed in the same way for a computer with a Linux operating system. It is important to download the OpenVPN configuration file generated by the icom Connectivity Suite - VPN and import this configuration file into the OpenVPN software. Instructions for iOS and Android are available here.

The router should be in default settings for this configuration!

Reset the router to default settings in case it has already been used.

1. Insert the SIM card into the router (for routers with two SIM card slots, make sure that you insert the SIM card into SIM1).

2. Install the router on the DIN rail (installation notes are available in the Installation and User Manual).

3. Connect the antenna (when using an antenna on routers with two antenna sockets, make sure that you connect the antenna to LTE1).

4. Connect the configuration PC to the router to socket ETH1 using an Ethernet cable.

5. Connect the power supply to terminals V+ (or VIN, positive) and V- (or GND, negative).

The uppermost LED PWR (Power) should light now and signal that the router is supplied with power.

1. Open a new browser window or tab - keep the browser window with the icom Connectivity Suite - VPN open.

2. Enter https://insys.icom into the address bar of the browser.

3. Click on the welcome screen on To Startup wizard.

   Please note!

   If the welcome screen is not displayed, you may also start the Startup wizard in the   Wizards → Startup wizard menu.

4. Click in step 1 - System time - on NEXT - this takes over the system time from the configuration PC and configures a regular update of the time.

5. Enter in step 2 - Authentication - a user name and a safe password for future access to the router and click on NEXT .

6. Select in step 3 - Internet connection - the interface you want to use to establish the connection, here LTE - SIM1, enter a PIN for the SIM cad if required, select the APN and click on NEXT .
   

7. Enable in step 4 - VPN connection - the Configure VPN switch, select as Type of VPN connection the icom Connectivity Suite, select Download configuration automatically and enter Customer name as well as Device code or Default code.
   
   If you did not specify a device code when registering the router, the default code will be used here. Customer name and default code can be found in the icom Connectivity Suite - VPN on the System → My VPN Hub page in the Account Information field.
   
   Click on NEXT .

8. Click in step 5 - LAN connection - on NEXT - the LAN connection will be configured automatically by the icom Connectivity Suite - VPN.

9. Step 6 - icom Router Management - allows to configure your router for the icom Router Management. For this purpose, the router must first be set up as described here.

10. Click on RUN WIZARD.

The Startup wizard is executed and displays the progress of the configurations it has made. The Ethernet interface of the router will be reconfigured.

The router should be indicated as Online in the device list in the portal of the icom Connectivity Suite - VPN (VPN > Devices menu) after a few minutes.

First, download the Alpine container from our container page.

Take care to download the correct version!

aarch64: for routers of the series MRX.neo and MOROS.neo

armv7: for routers of the series MRX, ECR and SCR

To install the Alpine container, follow the steps described in Installing a Linux container (LXC) and assign it the IP address 192.168.2.22.

The container will be started once the profile has been activated.

• Are remote access PC and router indicated as Online in the device list of the icom Connectivity Suite - VPN (VPN > Devices menu)?

• Does remote access to the router work via the address https://192.168.22.1?

• Is it possible to ping the controller in the local network of the router? To do this, go to the Administration → Debugging menu and enter for the Ping Tool the local address of the controller 192.168.2.22 as Parameter.

• Does local access to the controller work via the local address 192.168.2.22 from a PC in the local network of the controller?

• Open the Status → Dashboard page and check the necessary connections.