[673b0d8] | 1 | <?xml version="1.0" encoding="ISO-8859-1"?>
|
---|
[b06ca36] | 2 | <!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
|
---|
| 3 | "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
|
---|
[673b0d8] | 4 | <!ENTITY % general-entities SYSTEM "../general.ent">
|
---|
| 5 | %general-entities;
|
---|
| 6 | ]>
|
---|
[d781ffb] | 7 |
|
---|
[3be4d97] | 8 | <sect1 id="ch-scripts-network">
|
---|
[d781ffb] | 9 | <?dbhtml filename="network.html"?>
|
---|
| 10 |
|
---|
[0cda898] | 11 | <title>General Network Configuration</title>
|
---|
[d781ffb] | 12 |
|
---|
| 13 | <indexterm zone="ch-scripts-network">
|
---|
| 14 | <primary sortas="d-network">network</primary>
|
---|
| 15 | <secondary>configuring</secondary></indexterm>
|
---|
| 16 |
|
---|
| 17 | <para>This section only applies if a network card is to be
|
---|
| 18 | configured.</para>
|
---|
| 19 |
|
---|
[d7f2eb0] | 20 | <para>If a network card will not be used, there is likely no need to create
|
---|
| 21 | any configuration files relating to network cards. If that is the case, you
|
---|
| 22 | will need to remove the <filename class="symlink">network</filename> symlinks
|
---|
| 23 | from all run-level directories (<filename
|
---|
| 24 | class="directory">/etc/rc.d/rc*.d</filename>) after the bootscripts are
|
---|
| 25 | installed in <xref linkend="ch-scripts-bootscripts"/>.</para>
|
---|
[d781ffb] | 26 |
|
---|
[d29a03b] | 27 | <sect2 id='stable-net-names'>
|
---|
[d2c332bc] | 28 | <title>Creating stable names for network interfaces</title>
|
---|
| 29 |
|
---|
[0cda898] | 30 | <para>If there is only one network interface in the system to be
|
---|
| 31 | configured, this section is optional, although it will never be wrong to do
|
---|
| 32 | it. In many cases (e.g. a laptop with a wireless and a wired interface),
|
---|
[2ca8941] | 33 | accomplishing the configuration in this section is necessary.</para>
|
---|
[0cda898] | 34 |
|
---|
[d2c332bc] | 35 | <para>With Udev and modular network drivers, the network interface numbering
|
---|
| 36 | is not persistent across reboots by default, because the drivers are loaded
|
---|
| 37 | in parallel and, thus, in random order. For example, on a computer having
|
---|
| 38 | two network cards made by Intel and Realtek, the network card manufactured
|
---|
| 39 | by Intel may become <filename class="devicefile">eth0</filename> and the
|
---|
| 40 | Realtek card becomes <filename class="devicefile">eth1</filename>. In some
|
---|
| 41 | cases, after a reboot the cards get renumbered the other way around. To
|
---|
[80640a49] | 42 | avoid this, Udev comes with a script and some rules to assign stable names
|
---|
| 43 | to network cards based on their MAC address.</para>
|
---|
| 44 |
|
---|
[d29a03b] | 45 | <para>The rules were pre-generated in the build instructions for
|
---|
| 46 | <application>udev (systemd)</application> in the last chapter. Inspect the
|
---|
| 47 | <filename>/etc/udev/rules.d/70-persistent-net.rules</filename> file, to
|
---|
| 48 | find out which name was assigned to which network device:</para>
|
---|
[80640a49] | 49 |
|
---|
[2f0d64d] | 50 | <screen role="nodump"><userinput>cat /etc/udev/rules.d/70-persistent-net.rules</userinput></screen>
|
---|
[80640a49] | 51 |
|
---|
[d29a03b] | 52 | <note><para>In some cases such as when MAC addresess have been assigned to
|
---|
[f5976ac] | 53 | a network card manually or in a virtual environment such as Xen,
|
---|
[2ca8941] | 54 | the network rules file may not have been generated because addresses
|
---|
[d29a03b] | 55 | are not consistently assigned. In these cases, just continue to
|
---|
| 56 | the next section.</para></note>
|
---|
| 57 |
|
---|
[f801e9ea] | 58 | <para>The file begins with a comment block followed by two lines for each
|
---|
| 59 | NIC. The first line for each NIC is a commented description showing its
|
---|
[61e63d3] | 60 | hardware IDs (e.g. its PCI vendor and device IDs, if it's a PCI card),
|
---|
[f801e9ea] | 61 | along with its driver in parentheses, if the driver can be found. Neither
|
---|
[80640a49] | 62 | the hardware ID nor the driver is used to determine which name to give an
|
---|
[61e63d3] | 63 | interface; this information is only for reference. The second line is the
|
---|
| 64 | Udev rule that matches this NIC and actually assigns it a name.</para>
|
---|
[80640a49] | 65 |
|
---|
| 66 | <para>All Udev rules are made up of several keys, separated by commas and
|
---|
[61e63d3] | 67 | optional whitespace. This rule's keys and an explanation of each of them
|
---|
[80640a49] | 68 | are as follows:</para>
|
---|
| 69 |
|
---|
| 70 | <itemizedlist>
|
---|
| 71 | <listitem>
|
---|
| 72 | <para><literal>SUBSYSTEM=="net"</literal> - This tells Udev to ignore
|
---|
| 73 | devices that are not network cards.</para>
|
---|
| 74 | </listitem>
|
---|
[61e63d3] | 75 | <listitem>
|
---|
| 76 | <para><literal>ACTION=="add"</literal> - This tells Udev to ignore this
|
---|
| 77 | rule for a uevent that isn't an add ("remove" and "change" uevents also
|
---|
| 78 | happen, but don't need to rename network interfaces).</para>
|
---|
| 79 | </listitem>
|
---|
[80640a49] | 80 | <listitem>
|
---|
| 81 | <para><literal>DRIVERS=="?*"</literal> - This exists so that Udev will
|
---|
| 82 | ignore VLAN or bridge sub-interfaces (because these sub-interfaces do
|
---|
| 83 | not have drivers). These sub-interfaces are skipped because the name
|
---|
| 84 | that would be assigned would collide with their parent devices.</para>
|
---|
| 85 | </listitem>
|
---|
| 86 | <listitem>
|
---|
[61e63d3] | 87 | <para><literal>ATTR{address}</literal> - The value of this key is the
|
---|
| 88 | NIC's MAC address.</para>
|
---|
| 89 | </listitem>
|
---|
| 90 | <listitem>
|
---|
| 91 | <para><literal>ATTR{type}=="1"</literal> - This ensures the rule only
|
---|
| 92 | matches the primary interface in the case of certain wireless drivers,
|
---|
| 93 | which create multiple virtual interfaces. The secondary interfaces are
|
---|
| 94 | skipped for the same reason that VLAN and bridge sub-interfaces are
|
---|
| 95 | skipped: there would be a name collision otherwise.</para>
|
---|
[80640a49] | 96 | </listitem>
|
---|
| 97 | <listitem>
|
---|
[61e63d3] | 98 | <para><literal>KERNEL=="eth*"</literal> - This key was added to the
|
---|
| 99 | Udev rule generator to handle machines that have multiple network
|
---|
| 100 | interfaces, all with the same MAC address (the PS3 is one such
|
---|
| 101 | machine). If the independent interfaces have different basenames,
|
---|
| 102 | this key will allow Udev to tell them apart. This is generally not
|
---|
| 103 | necessary for most Linux From Scratch users, but does not hurt.</para>
|
---|
[80640a49] | 104 | </listitem>
|
---|
| 105 | <listitem>
|
---|
| 106 | <para><literal>NAME</literal> - The value of this key is the name that
|
---|
| 107 | Udev will assign to this interface.</para>
|
---|
| 108 | </listitem>
|
---|
| 109 | </itemizedlist>
|
---|
[a3b689f] | 110 |
|
---|
[80640a49] | 111 | <para>The value of <literal>NAME</literal> is the important part. Make sure
|
---|
| 112 | you know which name has been assigned to each of your network cards before
|
---|
| 113 | proceeding, and be sure to use that <literal>NAME</literal> value when
|
---|
| 114 | creating your configuration files below.</para>
|
---|
[c226182] | 115 |
|
---|
[d2c332bc] | 116 | </sect2>
|
---|
| 117 |
|
---|
[d781ffb] | 118 | <sect2>
|
---|
| 119 | <title>Creating Network Interface Configuration Files</title>
|
---|
| 120 |
|
---|
| 121 | <para>Which interfaces are brought up and down by the network script
|
---|
[0cda898] | 122 | depends on the files in <filename
|
---|
| 123 | class="directory">/etc/sysconfig/</filename>. This directory should
|
---|
| 124 | contain a file for each interface to be configured, such as
|
---|
[a2e555d] | 125 | <filename>ifconfig.xyz</filename>, where <quote>xyz</quote> is
|
---|
[0cda898] | 126 | meaningful to the administrator such as the device name (e.g. eth0).
|
---|
| 127 | Inside this file are attributes to this interface, such as its IP
|
---|
[2ca8941] | 128 | address(es), subnet masks, and so forth. It is necessary that
|
---|
[0cda898] | 129 | the stem of the filename be <emphasis>ifconfig</emphasis>.</para>
|
---|
| 130 |
|
---|
| 131 | <para>The following command creates a sample file for the
|
---|
| 132 | <emphasis>eth0</emphasis> device with a static IP address:</para>
|
---|
| 133 |
|
---|
| 134 | <screen><userinput>cd /etc/sysconfig/
|
---|
| 135 | cat > ifconfig.eth0 << "EOF"
|
---|
[d72e04a] | 136 | <literal>ONBOOT=yes
|
---|
[0cda898] | 137 | IFACE=eth0
|
---|
[a088964] | 138 | SERVICE=ipv4-static
|
---|
[00a2bd12] | 139 | IP=192.168.1.1
|
---|
[ba85054d] | 140 | GATEWAY=192.168.1.2
|
---|
[c0155c7] | 141 | PREFIX=24
|
---|
[d72e04a] | 142 | BROADCAST=192.168.1.255</literal>
|
---|
[f67f5cf] | 143 | EOF</userinput></screen>
|
---|
[00a2bd12] | 144 |
|
---|
[d781ffb] | 145 | <para>The values of these variables must be changed in every file to match
|
---|
[0cda898] | 146 | the proper setup.</para>
|
---|
| 147 |
|
---|
| 148 | <para>If the <envar>ONBOOT</envar> variable is set to <quote>yes</quote> the
|
---|
| 149 | network script will bring up the Network Interface Card (NIC) during
|
---|
| 150 | booting of the system. If set to anything but <quote>yes</quote> the NIC
|
---|
| 151 | will be ignored by the network script and not be automatically brought up.
|
---|
| 152 | The interface can be manually started or stopped with the
|
---|
| 153 | <command>ifup</command> and <command>ifdown</command> commands.</para>
|
---|
| 154 |
|
---|
| 155 | <para>The <envar>IFACE</envar> variable defines the interface name,
|
---|
[2ca8941] | 156 | for example, eth0. It is required for all network device configuration
|
---|
[0cda898] | 157 | files. </para>
|
---|
[d781ffb] | 158 |
|
---|
| 159 | <para>The <envar>SERVICE</envar> variable defines the method used for
|
---|
| 160 | obtaining the IP address. The LFS-Bootscripts package has a modular IP
|
---|
| 161 | assignment format, and creating additional files in the <filename
|
---|
[f874424] | 162 | class="directory">/lib/services/</filename> directory allows other IP
|
---|
[0cda898] | 163 | assignment methods. This is commonly used for Dynamic Host Configuration
|
---|
| 164 | Protocol (DHCP), which is addressed in the BLFS book.</para>
|
---|
[d781ffb] | 165 |
|
---|
| 166 | <para>The <envar>GATEWAY</envar> variable should contain the default
|
---|
| 167 | gateway IP address, if one is present. If not, then comment out the
|
---|
| 168 | variable entirely.</para>
|
---|
| 169 |
|
---|
[19e4f62] | 170 | <para>The <envar>PREFIX</envar> variable contains the number of
|
---|
[d781ffb] | 171 | bits used in the subnet. Each octet in an IP address is 8 bits. If the
|
---|
| 172 | subnet's netmask is 255.255.255.0, then it is using the first three octets
|
---|
| 173 | (24 bits) to specify the network number. If the netmask is 255.255.255.240,
|
---|
| 174 | it would be using the first 28 bits. Prefixes longer than 24 bits are
|
---|
| 175 | commonly used by DSL and cable-based Internet Service Providers (ISPs).
|
---|
| 176 | In this example (PREFIX=24), the netmask is 255.255.255.0. Adjust the
|
---|
[970a126] | 177 | <envar>PREFIX</envar> variable according to your specific subnet.i
|
---|
| 178 | If omitted, the PREFIX defaults to 24.</para>
|
---|
| 179 |
|
---|
| 180 | <para>For more information see the <command>ifup</command> man page.</para>
|
---|
[d781ffb] | 181 |
|
---|
| 182 | </sect2>
|
---|
| 183 |
|
---|
| 184 | <sect2 id="resolv.conf">
|
---|
| 185 | <title>Creating the /etc/resolv.conf File</title>
|
---|
| 186 |
|
---|
| 187 | <indexterm zone="resolv.conf">
|
---|
| 188 | <primary sortas="e-/etc/resolv.conf">/etc/resolv.conf</primary>
|
---|
| 189 | </indexterm>
|
---|
| 190 |
|
---|
| 191 | <para>If the system is going to be connected to the Internet, it will
|
---|
| 192 | need some means of Domain Name Service (DNS) name resolution to
|
---|
| 193 | resolve Internet domain names to IP addresses, and vice versa. This is
|
---|
| 194 | best achieved by placing the IP address of the DNS server, available
|
---|
| 195 | from the ISP or network administrator, into
|
---|
| 196 | <filename>/etc/resolv.conf</filename>. Create the file by running the
|
---|
| 197 | following:</para>
|
---|
[45340ae] | 198 |
|
---|
[f67f5cf] | 199 | <screen><userinput>cat > /etc/resolv.conf << "EOF"
|
---|
[d72e04a] | 200 | <literal># Begin /etc/resolv.conf
|
---|
[45340ae] | 201 |
|
---|
[4b51ca76] | 202 | domain <replaceable><Your Domain Name></replaceable>
|
---|
[0090db5] | 203 | nameserver <replaceable><IP address of your primary nameserver></replaceable>
|
---|
| 204 | nameserver <replaceable><IP address of your secondary nameserver></replaceable>
|
---|
[45340ae] | 205 |
|
---|
[d72e04a] | 206 | # End /etc/resolv.conf</literal>
|
---|
[f67f5cf] | 207 | EOF</userinput></screen>
|
---|
[45340ae] | 208 |
|
---|
[0cda898] | 209 | <para>The <varname>domain</varname> statement can be omitted
|
---|
| 210 | or replaced with a <varname>search</varname> statement. See the man page for
|
---|
| 211 | resolv.conf for more details.</para>
|
---|
| 212 |
|
---|
[0090db5] | 213 | <para>Replace <replaceable><IP address of the nameserver></replaceable>
|
---|
[d781ffb] | 214 | with the IP address of the DNS most appropriate for the setup. There will
|
---|
| 215 | often be more than one entry (requirements demand secondary servers for
|
---|
| 216 | fallback capability). If you only need or want one DNS server, remove the
|
---|
| 217 | second <emphasis>nameserver</emphasis> line from the file. The IP address
|
---|
| 218 | may also be a router on the local network.</para>
|
---|
[45340ae] | 219 |
|
---|
[0cda898] | 220 | <note><para>The Google Public IPv4 DNS addresses are 8.8.8.8 and 8.8.4.4.</para></note>
|
---|
| 221 |
|
---|
[d781ffb] | 222 | </sect2>
|
---|
[81fd230] | 223 |
|
---|
[d781ffb] | 224 | </sect1>
|
---|