Admin: ch05: Fill in some networking stuff

1 files changed, 23 insertions, 3 deletions

diff --git a/src/admin/5_networking.xml b/src/admin/5_networking.xml
index 9eb4e71..509e360 100644
--- a/src/admin/5_networking.xml
+++ b/src/admin/5_networking.xml
@@ -1,14 +1,25 @@
 <?xml version="1.0" encoding="utf-8"?>
 <chapter label="5" id="networking">
     <title>Networking</title>
-    <highlights><para>In this chapter, we will discuss how to configure your Adélie Linux system for networking.  Wired, wireless, and VPN connections using both static and dynamic IP addressing will be covered.  In addition, advanced topics including interface bonding and KVM configuration will also be discussed.</para></highlights>
+    <highlights><para>In this chapter, we will discuss how to configure your Adélie Linux system for networking.  Wired, wireless, and VPN connections using both static and dynamic IP addressing will be covered.  In addition, advanced topics including interface bondage and KVM configuration will also be discussed.</para></highlights>
     <section>
         <title>Introduction</title>
-        <para></para>
+        <para>The Adélie Linux system uses <firstterm><package>netifrc</package></firstterm> as its network configuration and management system.  The netifrc system uses a declarative configuration syntax in a single file, <filename>/etc/conf.d/net</filename>, for ease of administration.  All main system network configuration is declared in this file.  Some additional configuration may be required for wireless or VPN connections; notably, wireless connections require WPA Supplicant to be configured using either <package>wpa_gui</package> (on computers that use X11), or in the <filename>/etc/wpa_supplicant/wpa_supplicant.conf</filename> file.</para>
+        <para>The default configuration for the Adélie Linux system uses the traditional Linux interface names (such as "eth0", "eth1", and "wlan0").  If you prefer the new "predictable" interface names (such as "enP2p36s15f0" or "wlp9s0"), refer to <xref linkend="crappy_udev_ifs" />.</para>
+        <section>
+            <title>A netfirc primer</title>
+            <para>The netifrc configuration file consists of INI-style configuration variables.  For example, <literal>config_eth0="dhcp"</literal> sets the variable <varname>config_eth0</varname> to the value <literal>dhcp</literal>.  By default, all interfaces on the system that are enabled will attempt to retrieve a DHCP address, assuming <package>dhcpcd</package> is installed.</para>
+            <para>To enable a network interface, you must create a symbolic link to <filename>/etc/init.d/net.lo</filename> in <filename class="directory">/etc/init.d</filename> named <filename>net.<userinput>IFACE</userinput></filename> where <userinput>IFACE</userinput> is the name of the interface.  For example, for the interface named <literal>eth0</literal>, you would run <command>ln -s /etc/init.d/net.lo /etc/init.d/net.eth0</command>.  Next, you need to add the service to the default runlevel.  As noted in <xref linkend="enable_disable_rc" />, you would run <command>rc-update add net.<userinput>IFACE</userinput> default</command>  to enable the net.<userinput>IFACE</userinput> service.  You may then <link linkend="start_stop_rc">start the service</link>, assuming the interface has been configured properly in <filename>/etc/conf.d/net</filename>.</para>
+            <para>To disable a network interface, you must first <link linkend="start_stop_rc">stop it</link>, if it is running.  Next, <link linkend="enable_disable_rc">remove it from the default runlevel</link> (<command>rc-update del net.<userinput>IFACE</userinput> default</command>).  Finally, remove the symbolic link in <filename class="directory">/etc/init.d</filename>.</para>
+        </section>
+        <section>
+            <title>Identifying adaptors</title>
+            <para>Before we begin configuring the network, we will list the network adaptors available on your computer.  This will ensure that the adaptor or adaptors were detected successfully by the kernel.  To do this, ensure the <package>iproute2</package> package is installed, and run the command <command>ip link</command> as root.</para>
+        </section>
     </section>
     <section>
         <title>Wired connections</title>
-        <para></para>
+        <para>For the purposes of this handbook, a <firstterm>wired connection</firstterm> is a connection to a network that utilises Ethernet.  While the Adélie Linux system supports ATM, CAN bus, IEEE 1394, and Token Ring networking, these connection types are exceedingly rare and out of the scope of this handbook.</para>
         <section>
             <title>Dynamic addressing</title>
             <para></para>
@@ -61,6 +72,15 @@
     <section>
         <title>Advanced topics</title>
         <para></para>
+        <section id="crappy_udev_ifs">
+            <title>Advanced: Using "predictable" network interface names</title>
+            <para></para>
+        </section>
+        <section>
+            <title>Advanced: Multiple interfaces</title>
+            <para></para>
+            <para>Note that by default, all interfaces must be active before the rest of the system will consider the network to be active.  This will cause network services to delay start-up until all interfaces are active.  If this is not desired, you may set <varname>rc_depend_strict</varname> to <literal>NO</literal> in <filename>/etc/rc.conf</filename>.</para>
+        </section>
         <section>
             <title>Advanced: Interface bondage</title>
             <para></para>