Client not honoring route-nopull in config

point0

I'm trying to set up some custom DNS and routing on a particular client. After some research, I see that "route-nopull" in the client config, and manual routes should do the trick. Trouble is, with that option int he config the client is still pulling DNS and routes from the server.

This is a config that was auto-generated and modified, if that makes a difference. I've tried using the OpenVPN Connect client, and through the OpenVPN GUI on Windows.

Access server 2.1.4b
OpenVPN for Windows 2.3.13
OpenVPN Access for Windows 2.1.3.110

point0

Bump. Anyone else experience this?

SomeGuy

Check to see if you have later configuration items in your client configuration which override your earlier "route-nopull".
To avoid this, make the "route-nopull" the last line in your client config, and enabled "verb 4" to see that your client option is being used in the resulting log file. (This is the most common problem I've seen when adding a config item seems to not change things.)

Make sure that the config file you are altering is actually the one being used by your client. (Second most common cause for changing config not changing use.)

If that does not help, you can try "pull-filter" with accepts and ignores for what you do and do not want added.

If that does not help, you could try this:

pull
route-noexec
route-up YOUR_ROUTE_UP_SCRIPT_HERE
up YOUR_UP_SCRIPT_HERE
down YOUR_DOWN_SCRIPT_HERE

And then have your scripts control what is added and when. It will mean parsing variables/arrays that the calling openvpn prepares for the script to use.

point0

Thanks for the help. After revisiting this and playing around a bit, I'm embarrassed to say it was a simple issue of formatting in the config file. I'm not sure how it happened, but route-nopull and a the next couple of lines ran together without a carriage return. Notepad++ displayed normal, but opening it in notepad showed the issue. :oops: