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
Please consider adding it.
Thanks
tct
On 18/03/2019 21:16, selva.n...@gmail.com wrote:
From: Selva Nair <selva.n...@gmail.com>
Make clear that --dhcp-option is not processed on
non-Windows clients and the user is expected to handle
it using an --up script.
Signed-off-by: Selva Nair <selva.n...@gmail.com>
---
doc/openvpn.8 | 18 +++++++++++++-----
1 file changed, 13 insertions(+), 5 deletions(-)
diff --git a/doc/openvpn.8 b/doc/openvpn.8
index ce44044..993c8bd 100644
--- a/doc/openvpn.8
+++ b/doc/openvpn.8
@@ -6026,13 +6026,21 @@ scope IDs. The Scope ID becomes a part of the NetBIOS
name, making the name uniq
.B DISABLE\-NBT \-\-
Disable Netbios\-over\-TCP/IP.
-Note that if
+Note that
+.B \-\-dhcp\-option
+is processed only on Windows clients. If
.B \-\-dhcp\-option
-is pushed via
+is used directly on or pushed via
.B \-\-push
-to a non\-windows client, the option will be saved in the client's
-environment before the up script is called, under
-the name "foreign_option_{n}".
+to a non\-windows client, the option is
+.B only
+saved in the client's
+environment before the
+.B \-\-up
+script is called, under the name "foreign_option_{n}".
+The user has to arrange an
+.B \-\-up
+script to pick up those parameters and act on them as required.
.\"*********************************************************
.TP
.B \-\-tap\-sleep n
_______________________________________________
Openvpn-devel mailing list
Openvpn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openvpn-devel
