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..) > > > However, I was thinking that a WARNING in the log when parsing a > dhcp-option without any script configured (on non-windows platform) may > also be beneficial. This would catch some obvious cases but not when a script is being used for some other purpose. Still, sounds useful. Selva _______________________________________________ Openvpn-devel mailing list Openvpn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openvpn-devel
