[system-administrators-reference-guide] alias names should not be confused for VLAN names

[stephenw]

commit ff933b834bf549c6ef537e47b71489bb8753adae
Author: Stephen Wadeley <swadeley at redhat.com>
Date:   Mon Mar 17 17:58:48 2014 +0100

    alias names should not be confused for VLAN names

 en-US/Network_Interfaces.xml |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)
---
diff --git a/en-US/Network_Interfaces.xml b/en-US/Network_Interfaces.xml
index 60724d8..9498a5b 100644
--- a/en-US/Network_Interfaces.xml
+++ b/en-US/Network_Interfaces.xml
@@ -788,7 +788,7 @@ ONBOOT=yes</programlisting>
         For new installations, users should select the <guilabel>Manual</guilabel> method on the <systemitem class="protocol">IPv4</systemitem> or <systemitem class="protocol">IPv6</systemitem> tab in <application>NetworkManager</application> to assign multiple <systemitem class="protocol">IP</systemitem> address to the same interface. For more information on using this tool, see the <citetitle pubwork="book">Fedora Networking Guide</citetitle>.
       </para>
       <para>
-        Alias interface configuration files, which are used to bind multiple addresses to a single interface, use the <filename>ifcfg-<replaceable>if-name</replaceable>:<replaceable>alias-value</replaceable></filename> naming scheme.
+        Alias interface configuration files, which are used to bind multiple addresses to a single interface, use the <filename>ifcfg-<replaceable>if-name</replaceable>:<replaceable>alias-value</replaceable></filename> naming scheme. Do not confuse alias <filename>ifcfg</filename> file and interface names with VLAN <filename>ifcfg</filename> file and interface names which take the form: <filename>ifcfg-<replaceable>if-name</replaceable>.<replaceable>vlan-id</replaceable></filename> and <literal>ethX.</literal><replaceable>vlan-id</replaceable> respectively. 
       </para>
       <para>
         For example, an <filename>ifcfg-eth0:0</filename> file could be configured to specify <literal>DEVICE=eth0:0</literal> and a static <systemitem class="protocol">IP</systemitem> address of <systemitem class="ipaddress">10.0.0.2</systemitem>, serving as an alias of an Ethernet interface already configured to receive its <systemitem class="protocol">IP</systemitem> information via <systemitem class="protocol">DHCP</systemitem> in <filename>ifcfg-eth0</filename>. Under this configuration, <systemitem class="etheraddress">eth0</systemitem> is bound to a dynamic <systemitem class="protocol">IP</systemitem> address, but the same physical network card can receive requests via the fixed, <systemitem class="ipaddress">10.0.0.2</systemitem> <systemitem class="protocol">IP</systemitem> address.