[networking-guide] master: Incorrect link for IPv4 DHCP Relay section (b229da0)
by stephenw
Repository : http://git.fedorahosted.org/cgit/docs/networking-guide.git
On branch : master
>---------------------------------------------------------------
commit b229da01a50ae7202f676865519107f70986218c
Author: Stephen Wadeley <swadeley(a)redhat.com>
Date: Tue May 26 12:32:40 2015 +0200
Incorrect link for IPv4 DHCP Relay section
>---------------------------------------------------------------
en-US/DHCP_Servers.xml | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/en-US/DHCP_Servers.xml b/en-US/DHCP_Servers.xml
index 0a5e73a..993799b 100644
--- a/en-US/DHCP_Servers.xml
+++ b/en-US/DHCP_Servers.xml
@@ -308,7 +308,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 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>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_DHCPv4_and_BOOTP_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>.
8 years, 12 months
[networking-guide] f22: Incorrect link for IPv4 DHCP Relay section (4e33ef7)
by stephenw
Repository : http://git.fedorahosted.org/cgit/docs/networking-guide.git
On branch : f22
>---------------------------------------------------------------
commit 4e33ef715ee39090dd10941240d0b35fd795d97d
Author: Stephen Wadeley <swadeley(a)redhat.com>
Date: Tue May 26 12:32:40 2015 +0200
Incorrect link for IPv4 DHCP Relay section
>---------------------------------------------------------------
en-US/DHCP_Servers.xml | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/en-US/DHCP_Servers.xml b/en-US/DHCP_Servers.xml
index 0a5e73a..993799b 100644
--- a/en-US/DHCP_Servers.xml
+++ b/en-US/DHCP_Servers.xml
@@ -308,7 +308,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 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>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_DHCPv4_and_BOOTP_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>.
8 years, 12 months
[networking-guide] f22: Bonding now also supports lockless Tx/Rx (03faa16)
by stephenw
Repository : http://git.fedorahosted.org/cgit/docs/networking-guide.git
On branch : f22
>---------------------------------------------------------------
commit 03faa16bf1d93334f0f79d0c7363468b49b163bc
Author: Stephen Wadeley <swadeley(a)redhat.com>
Date: Tue May 26 09:27:59 2015 +0200
Bonding now also supports lockless Tx/Rx
>---------------------------------------------------------------
en-US/Configure_Network_Teaming.xml | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/en-US/Configure_Network_Teaming.xml b/en-US/Configure_Network_Teaming.xml
index c50c816..35a4163 100644
--- a/en-US/Configure_Network_Teaming.xml
+++ b/en-US/Configure_Network_Teaming.xml
@@ -58,7 +58,7 @@
<row><entry>port priorities and stickiness (<quote>primary</quote> option enhancement)</entry> <entry>No</entry> <entry>Yes</entry></row>
<row><entry>separate per-port link monitoring setup</entry> <entry>No</entry> <entry>Yes</entry></row>
<row><entry>multiple link monitoring setup</entry> <entry>Limited</entry> <entry>Yes</entry></row>
- <row><entry>lockless Tx/Rx path</entry> <entry>No (rwlock)</entry> <entry>Yes (RCU)</entry></row>
+ <row><entry>lockless Tx/Rx path</entry> <entry>Yes (RCU)</entry> <entry>Yes (RCU)</entry></row>
<row><entry>VLAN support</entry> <entry>Yes</entry> <entry>Yes</entry></row>
<row><entry>user-space runtime control</entry> <entry>Limited</entry> <entry>Full</entry></row>
<row><entry>Logic in user-space</entry> <entry>No</entry> <entry>Yes</entry></row>
8 years, 12 months
[networking-guide] master: Bonding now also supports lockless Tx/Rx (cde7145)
by stephenw
Repository : http://git.fedorahosted.org/cgit/docs/networking-guide.git
On branch : master
>---------------------------------------------------------------
commit cde7145b57a7a99e74b17533bdc6079d924e3bbe
Author: Stephen Wadeley <swadeley(a)redhat.com>
Date: Tue May 26 09:27:59 2015 +0200
Bonding now also supports lockless Tx/Rx
>---------------------------------------------------------------
en-US/Configure_Network_Teaming.xml | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/en-US/Configure_Network_Teaming.xml b/en-US/Configure_Network_Teaming.xml
index c50c816..35a4163 100644
--- a/en-US/Configure_Network_Teaming.xml
+++ b/en-US/Configure_Network_Teaming.xml
@@ -58,7 +58,7 @@
<row><entry>port priorities and stickiness (<quote>primary</quote> option enhancement)</entry> <entry>No</entry> <entry>Yes</entry></row>
<row><entry>separate per-port link monitoring setup</entry> <entry>No</entry> <entry>Yes</entry></row>
<row><entry>multiple link monitoring setup</entry> <entry>Limited</entry> <entry>Yes</entry></row>
- <row><entry>lockless Tx/Rx path</entry> <entry>No (rwlock)</entry> <entry>Yes (RCU)</entry></row>
+ <row><entry>lockless Tx/Rx path</entry> <entry>Yes (RCU)</entry> <entry>Yes (RCU)</entry></row>
<row><entry>VLAN support</entry> <entry>Yes</entry> <entry>Yes</entry></row>
<row><entry>user-space runtime control</entry> <entry>Limited</entry> <entry>Full</entry></row>
<row><entry>Logic in user-space</entry> <entry>No</entry> <entry>Yes</entry></row>
8 years, 12 months
[networking-guide] master: Update RevHist to 2-3 (457d81c)
by stephenw
Repository : http://git.fedorahosted.org/cgit/docs/networking-guide.git
On branch : master
>---------------------------------------------------------------
commit 457d81c436aefe6fcab1a6e04297d90227b20b59
Author: Stephen Wadeley <swadeley(a)redhat.com>
Date: Tue May 26 09:00:39 2015 +0200
Update RevHist to 2-3
For Fedora 22 release
>---------------------------------------------------------------
en-US/Revision_History.xml | 15 +++++++++++++++
1 files changed, 15 insertions(+), 0 deletions(-)
diff --git a/en-US/Revision_History.xml b/en-US/Revision_History.xml
index d3bf720..404d22c 100644
--- a/en-US/Revision_History.xml
+++ b/en-US/Revision_History.xml
@@ -8,6 +8,21 @@
<simpara>
<revhistory>
+ <revision>
+ <revnumber>2-3</revnumber>
+ <date>Tue May 26 2015</date>
+ <author>
+ <firstname>Stephen</firstname>
+ <surname>Wadeley</surname>
+ <email>swadeley(a)redhat.com</email>
+ </author>
+ <revdescription>
+ <simplelist>
+ <member>Fedora 22 release of the <citetitle>Networking Guide</citetitle>.</member>
+ </simplelist>
+ </revdescription>
+ </revision>
+
<revision>
<revnumber>2-2</revnumber>
<date>Mon Mar 30 2015</date>
8 years, 12 months
[networking-guide] master: Update entities to 22 (1da1843)
by stephenw
Repository : http://git.fedorahosted.org/cgit/docs/networking-guide.git
On branch : master
>---------------------------------------------------------------
commit 1da18430ae928eefc731f6f58ce8604770f49feb
Author: Stephen Wadeley <swadeley(a)redhat.com>
Date: Tue May 26 08:59:59 2015 +0200
Update entities to 22
>---------------------------------------------------------------
en-US/Networking_Guide.ent | 6 +++---
1 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/en-US/Networking_Guide.ent b/en-US/Networking_Guide.ent
index 7971cc0..ce1fc0c 100644
--- a/en-US/Networking_Guide.ent
+++ b/en-US/Networking_Guide.ent
@@ -7,7 +7,7 @@
<!ENTITY BZURL 'https://bugzilla.redhat.com/enter_bug.cgi?product=&PRODUCT;&component...;'>
<!-- Additional Entities: -->
<!ENTITY MAJOROS "Fedora">
-<!ENTITY MAJOROSVER "Fedora 21">
+<!ENTITY MAJOROSVER "Fedora 22">
<!ENTITY OSORG "The Fedora Project">
-<!ENTITY PKGOS "fc21">
-<!ENTITY PRODVER "21">
+<!ENTITY PKGOS "fc22">
+<!ENTITY PRODVER "22">
8 years, 12 months
[networking-guide] master: Update product num and reset edition to 1.0 (b23169b)
by stephenw
Repository : http://git.fedorahosted.org/cgit/docs/networking-guide.git
On branch : master
>---------------------------------------------------------------
commit b23169b576d95acabeb2abbbaf77cfd48854c662
Author: Stephen Wadeley <swadeley(a)redhat.com>
Date: Tue May 26 07:50:58 2015 +0200
Update product num and reset edition to 1.0
For Fedora 22 release
>---------------------------------------------------------------
en-US/Book_Info.xml | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/en-US/Book_Info.xml b/en-US/Book_Info.xml
index f2f84da..e694177 100644
--- a/en-US/Book_Info.xml
+++ b/en-US/Book_Info.xml
@@ -7,8 +7,8 @@
<title>Networking Guide</title>
<subtitle>Configuration and Administration of Networking for &MAJOROSVER;</subtitle>
<productname>Fedora</productname>
- <productnumber>21</productnumber>
- <edition>2</edition>
+ <productnumber>22</productnumber>
+ <edition>1.0</edition>
<pubsnumber>1</pubsnumber>
<abstract>
<para>
8 years, 12 months
[networking-guide] master: Add: packets_per_slave (1bd956c)
by stephenw
Repository : http://git.fedorahosted.org/cgit/docs/networking-guide.git
On branch : master
>---------------------------------------------------------------
commit 1bd956c21fff617d34a850ac5e42fdb9a0b55137
Author: Stephen Wadeley <swadeley(a)redhat.com>
Date: Mon May 25 07:36:56 2015 +0200
Add: packets_per_slave
>---------------------------------------------------------------
en-US/Configure_Network_Bonding.xml | 13 +++++++++++++
1 files changed, 13 insertions(+), 0 deletions(-)
diff --git a/en-US/Configure_Network_Bonding.xml b/en-US/Configure_Network_Bonding.xml
index 566a9f3..44ef5d2 100644
--- a/en-US/Configure_Network_Bonding.xml
+++ b/en-US/Configure_Network_Bonding.xml
@@ -1213,6 +1213,19 @@ This policy is useful for devices that cannot ever alter their MAC address, or f
<para>The valid range is <userinput>0 - 255</userinput>; the default value is <userinput>1</userinput>. This parameter affects only the active-backup mode.</para>
</listitem>
</varlistentry> not supported by NM -->
+
+<varlistentry>
+ <term>
+ <literal>packets_per_slave=<replaceable>range</replaceable></literal></term>
+ <listitem>
+ <para>
+ Specify the number of packets to transmit through a slave before moving to the next one. When set to <literal>0</literal> then a slave is chosen at random.
+ </para>
+ <para>
+ The valid range is <literal>0</literal> to <literal>65535</literal>; the default value is <literal>1</literal>. This option has effect only in <command>balance-rr</command> mode.</para>
+ </listitem>
+</varlistentry>
+
<varlistentry>
<term>
<literal>primary=<replaceable>interface_name</replaceable>
8 years, 12 months
[networking-guide] master: typo, maintains >> maintain (a003be7)
by stephenw
Repository : http://git.fedorahosted.org/cgit/docs/networking-guide.git
On branch : master
>---------------------------------------------------------------
commit a003be79ef05d909fd6b3c8b60bfb41363faead2
Author: Stephen Wadeley <swadeley(a)redhat.com>
Date: Sat May 23 18:05:18 2015 +0200
typo, maintains >> maintain
>---------------------------------------------------------------
en-US/Configure_Network_Bonding.xml | 3 +--
1 files changed, 1 insertions(+), 2 deletions(-)
diff --git a/en-US/Configure_Network_Bonding.xml b/en-US/Configure_Network_Bonding.xml
index 6140d86..566a9f3 100644
--- a/en-US/Configure_Network_Bonding.xml
+++ b/en-US/Configure_Network_Bonding.xml
@@ -1012,7 +1012,6 @@ bond0</screen>
</listitem>
</varlistentry>
-
<varlistentry>
<term>arp_all_targets=<replaceable>value</replaceable>
</term>
@@ -1292,7 +1291,7 @@ This policy is useful for devices that cannot ever alter their MAC address, or f
</literal>
</term>
<listitem>
- <para>Specifies whether or not <literal>miimon</literal> should use MII/ETHTOOL ioctls or <function>netif_carrier_ok()</function> to determine the link state. The <function>netif_carrier_ok()</function> function relies on the device driver to maintains its state with <literal>netif_carrier_<replaceable>on/off</replaceable></literal>; most device drivers support this function.</para>
+ <para>Specifies whether or not <literal>miimon</literal> should use MII/ETHTOOL ioctls or <function>netif_carrier_ok()</function> to determine the link state. The <function>netif_carrier_ok()</function> function relies on the device driver to maintain its state with <literal>netif_carrier_<replaceable>on/off</replaceable></literal>; most device drivers support this function.</para>
<para>The MII/ETHTOOL ioctls tools utilize a deprecated calling sequence within the kernel. However, this is still configurable in case your device driver does not support <literal>netif_carrier_<replaceable>on/off</replaceable></literal>.</para>
<para>Valid values are:</para>
<itemizedlist>
8 years, 12 months