August-24th-2021, 04:15 PM
(This post was last modified: August-25th-2021, 06:56 AM by Armin@netPI.)
Well,
1.) No changes on the Internet router was necessary during my test session with my personal OpenVPN server at home. Here on the Hilscher's Headquarter office network I have anyway no chance to make any changes on this HQ internet router, since I am not an IT admin. So I was using the standard Internet connection of the office network they are providing to my notebook, PC and also to my netFIELD Connect gateway of course during this test.
2.) I have seen this remote proxy software once when our netFIELD software product manager Frank Bauer introduced it. But now Frank Bauer has left Hilscher 2 month ago, and I don't know where he put this software to. But there is one important thing ... the netFIELD remote proxy function will only work if you have a running subscription with your netFIELD gateway. If you or your customer don't have it then you can't use it. And remember getting a subsciption for a single device is not rentable, he always has to pay an initial setup cost in any case per month plus the device usage. Getting subscriptions and remote management option makes only sense if you have multiple devices running and want to control them from remote. Anyway the netfield cloud services and functions run independent from the openvpn CLI command introduced with netFIELD OS 2.2. openvpn is, was and stays a free tool from the community.
For your tests you need of course a working VPN server somewhere on the Internet the gateway can connect to. And also you need a proper *.ovpn configuration file.
To connect this server it has to have a static IP address forever as one option since the *.ovpn file contains its IP address ... but static IP address is quite unusal to have since its IP address usually changes daily due to forced disconnection by the Internet provider ... or your server is getting a static domain name instead like my server at home using a DNS provide. So instead of a static IP address in the *.ovpn file the static domain name in this file is telling later the openvpn CLI where to connect to.
If you have a servier and proper *.ovpn file then you should be able to connect netFIELD Connect gateway running netFIELD OS 2.2 with charm in just a minute without any problems.
1.) No changes on the Internet router was necessary during my test session with my personal OpenVPN server at home. Here on the Hilscher's Headquarter office network I have anyway no chance to make any changes on this HQ internet router, since I am not an IT admin. So I was using the standard Internet connection of the office network they are providing to my notebook, PC and also to my netFIELD Connect gateway of course during this test.
2.) I have seen this remote proxy software once when our netFIELD software product manager Frank Bauer introduced it. But now Frank Bauer has left Hilscher 2 month ago, and I don't know where he put this software to. But there is one important thing ... the netFIELD remote proxy function will only work if you have a running subscription with your netFIELD gateway. If you or your customer don't have it then you can't use it. And remember getting a subsciption for a single device is not rentable, he always has to pay an initial setup cost in any case per month plus the device usage. Getting subscriptions and remote management option makes only sense if you have multiple devices running and want to control them from remote. Anyway the netfield cloud services and functions run independent from the openvpn CLI command introduced with netFIELD OS 2.2. openvpn is, was and stays a free tool from the community.
For your tests you need of course a working VPN server somewhere on the Internet the gateway can connect to. And also you need a proper *.ovpn configuration file.
To connect this server it has to have a static IP address forever as one option since the *.ovpn file contains its IP address ... but static IP address is quite unusal to have since its IP address usually changes daily due to forced disconnection by the Internet provider ... or your server is getting a static domain name instead like my server at home using a DNS provide. So instead of a static IP address in the *.ovpn file the static domain name in this file is telling later the openvpn CLI where to connect to.
If you have a servier and proper *.ovpn file then you should be able to connect netFIELD Connect gateway running netFIELD OS 2.2 with charm in just a minute without any problems.
„You never fail until you stop trying.“, Albert Einstein (1879 - 1955)
