I have an OpenVPN setup consisting of separate machines on the Internet: one machine runs single OpenVPN server with private address 10.10.0.1 and the other machines run OpenVPN clients with private adresses from the range 10.10.0.0/16. Tun devices are used everywhere (with appropriate route and iroute commands). Everything works, every host is accessible as desired.
However, for the reasons of simplicity of use, I would like to have one OpenVPN client running on the first machine as well. This "local client" would have its own unique IP address, connect to the same OpenVPN server daemon as the other remote clients do and be accessible from within VPN just as the other, "remote" clients on the physically separate machines. In the end, one could login to the first machine through its OpenVPN client IP adress, thus avoiding connecting to the server IP address 10.10.0.1.
Is it possible to "virtualize the OpenVPN client" in this way? I tried the most direct way but when I execute openvpn client.conf on the first machine, although it keeps running and connects to the server daemon, it is only accessible locally on the first machine. Unlike the other OpenVPN clients, it does not respond to ping requests from the other machines in the VPN.
I think if I placed the local client into its separate virtual machine it is certainly possible, but I would like to avoid that and simply run two daemons side-by-side.