August-24th-2021, 01:20 PM
(This post was last modified: August-25th-2021, 07:53 AM by Armin@netPI.)
Hello Madhumati,
1.) No the netFIELD OnPremise can be ordered without any subscription. You can operate totally independent of netfield cloud services. So you can manage it locally using a standard Linux terminal console over SSH or via the web UI pages. Using the option netfield and cloud management can be ordered separately and is an addtional function. Some customers do not allow Internet connection in their plants anyway, so for them it is the ideal solution to do everything locally only. The two gateways netFIELD Connect and netFIELD OnPremise both have two Docker engines preinstalled. One Docker instance we call "local" and can be managed via local terminal console. This one is active in both devices by default and you are free to use it with any Docker container you want (OnPremise is Intel CPU based so it needs X86 compatible containers so "hilschernetpi/netpi-nodered" container for example will never run on it, Connect is ARM CPU based so it needs ARM compatible containers ). The second Docker instance is deactivated and "sleeping" until you book a netfield subscription additonally. Then this Docker instance can be controlled from remote over netfield cloud/internet platform. But this is just an option. If you don't like it to use it keeps "sleeping".
2.) No there is no other software in charge for an OpenVPN connection. In new netFIELD OS 2.2 the command line (CLI) program openvpn comes preinstalled right away for a direct use. You can reach this command like all other Linux commands using a terminal console over an SSH connection or alternatively over the device web-UI site (embedded terminal).
3.) OpenVPN is a community developed service. We have just embedded it as command into the latest netFIELD OS 2.2 version as it is. The OpenVPN project and the CLI command openvpn is well documented by the OpenVPN organization. It does not make sense to document this CLI command and its parametes once again on any Hilscher web site. Here is for example one of the official Internet pages explaining the command line: https://openvpn.net/vpn-server-resources...ith-linux/
Today I tried to establish a VPN connection to my OpenVPN server running at home via Hilscher gateways using netFIELD OS 2.2. It worked immediately and I was able to ping all my home network devices via the netFIELD Connect or netFIELD OnPremise gateway after I have established the VPN connection. The command line I was calling was quite simple: openvpn --config arminhomserver.ovpn.
The *.ovpn file is a common configuration file I created based on the instructions on the OpenVPN organizations web site or there are also online web sites like this one https://ovpnconfig.com.br/ you can feed with data/credentials coming from my OpenVPN server to generate them. It contains parameters like the internet domain name of my server (I am using a DNS provideron my server for giving me a constant Internet Domain name), used ports for the connections and the most important point the certificates (issued for my Internet Domain name). Of course there are a lot of other parameters that can be added to the config file which I don't know and just the basic ones. But in the end with such a very simple setup I was able to establish an OpenVPN connection to my homeserver in 5 minutes.
Thx
Armin
1.) No the netFIELD OnPremise can be ordered without any subscription. You can operate totally independent of netfield cloud services. So you can manage it locally using a standard Linux terminal console over SSH or via the web UI pages. Using the option netfield and cloud management can be ordered separately and is an addtional function. Some customers do not allow Internet connection in their plants anyway, so for them it is the ideal solution to do everything locally only. The two gateways netFIELD Connect and netFIELD OnPremise both have two Docker engines preinstalled. One Docker instance we call "local" and can be managed via local terminal console. This one is active in both devices by default and you are free to use it with any Docker container you want (OnPremise is Intel CPU based so it needs X86 compatible containers so "hilschernetpi/netpi-nodered" container for example will never run on it, Connect is ARM CPU based so it needs ARM compatible containers ). The second Docker instance is deactivated and "sleeping" until you book a netfield subscription additonally. Then this Docker instance can be controlled from remote over netfield cloud/internet platform. But this is just an option. If you don't like it to use it keeps "sleeping".
2.) No there is no other software in charge for an OpenVPN connection. In new netFIELD OS 2.2 the command line (CLI) program openvpn comes preinstalled right away for a direct use. You can reach this command like all other Linux commands using a terminal console over an SSH connection or alternatively over the device web-UI site (embedded terminal).
3.) OpenVPN is a community developed service. We have just embedded it as command into the latest netFIELD OS 2.2 version as it is. The OpenVPN project and the CLI command openvpn is well documented by the OpenVPN organization. It does not make sense to document this CLI command and its parametes once again on any Hilscher web site. Here is for example one of the official Internet pages explaining the command line: https://openvpn.net/vpn-server-resources...ith-linux/
Today I tried to establish a VPN connection to my OpenVPN server running at home via Hilscher gateways using netFIELD OS 2.2. It worked immediately and I was able to ping all my home network devices via the netFIELD Connect or netFIELD OnPremise gateway after I have established the VPN connection. The command line I was calling was quite simple: openvpn --config arminhomserver.ovpn.
The *.ovpn file is a common configuration file I created based on the instructions on the OpenVPN organizations web site or there are also online web sites like this one https://ovpnconfig.com.br/ you can feed with data/credentials coming from my OpenVPN server to generate them. It contains parameters like the internet domain name of my server (I am using a DNS provideron my server for giving me a constant Internet Domain name), used ports for the connections and the most important point the certificates (issued for my Internet Domain name). Of course there are a lot of other parameters that can be added to the config file which I don't know and just the basic ones. But in the end with such a very simple setup I was able to establish an OpenVPN connection to my homeserver in 5 minutes.
Thx
Armin
„You never fail until you stop trying.“, Albert Einstein (1879 - 1955)
