Score:0

OpenVpn - connect vpn clients to server subnet / server intranet

nc flag

We have installed OpenVpn community editon (v2.5.8) in windows server 2019, having multiple VMs running in Intranet (10.0.0.0/24). I want my vpn clients (10.8.0.0/24) to communicate with VMs and VMs can communicate with vpn clients, as described in below image :

Network Diagram

server config as :

dev tun
topology subnet
server 10.8.0.0 255.255.255.0
ifconfig-pool-persist ipp.txt
client-to-client
push "route 10.0.0.0 255.255.255.0"
client-config-dir ccd

We are using default client config.

Inside CCD (client1,client2 files) as :

client1 => ifconfig-push 10.8.0.11 255.255.255.0
client2 => ifconfig-push 10.8.0.12 255.255.255.0

We have enabled Packet Forwarding as [Enable Packet Forwarding][2], Vpn is working fine and vpn clients can communicate with other Vpn Clients.

We have enabled Windows Server NAT on Internal Network(10.0.0.0/24) for OpenVpnTap, So our VMs(VM1,VM2..) can easily communicate with VPN Clients. VMs can easily access/ping VPN Clients, But

Vpn clients can not communicate with Server Intranet VMs (VM1,VM2,VM3)

OpenVpn is not in Bridge and all vpn clients are on Windows 8 and above.

How can VPN Clients communicate with VM1,VM2 and VM3 ?

Do we need some additional configuration in VM1,VM2,VM3 or In VPN clients ?

I sit in a Tesla and translated this thread with Ai:

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.