Browse code

Explain that route-nopull also causes the client to ignore dhcp options.

Signed-off-by: Arne Schwabe <arne@rfc2549.org>
Acked-by: David Sommerseth <davids@redhat.com>
Message-Id: 1338642223-20324-5-git-send-email-arne@rfc2549.org
URL: http://article.gmane.org/gmane.network.openvpn.devel/6649
Signed-off-by: David Sommerseth <davids@redhat.com>

Arne Schwabe authored on 2012/06/02 22:03:39
Showing 2 changed files
... ...
@@ -1087,7 +1087,8 @@ When used with
1087 1087
 .B \-\-client
1088 1088
 or
1089 1089
 .B \-\-pull,
1090
-accept options pushed by server EXCEPT for routes.
1090
+accept options pushed by server EXCEPT for routes and dhcp options
1091
+like DNS servers.
1091 1092
 
1092 1093
 When used on the client, this option effectively bars the
1093 1094
 server from adding routes to the client's routing table,
... ...
@@ -231,7 +231,7 @@ static const char usage_message[] =
231 231
   "--route-noexec  : Don't add routes automatically.  Instead pass routes to\n"
232 232
   "                  --route-up script using environmental variables.\n"
233 233
   "--route-nopull  : When used with --client or --pull, accept options pushed\n"
234
-  "                  by server EXCEPT for routes.\n"
234
+  "                  by server EXCEPT for routes and dhcp options.\n"
235 235
   "--allow-pull-fqdn : Allow client to pull DNS names from server for\n"
236 236
   "                    --ifconfig, --route, and --route-gateway.\n"
237 237
   "--redirect-gateway [flags]: Automatically execute routing\n"