I would like to use OpenVPN to enable connectivity as follows: - A TCPIP server is behind a NAT ISP (no inbound address available) - A client running on another network connected to the Internet - An OpenVPN server runs on a 3rd location and is externally available - The server connects to the OpenVPN server on startup and remains connected at all times. - On connection the server obtains a fixed tunnel address - The client also connects to the same OpenVPN server but gets a dynamic tunnel address - Now knowing the servers tunnel address the client should be able to connect to the server using that address, right? - Following this normal client/server communication is available, right?
What I need to use is the VPN tunnel itself for communication between the client and server and none of them needs to use the OpenVPN server to reach the network the OpenVPN server is on or via VPN to the Internet. So I would like to set up OpenVPN without routing to the VPN server's network... Question: --------- How should I configure the OpenVPN server to enable this way of operation where the VPN connection is really a way to make otherwise hidden server(s) available for connection? The server devices in this case are RaspberryPi controllers running on remote locations for data monitoring and the clients are dedicated Configuration/Control programs running on Windows or Linux desktops. The server connectivity is limited by using mobile broadband Internet (on solar/battery power) so there is only outgoing Internet connections available on the RPi units. -- Bo Berglund Developer in Sweden _______________________________________________ Openvpn-users mailing list Openvpn-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openvpn-users
