Hi, On Wed, Mar 20, 2019 at 9:45 AM Arne Schwabe <a...@rfc2549.org> wrote: > > Am 20.03.19 um 14:25 schrieb Selva Nair: > > 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. > > > > The patch was meant to remove the ambiguity in the current > > wording. We could add a line saying many distributions include > > such scripts and front-ends such as network manager, tunnelblick, > > OpenVPN for Android etc. also handle some dhcp-options. (I don't use > > any of them, so guessing here..) > > > > Yes. Most platforms and client interpret this option. Only OpenVPN > itself only interprets it only Windows and Android. It should probably > changed to reflect reality.
In case of Android, its only sent to the management, right? As the man page is about OpenVPN core, I would say the current statement that the option is handled only on Windows is correct. But its useful to expand on the usage on other platforms. I can add a line about scripts in OS distributions and front-ends/UI like Android that can transparently handle it. Selva _______________________________________________ Openvpn-devel mailing list Openvpn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openvpn-devel
