Fix OpenVPN route gateway is not reachable

by Daniel Pham
Published: Updated:

This article will show you how to fix the gateway route OpenVPN error that is not reachable on any active network adapters.

OpenVPN errors appear on Windows client machines

I have the OpenVPN server installed for the clients in the company to use. Everything is fine but there are some Windows computers that fail as follows.

Warning: route gateway is not reachable on any active network adapters

This error will be displayed in the status log on the client, along with the yellow OpenVPN connection icon.

It appears on Windows 10 client, Windows 7 seems to be better.

Fix OpenVPN error route gateway is not reachable

If you encounter an error above, I hope the way below will help you solve the problem.

I have done it and it’s successful with the client machine in my company.

fix openvpn route gateway is not reachable
Fix OpenVPN route gateway is not reachable.

First, below is the content of the configuration file of the client OpenVPN before fixing the error. For example, file name client.ovpn.

client
remote 192.168.100.10 11194
ca "C:\\Program Files\\OpenVPN\\config\\vpnca.crt"
tls-auth "C:\\Program Files\OpenVPN\config\vpn.tlsauth" 1
auth-user-pass
auth-nocache
auth SHA256
comp-lzo yes
dev tap
proto tcp
nobind
persist-key
persist-tun
remote-cert-tls server
remote-cert-eku "TLS Web Server Authentication"
cipher AES-256-CBC
script-security 2

And I added the following lines to the bottom of the OpenVPN configuration file on the client.

tap-sleep 3
verb 4
route-delay 1 3
route-method exe
ip-win32 netsh

After adding the above lines at the end of the file client.ovpn, save the file. I restart OpenVPN on the client again and it connects successfully.

Conclusion

Above is the experience of sharing error handling that I have encountered with OpenVPN on the client. I hope it will help you in case you encounter it.

(This is an article from my old blog that has been inactive for a long time, I don’t want to throw it away so I will keep it and hope it helps someone).

0 0 votes
Article Rating

You may also like

Subscribe
Notify of
guest
2 Comments
Newest
Oldest Most Voted
Inline Feedbacks
View all comments
Bryan
Bryan
Guest
3 years ago

The above additions worked for me. Note that I tried the suggestions on another site which included setting the tun adapter to always connected. That did not work, but these instructions did.
It would be helpful to let people know what the added otions do.
tap-sleep 3 = Sleep for 3 seconds after the TAP-Win32 adapter state is ‘connected’.
verb 4 = Verbosity level 4. Show more debug info.
route-delay 1 3 = Wait 1 second after connection before adding routes. Wait 3 seconds for the TAP-Win32 adapter to come up before adding routes.
route-method exe = use the route.exe shell command to add routes.
ip-win32 netsh = Use netsh to set the TAP-Win32 adapter IP address and netmask.

Alex
Alex
Guest
3 years ago

Thank you
Its works

DevOps Lite is a personal blog specializing in technology with main topics about DevOps, DevSecOps, SRE and System Administrator. Articles are shared for free and contributed to the community.

SUPPORT US

FOLLOW US

Subscribe my Newsletter for new blog posts. Stay updated from your inbox!

© 2021-2024 DevOpsLite.com – All rights reserved.

Please write sources “DevOpsLite.com” when using articles from this website.

This website uses cookies to improve your experience. We'll assume you're ok with this, but you can opt-out if you wish. Accept Read More

2
0
Would love your thoughts, please comment.x
()
x

Adblock Detected

Please support us by disabling your AdBlocker extension from your browsers for our website.