Hi David, On 08/02/17 13:52, David Sommerseth wrote: > You need to check what the resolvconf script on your computer does, and > if there is a way to configure it to behave differently. > > Otherwise, you can try to uninstall that script. Then the > update-resolv-conf script (if it is based on the client.up script we > ship with OpenVPN), should rename /etc/resolv.conf, create a new one > with only the VPN provided DNS servers, and switch back afterwords. The > problem with this approach is if you use --user/--group in your OpenVPN > config, then you must run the client.down script via the down-root > plugin - otherwise the resolv.conf file is not restored properly.
Thanks for your help. Debian's /etc/openvpn/update-resolv-conf script is a bit different from client.up/client.down -- it simply gives up if /sbin/resolvconf doesn't exist. Also I wouldn't want resolvconf as I guess it's needed when not running OpenVPN. But I now got it basically working by downloading the client.up/client.down scripts and modifying them to simply skip the call to resolvconf, using the fallback solution instead. However, I don't know how to compile the down-root plugin -- I cloned the repo and the README says I should simply invoke "make". But there is no "Makefile" in the src/plugins/down-root directory, only "Makefile.am". "automake" or "autoreconf" don't work either (they ask for 'configure.ac' or 'configure.in'). Any hints? Thanks Matthias ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot _______________________________________________ Openvpn-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openvpn-users
