Connection established but can’t access remote network

[confusedShark]

I have remote Synology NAS that runs a OpenVPN Server. It's just a super basic config, that allows me to connect to the remote network.
Connection between my two NAS's works great via OpenVPN and in the past i was able to connect to the remote network via OpenVPN connect. Sadly this stopped working at some point. Am I missing something? OpenVPN connect shows that some kind of connection is established but i can't ping any remote IP. (Also tried on another computer, also with no luck)



Remote network: 192.168.1.0/24
Local network: 192.168.178.0/24
VPN IP: 10.8.0.1

A DynamicDNS service runs in the remote network and the connection is established via the DynDNS hostname. The UDP Port (1194) is open in the firewall and forwareded to the NAS.

Config on the NAS:


Config file:

Code: Select all

dev tun
tls-client

remote [DYNDNSHOST] 1194

redirect-gateway def1

dhcp-option DNS 192.168.1.1

pull
proto udp
script-security 2
compress lzo
reneg-sec 0
cipher AES-256-CBC
auth SHA512
auth-user-pass
<ca>
-----BEGIN CERTIFICATE-----
[CERT]
-----END CERTIFICATE-----

</ca>

I connect with username and password.

Thanks for your help!

[pgehle]

I have the same problem, but with the difference that my configuration worked two years. Since some weeks I couldn't my Windows Servers throug the Tunnel.

[confusedShark]

Same for me. I had this working on my old Windows 10 PC but only used it a few times a year so I can't say when it stopped working. Now on my new Windows 11 machine it won't work. I don't have the old PC anymore but the config is exactly the same. I checked it with another Win10 notebook and it also doesn't work there.

[Killer2600]

Can't say I've had the same problem but AES-256-CBC has been deprecated, AES-256-GCM is the current recommended/default cipher algorithm.

[jfgass]

I have the same issue. I'm connected to the VPN, but I can't connect to any remote machines. I always get the "taking to long to respond" error.