From: Suzanne Goldlust Date: Wed, 20 Feb 2019 20:02:16 +0000 (-0500) Subject: Update dhcp4-srv.xml to add minor text corrections from Stephen X-Git-Tag: 481-remote-subnet4-set-inconsistent-work-when-id-subnet-is-duplicated_base~16 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=2f632034656c279e748597fc786428c571a4aee7;p=thirdparty%2Fkea.git Update dhcp4-srv.xml to add minor text corrections from Stephen --- diff --git a/doc/guide/dhcp4-srv.xml b/doc/guide/dhcp4-srv.xml index e000691346..a3ba4b7bc3 100644 --- a/doc/guide/dhcp4-srv.xml +++ b/doc/guide/dhcp4-srv.xml @@ -39,7 +39,7 @@ -p server-port - - specifies the UDP local port on which the server will listen. + specifies the local UDP port on which the server will listen. This is only useful during testing, as a DHCPv4 server listening on ports other than the standard ones will not be able to handle regular DHCPv4 queries. @@ -47,7 +47,7 @@ -P client-port - - specifies the UDP remote port to which the server will send + specifies the remote UDP port to which the server will send all responses. This is only useful during testing, as a DHCPv4 server sending responses to ports other than the standard ones will not be able to handle regular DHCPv4 @@ -305,7 +305,7 @@ In some cases it may be preferable to use more compact notation. After all the parameters have been specified, we have two contexts open: global and Dhcp4, so we need two closing curly brackets to close them. In a real-life configuration file there most likely would be an additional -component defined such as Logging, so the closing brace would be followed +component defined such as Logging, so the first closing brace would be followed by a comma and another object definition.