The goal is to enable RDP access to the workstations in the LAN (192.168.0).
The OpenVPN server runs on Domain Controller 192.168.0.1 - Windows Server with running NAT service.
The configuration files:
client
dev tun
proto udp
remote xxxsag.xxxx.net 1194
resolv-retry infinite
nobind
persist-key
persist-tun
ca ca.crt"
cert test.crt"
key test.key"
compress lz4
verb 3
local 192.168.0.1
port 1194
proto udp
dev tun
dh "path to dh"
ca "ca.crt"
cert "server.crt"
key "server.key"
;
server 10.16.14.0 255.255.255.0
ifconfig-pool-persist "C:\\Program Files\\OpenVPN\\ipp.txt"
client-config-dir "C:\\Program Files\\OpenVPN\\ccd"
push "route 192.168.0.0 255.255.255.0"
push "dhcp-option DNS 192.168.0.1"
push "dhcp-option DOMAIN domainname.local"
keepalive 10 120
compress lz4
persist-key
persist-tun
remote-cert-tls client
status "openvpn-status.log"
log-append "openvpn.log"
verb 3
The result:
The VPN connection is established. The server (both 192.168.0.1 and 10.16.14.1 addresses) is accessible. But not the work stations. They are unpingable.
a remarkable row from the server log:
Thu Mar 19 09:49:48 2020 client/46.114.1.37:34205 SENT CONTROL [client]: 'PUSH_REPLY,route 192.168.0.0 255.255.255.0,dhcp-option DNS 192.168.0.1,dhcp-option DOMAIN domainname.local,route 10.16.14.1,topology net30,ping 10,ping-restart 120,ifconfig 10.16.14.10 10.16.14.9,peer-id 0,cipher AES-256-GCM' (status=1)
where I can not understand the part with
ifconfig 10.16.14.10 10.16.14.9. Because the 10.16.14.9 address is unpingable!
Where does it come from? Which part of the config does produce it?
Noteworthy routing table entries on client:
Internet:
Destination Gateway Flags Netif Expire
default 172.20.10.1 UGSc en4
10.16.14.1/32 10.16.14.9 UGSc utun4
10.16.14.9 10.16.14.10 UH utun4
192.168.0 10.16.14.9 UGSc utun4
It seems to me the routing table looks a bit strange (particularly the 10.16.14.9 as a destination and as a gateway)
Any ideas?
