References: <1552943809-6367-1-git-send-email-selva.nair@...277...> <5a54b7c9-d466-c8c2-e468-42c16c88d1dd@...277...> <2bf767b9-8459-c0bf-3914-9afaee3093f8@...2181...> From: Arne Schwabe Message-ID: Date: Wed, 20 Mar 2019 14:45:25 +0100 MIME-Version: 1.0 In-Reply-To: Content-Language: en-GB Subject: Re: [Openvpn-devel] [PATCH] Improve the documentation for --dhcp-option List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit To: Selva Nair Cc: "openvpn-devel@lists.sourceforge.net" Am 20.03.19 um 14:25 schrieb Selva Nair: > Hi, > > On Wed, Mar 20, 2019 at 4:02 AM Antonio Quartulli 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. Arne