OpenVPN Support Forum

Posted: **Mon May 31, 2021 2:33 pm**

I connected successfully using OpenVPN 2.5.2.
I used a configuration like this:

port 1194
proto tcp
dev tap
ca certificates/ca_stack.crt
cert server.crt
dh dh.pem
ifconfig-pool-persist ipp.txt
server-bridge 192.168.88.103 255.255.255.0 192.168.88.200 192.168.88.254
server-bridge
push "route 192.168.88.0 255.255.255.0"
keepalive 10 120
persist-key
persist-tun
status openvpn-status.log
verb 4
management 192.168.88.103 6001

The Windows client connects and sets the TAP IP 192.168.88.200 but I can't access the network 192.168.88.0/24.
When I do a "tracert -d 192.168.88.103", windows is not routing me through the assigned tap ip (192.168.88.200), instead, I exit using my default gateway. This looks like a Windows problem... but I was hoping someone here got the same problem.

Thank you

Posted: **Mon May 31, 2021 3:59 pm**

victorqedu wrote: ↑
Mon May 31, 2021 2:33 pm
This looks like a Windows problem

Nope .. it's a You problem.

A Bridge Too Far ...

Posted: **Mon May 31, 2021 4:22 pm**

If you are referring to the secondary "server-bridge" you should know that I tried to remove it and the result is the same.
I actually tried first without the secondary "server-bridge", I just placed it later hoping to fix the problem, but I don't really understand what is going on.

Posted: **Mon May 31, 2021 5:41 pm**

Ok, I created the bridge and I can ping the VPN network, I guess it was a bridge too short.

OpenVPN Support Forum

Openvpn - network not accesible

Openvpn - network not accesible

Re: Openvpn - network not accesible

Re: Openvpn - network not accesible

Re: Openvpn - network not accesible