--- title: "Double Netmapping – VPN For Connections To Devices With Identical Addresses - icom Connectivity Suite - VPN" slug: "double-netmapping-in-the-icom-connectivity-suite-vpn-for-connections-to-devices-with-identical-addresses-en" updated: 2024-11-27T14:03:05Z published: 2024-11-27T14:03:05Z canonical: "docs.insys-icom.com/double-netmapping-in-the-icom-connectivity-suite-vpn-for-connections-to-devices-with-identical-addresses-en" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.insys-icom.com/llms.txt > Use this file to discover all available pages before exploring further. # Double Netmapping – VPN For Connections To Devices With Identical Addresses - icom Connectivity Suite - VPN The **icom Connectivity Suite - VPN** is a service of INSYS icom for the simple and secure network connection of locations, plants, control centers and mobile devices via a Virtual Private Network (VPN). Netmapping enables devices in the local network behind an INSYS router to keep their IP address. These devices can then be addressed with the virtual IP address via the **icom Connectivity Suite – VPN**. ## Situation The application used to address the units via the **icom Connectivity Suite - VPN** does not permit a connection via the virtual IP address (netmapping address). ## Solution If it is not possible to address the identically configured devices in the different remote networks individually using the netmapping address, the selection of the device to be addressed can be made via individual VPN connections, which in turn use netmapping to redirect the data traffic to the original address of the device to be addressed to the virtual IP address. This can be referred to as **double netmapping**. ![cg ics double netmapping](https://docs.insys-icom.de/assets/cg_ics_double_netmapping.png) To do this, the OpenVPN configuration files for each VPN connection must be modified as follows. It is assumed that you - have already registered an account for the **icom Connectivity Suite - VPN**, as described in this [Configuration Guide](/kb/docs/en/registration-with-the-icom-connectivity-suite-en), - have added the router to the **icom Connectivity Suite - VPN** as described in this [Configuration Guide](/kb/docs/en/adding-an-insys-router-with-icom-os-to-the-icom-connectivity-suite-vpn-en), and - have configured the router to connect to the **icom Connectivity Suite - VPN** and for **netmapping** as described in this [Configuration Guide](/kb/docs/en/configuring-an-insys-router-with-icom-os-for-a-connection-to-the-icom-connectivity-suite-vpn-en), and - have added the PC to the **icom Connectivity Suite - VPN** as described in this [Configuration Guide](/kb/docs/en/configuring-a-windows-pc-for-a-connection-to-the-icom-connectivity-suite-vpn-en), and - have installed the OpenVPN software on your PC as described in this [Configuration Guide](/kb/docs/en/configuring-a-windows-pc-for-a-connection-to-the-icom-connectivity-suite-vpn-en) in the *Installing the OpenVPN software* section. ### Downloading the configuration file The **icom Connectivity Suite – VPN** generates a configuration file for establishing the OpenVPN connection. 1. Open the portal of the **icom Connectivity Suite**: - [https://connectivity.insys-icom.de](https://connectivity.insys-icom.de) (or the link you’ve received from your distribution partner) - Enter your credentials, select your preferred language under *Sprache* or *Language* and click on *Log in*. 2. Select on the *Devices* page in the device list the device that is supposed to connect to the **icom Connectivity Suite - VPN** and click on the device details page on DOWNLOAD CONFIGURATION. 3. Save the configuration file on your computer. 4. Move the OpenVPN configuration file from the Download directory to the configuration directory of the OpenVPN installation. The standard configuration directory for this is **C:\Program Files\OpenVPN\config**. ### Modifying the configuration files The configuration files for each VPN connection must be modified for the double netmapping of the connection to the **icom Connectivity Suite - VPN**. This requires a DNAT rule that forwards all requests to the network behind the router to the netmapping address and a static route that routes all requests to the network behind the router through the VPN tunnel. 1. Open the configuration directory in a file manager. 2. Make a copy of the OpenVPN configuration file **Control_PC.ovpn** and rename it accordingly, e. B. **Control_PC_101.ovpn** following the different netmapping addresses in this example. 3. Open the new OpenVPN configuration file in a text editor and insert the following lines: `client-nat dnat 192.168.1.0 255.255.255.0 192.168.101.0` `route 192.168.1.0 255.255.255.0` ![](https://cdn.document360.io/c690fe99-a3eb-474c-a449-c2c75e5df119/Images/Documentation/image(11).png) 4. Save the modified OpenVPN configuration file. 5. Modify the OpenVPN configuration files for the other VPN connections accordingly. Be sure to adjust the addresses in the commands accordingly and name the files accordingly. ### Establishing the OpenVPN connection When the OpenVPN package is installed, it is possible to establish a connection to each OpenVPN network, for which a configuration file is present, from a PC. 1. Start the **OpenVPN GUI** via the *Start menu* → *OpenVPN* → *Open-VPN GUI* or by clicking on the desktop icon. 2. Right-click the symbol of the OpenVPN GUI in the task bar and select *Control_PC_101* → *Connect* (the OpenVPN connection will be named by the file name of the configuration file). The **OpenVPN GUI** will establish a connection to the **icom Connectivity Suite – VPN** now and the desired device can be addressed via **double netmapping** using the original address. ## Troubleshooting - You can verify a successful connection when the *Status* of the device in the device list in the *Devices* menu of the **icom Connectivity Suite - VPN** changes to *Online*. Please note that this may take up to a few minutes. - If the connection to the **icom Connectivity Suite – VPN** has been established successfully, the symbol of the Open-VPN GUI will be shown green. If the symbol remains yellow, the OpenVPN client tries to reach the server, but the connection cannot be established. - A connection log can be displayed using the menu item *View Log* displayed If the symbol remains yellow and the log stops with the line **UDP link remote**, a possible reason is that an external firewall blocks the VPN connection. The port for the VPN connection is displayed in this log entry at the end after the colon. This port (with the UDP protocol) must be opened by the administrator. A VPN is a communications environment in which access is controlled to permit peer connections only within a defined community of interest. It is constructed though some form of partitioning of a common underlying communications medium, where this underlying communications medium provides services to the network on a non-exclusive basis