patjuh112
Hi all and thanks for reading that was comes below 😉
I've used OpenVPN about 10 years ago on a linux based setup and was still charmed by it, due to the current company not having physical routers able to setup a proper VPN i instantly went back to OpenVPN but this time on a windows setup. The problem i am facing must be in my setup since i tested this between multiple situations and servers/clients and it always results in the same : Client can connect to server but server can not (e.g. ping) get back to the client. Additionally i want the full subnets to be reachable but i havent even gotten to that part yet due to this problem.
Any help is appreciated, the client is running Win7 x86 ult. and the server is running 2008 R2 x64 standard. Openvpn version is latest.
Network information :
Site 1 (server site)
Network : 192.168.1.0/24
VPN Server : 192.168.1.13
Server config file contents :
//-------------------start of config file
local 192.168.1.13
port 1194
proto udp
dev tun
ca ca.crt
cert server.crt
key server.key
dh dh1024.pem
server 10.8.0.0 255.255.255.0
ifconfig-pool-persist ipp.txt
push "route 192.168.1.0 255.255.255.0"
client-config-dir ccd
route 192.168.1.0 255.255.255.0
client-to-client
keepalive 10 120
comp-lzo
persist-key
persist-tun
status openvpn-status.log
verb 3
//-------------------end of config file
Server side uses extra client directive ccd dir, file contents :
//-------------------Start of client route lines (server side)
iroute 192.168.0.0 255.255.255.0
//-------------------End of client route lines (server side)
Site 2 (client site)
Network : 192.168.0.0/24
VPN client IP : 192.168.0.196
Client config file contents :
//-------------------start of config file
client
dev tun
proto udp
remote 83.81.167.232 1194
persist-key
persist-tun
ca ca.crt
cert client1.crt
key client1.key
ns-cert-type server
comp-lzo
verb 3
//-------------------End of config file
maikcat
hi there,
to your server config replace this:
route 192.168.1.0 255.255.255.0
with this:
route 192.168.0.0 255.255.255.0
route directive is used for clients subnet not yours..
the rest look ok..
for your client problem,
did you configured their firewall to accept traffic from the tunnel?
Michael.
patjuh112
Thanks for that first part, will test this out in 2 hours when production hours are over. Regarding the other servers behind the vpn server, they have no firewall active at all at this moment and the same goes on the stuff behind the client's LAN (dont really need to reach that).
What puzzles me is how to add this route on the other servers, obviously they are unaware of its network now so i could do something like : route add 192.168.1.0 mask 255.255.255.0 192.168.1.3 (LAN ip from vpn server) but i doubt that is sufficient. Also i read somewhere that i had to enable IP forwarding which i did through the registry, is it needed to have rras turned on at all ?
Apols for the double post btw, posted this yesterday and noticed the forum wasnt loading this morning so thought the post was lost.
