Hi, On Thu, Mar 7, 2019 at 10:40 AM Lars Schotte <l...@gustik.eu> wrote:
> Very nice, thanks for the advice. > > I think the reason why this question comes up so often is that when you > google it you will get thousends of howtos how to configure a OpenVPN > server on CentOS which is obviously not what I am trying to do here. > > So simply googleing the issue does not help if you do not exactly know > what to look for. That's why I also think that it is a good idea to > have a wiki article written about it so that search engines can deliver > also this kind of result. > I also suggest that we modify the last para of --dhcp-option docs in the man page to clearly indicate that this option is not handled by OpenVPN on non-Windows clients, and that the user has to use a script to pick up the DNS options and update their lcoal "resolver" settings. What we currently have is Note that if --dhcp-option is pushed via --push to a non-win‐ dows client, the option will be saved in the client's environ‐ ment before the up script is called, under the name "for‐ eign_option_{n}". from which its not at all obvious that adding the options to the env is all that OpenVPN does. It sounds more like an extra step done on non-Windows clients. Selva
_______________________________________________ Openvpn-users mailing list Openvpn-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openvpn-users