Repository :
http://git.fedorahosted.org/cgit/docs/networking-guide.git
On branch : master
---------------------------------------------------------------
commit b362ca0ca4f87bd23781de0d6d0de9c8e26ccd8d
Author: Stephen Wadeley <swadeley(a)redhat.com>
Date: Mon Aug 4 11:46:21 2014 +0200
DHCP: Clarify if no interfaces specified
Behavior is different for IPv4 and IPv6
---------------------------------------------------------------
en-US/DHCP_Servers.xml | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/en-US/DHCP_Servers.xml b/en-US/DHCP_Servers.xml
index 6a28696..2848fb3 100644
--- a/en-US/DHCP_Servers.xml
+++ b/en-US/DHCP_Servers.xml
@@ -307,7 +307,7 @@ Then, as the <systemitem
class="username">root</systemitem> user, restart the se
When a <systemitem class="protocol">DHCP</systemitem> client
requests information, the DHCP Relay Agent forwards the request to the list of
<systemitem class="protocol">DHCP</systemitem> servers specified
when the DHCP Relay Agent is started. When a <systemitem
class="protocol">DHCP</systemitem> server returns a reply, the reply is
broadcast or unicast on the network that sent the original request.
</para>
- <para>The DHCP Relay Agent listens for DHCP requests on all interfaces unless
the interfaces are specified in <filename>/etc/sysconfig/dhcrelay</filename>
with the <computeroutput>INTERFACES</computeroutput> directive.</para>
+ <para>The DHCP Relay Agent for <systemitem
class="protocol">IPv4</systemitem>,
<application>dhcrelay</application>, listens for <systemitem
class="protocol">DHCPv4</systemitem> and <systemitem
class="protocol">BOOTP</systemitem> requests on all interfaces unless
the interfaces are specified in <filename>/etc/sysconfig/dhcrelay</filename>
with the <computeroutput>INTERFACES</computeroutput> directive. See <xref
linkend="sec-Configure_dhcrelay_as_a_DHCPv6_relay_agent" />. The DHCP Relay
Agent for <systemitem class="protocol">IPv6</systemitem>,
<application>dhcrelay6</application>, does not have this default behavior and
interfaces to listen for <systemitem
class="protocol">DHCPv6</systemitem> requests must be specified. See
<xref linkend="sec-Configure_dhcrelay_as_a_DHCPv6_relay_agent"
/>.</para>
<para>
<application>dhcrelay</application> can either be run as a
<systemitem class="protocol">DHCPv4</systemitem> and <systemitem
class="protocol">BOOTP</systemitem> relay agent (by default) or as a
<systemitem class="protocol">DHCPv6</systemitem> relay agent (with
<option>-6</option> argument). To see the usage message, issue the command
<command>dhcrelay -h</command>.
@@ -330,7 +330,7 @@ Edit the <option>ExecStart</option> option under section
[Service] and add one o
<synopsis>ExecStart=/usr/sbin/dhcrelay -d --no-pid 192.168.1.1</synopsis>
</para>
<para>
-If you also want to specify interfaces where the DHCP Relay Agent listens for
<systemitem class="protocol">DHCP</systemitem> requests, add them to
the <option>ExecStart</option> option with <option>-i</option>
argument, for example:
+If you also want to specify interfaces where the DHCP Relay Agent listens for
<systemitem class="protocol">DHCP</systemitem> requests, add them to
the <option>ExecStart</option> option with <option>-i</option>
argument (otherwise it will listen on all interfaces), for example:
<synopsis>ExecStart=/usr/sbin/dhcrelay -d --no-pid 192.168.1.1 -i
em1</synopsis>
For other options see the <filename>dhcrelay(8)</filename> man page.
</para>