On Thu, 27 May 2021 12:51:53 +0200, Jan Just Keijser <janj...@nikhef.nl> wrote:
>> I thought it to be a built-in limitation of OpenVPN but this response >> suggests >> otherwise. >> Please if you can, expand on what is possible and how to accomplish this on >> Windows (client side). >> My target servers operate on a number of different remote networks with >> varying >> address pools. >> >> Or is the problem that *all* of the servers operate with the *same* tunnel IP >> range (the default 10.8.0.x)? >> That would explain the problem, I guess... >OpenVPN for Windows definitely supports multiple tunnels, but you need >multiple tun/wintun adapters for this. These can be installed using the >Start menu items. > So these adapters are not created on demand then? In any case I suspect that my various OpenVPN servers need an overhaul since they all use basically the same server.conf file especially regarding the tunnel address range. Always 10.8.0.x or 10.8.1.x (if there are more than one service). Since the client will get such an address from all servers I guess the routing on my Windows machine will be screwed up... The tunnel on each of my servers need to use *different* networks if they are to be concurrent on a client, I believe. Did not think about that when I set them up. I'm using several RaspberryPi OpenVPN servers to reach my family's home networks.... -- Bo Berglund Developer in Sweden _______________________________________________ Openvpn-users mailing list Openvpn-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openvpn-users
