On Wed, Mar 20, 2019 at 10:52 AM tincanteksup <tincantek...@gmail.com> wrote: > > > > On 20/03/2019 13:25, Selva Nair wrote: > > Hi, > > > > On Wed, Mar 20, 2019 at 4:02 AM Antonio Quartulli <a...@unstable.cc> wrote: > >> > >> Hi, > >> > >> On 18/03/2019 22:30, tincanteksup wrote: > >>> Hi, > >>> > >>> this situation has been hanging around for so long is this brief note > >>> really enough? Considering that the manual has numerous other URLs why > >>> not include this URL here: > >>> https://community.openvpn.net/openvpn/wiki/Pushing-DNS-to-clients > >>> > >>> We already have this: > >>> https://community.openvpn.net/openvpn/wiki/SWEET32 > >>> > >> > >> the problem with URLs is that they become obsolete and we need to > >> re-patch the manual in order to update them (or ensure the URL always > >> work/redirect to something). > > > > > > I have the same opinion about URLs. On top of that the wiki > > description is inadequate and inaccurate. But that's a different > > topic. > > Inadequate: > Compared to NOTHING, the page is at least a step toward documentation. > > Inaccurate: > Please expand ..
The wiki states that on Windows using version 2.4, OpenVPN-GUI+interactive service required for processing this option. Not so. Just as in 2.3, it works if run as admin. In fact, several setups run OpenVPN on boot using OpenVPNService, and --dhcp-option does work for them. With 2.4, it also works as limited user if started using the interactive service (for example, using OpenVPN-GUI). In both 2.3 and 2.4, the critical piece is not overriding --ipwin32 method (adaptive or dynamic is required and the latter is the default). Selva On Wed, Mar 20, 2019 at 10:52 AM tincanteksup <tincantek...@gmail.com> wrote: > > > On 20/03/2019 13:25, Selva Nair wrote: > > Hi, > > > > On Wed, Mar 20, 2019 at 4:02 AM Antonio Quartulli <a...@unstable.cc> wrote: > >> > >> Hi, > >> > >> On 18/03/2019 22:30, tincanteksup wrote: > >>> Hi, > >>> > >>> this situation has been hanging around for so long is this brief note > >>> really enough? Considering that the manual has numerous other URLs why > >>> not include this URL here: > >>> https://community.openvpn.net/openvpn/wiki/Pushing-DNS-to-clients > >>> > >>> We already have this: > >>> https://community.openvpn.net/openvpn/wiki/SWEET32 > >>> > >> > >> the problem with URLs is that they become obsolete and we need to > >> re-patch the manual in order to update them (or ensure the URL always > >> work/redirect to something). > > > > > > I have the same opinion about URLs. On top of that the wiki > > description is inadequate and inaccurate. But that's a different > > topic. > > Inadequate: > Compared to NOTHING, the page is at least a step toward documentation. > > Inaccurate: > Please expand .. > >
_______________________________________________ Openvpn-devel mailing list Openvpn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openvpn-devel
