network.xml 10 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246
  1. <?xml version="1.0" encoding="ISO-8859-1"?>
  2. <!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
  3. "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
  4. <!ENTITY % general-entities SYSTEM "../general.ent">
  5. %general-entities;
  6. ]>
  7. <sect1 id="ch-scripts-network" revision="sysv">
  8. <?dbhtml filename="network.html"?>
  9. <title>General Network Configuration</title>
  10. <indexterm zone="ch-scripts-network">
  11. <primary sortas="d-network">network</primary>
  12. <secondary>configuring</secondary></indexterm>
  13. <!--
  14. <para>This section only applies if a network card is to be
  15. configured.</para>
  16. <para>If a network card will not be used, there is likely no need to create
  17. any configuration files relating to network cards. If that is the case, you
  18. will need to remove the <filename class="symlink">network</filename> symlinks
  19. from all run-level directories (<filename
  20. class="directory">/etc/rc.d/rc*.d</filename>) after the bootscripts are
  21. installed in <xref linkend="ch-scripts-bootscripts"/>.</para>
  22. -->
  23. <sect2>
  24. <title>Creating Network Interface Configuration Files</title>
  25. <para>Which interfaces are brought up and down by the network script
  26. usually depends on the files in <filename
  27. class="directory">/etc/sysconfig/</filename>. This directory should
  28. contain a file for each interface to be configured, such as
  29. <filename>ifconfig.xyz</filename>, where <quote>xyz</quote> should describe
  30. the network card. The interface name (e.g. eth0) is usually appropriate.
  31. Inside this file are attributes to this interface, such as its IP
  32. address(es), subnet masks, and so forth. It is necessary that the stem of
  33. the filename be <emphasis>ifconfig</emphasis>.</para>
  34. <note><para>If the procedure in the previous section was not used, Udev
  35. will assign network card interface names based on system physical
  36. characteristics such as enp2s1. If you are not sure what your interface
  37. name is, you can always run <command>ip link</command> or <command>ls
  38. /sys/class/net</command> after you have booted your system.
  39. </para></note>
  40. <para>The following command creates a sample file for the
  41. <emphasis>eth0</emphasis> device with a static IP address:</para>
  42. <screen><userinput>cd /etc/sysconfig/
  43. cat &gt; ifconfig.eth0 &lt;&lt; "EOF"
  44. <literal>ONBOOT=yes
  45. IFACE=eth0
  46. SERVICE=ipv4-static
  47. IP=192.168.1.2
  48. GATEWAY=192.168.1.1
  49. PREFIX=24
  50. BROADCAST=192.168.1.255</literal>
  51. EOF</userinput></screen>
  52. <para>The values of these variables must be changed in every file to match
  53. the proper setup.</para>
  54. <para>If the <envar>ONBOOT</envar> variable is set to <quote>yes</quote> the
  55. System V network script will bring up the Network Interface Card (NIC) during
  56. booting of the system. If set to anything but <quote>yes</quote> the NIC
  57. will be ignored by the network script and not be automatically brought up.
  58. The interface can be manually started or stopped with the
  59. <command>ifup</command> and <command>ifdown</command> commands.</para>
  60. <para>The <envar>IFACE</envar> variable defines the interface name,
  61. for example, eth0. It is required for all network device configuration
  62. files. </para>
  63. <para>The <envar>SERVICE</envar> variable defines the method used for
  64. obtaining the IP address. The LFS-Bootscripts package has a modular IP
  65. assignment format, and creating additional files in the <filename
  66. class="directory">/lib/services/</filename> directory allows other IP
  67. assignment methods. This is commonly used for Dynamic Host Configuration
  68. Protocol (DHCP), which is addressed in the BLFS book.</para>
  69. <para>The <envar>GATEWAY</envar> variable should contain the default
  70. gateway IP address, if one is present. If not, then comment out the
  71. variable entirely.</para>
  72. <para>The <envar>PREFIX</envar> variable contains the number of
  73. bits used in the subnet. Each octet in an IP address is 8 bits. If the
  74. subnet's netmask is 255.255.255.0, then it is using the first three octets
  75. (24 bits) to specify the network number. If the netmask is 255.255.255.240,
  76. it would be using the first 28 bits. Prefixes longer than 24 bits are
  77. commonly used by DSL and cable-based Internet Service Providers (ISPs).
  78. In this example (PREFIX=24), the netmask is 255.255.255.0. Adjust the
  79. <envar>PREFIX</envar> variable according to your specific subnet.
  80. If omitted, the PREFIX defaults to 24.</para>
  81. <para>For more information see the <command>ifup</command> man page.</para>
  82. </sect2>
  83. <sect2 id="resolv.conf">
  84. <title>Creating the /etc/resolv.conf File</title>
  85. <indexterm zone="resolv.conf">
  86. <primary sortas="e-/etc/resolv.conf">/etc/resolv.conf</primary>
  87. </indexterm>
  88. <para>The system will need some means of obtaining Domain Name Service
  89. (DNS) name resolution to resolve Internet domain names to IP addresses, and
  90. vice versa. This is best achieved by placing the IP address of the DNS
  91. server, available from the ISP or network administrator, into
  92. <filename>/etc/resolv.conf</filename>. Create the file by running the
  93. following:</para>
  94. <screen><userinput>cat &gt; /etc/resolv.conf &lt;&lt; "EOF"
  95. <literal># Begin /etc/resolv.conf
  96. domain <replaceable>&lt;Your Domain Name&gt;</replaceable>
  97. nameserver <replaceable>&lt;IP address of your primary nameserver&gt;</replaceable>
  98. nameserver <replaceable>&lt;IP address of your secondary nameserver&gt;</replaceable>
  99. # End /etc/resolv.conf</literal>
  100. EOF</userinput></screen>
  101. <para>The <varname>domain</varname> statement can be omitted
  102. or replaced with a <varname>search</varname> statement. See the man page for
  103. resolv.conf for more details.</para>
  104. <para>Replace <replaceable>&lt;IP address of the nameserver&gt;</replaceable>
  105. with the IP address of the DNS most appropriate for the setup. There will
  106. often be more than one entry (requirements demand secondary servers for
  107. fallback capability). If you only need or want one DNS server, remove the
  108. second <emphasis>nameserver</emphasis> line from the file. The IP address
  109. may also be a router on the local network.</para>
  110. <note>
  111. <para>The Google Public IPv4 DNS addresses are 8.8.8.8 and 8.8.4.4.</para>
  112. </note>
  113. </sect2>
  114. <sect2 id="ch-scripts-hostname">
  115. <title>Configuring the system hostname</title>
  116. <indexterm zone="ch-scripts-hostname">
  117. <primary sortas="d-hostname">hostname</primary>
  118. <secondary>configuring</secondary>
  119. </indexterm>
  120. <para>During the boot process, the file <filename>/etc/hostname</filename>
  121. is used for establishing the system's hostname.</para>
  122. <para>Create the <filename>/etc/hostname</filename> file and enter a
  123. hostname by running:</para>
  124. <screen><userinput>echo "<replaceable>&lt;lfs&gt;</replaceable>" &gt; /etc/hostname</userinput></screen>
  125. <para><replaceable>&lt;lfs&gt;</replaceable> needs to be replaced with the
  126. name given to the computer. Do not enter the Fully Qualified Domain Name
  127. (FQDN) here. That information is put in the
  128. <filename>/etc/hosts</filename> file.</para>
  129. </sect2>
  130. <sect2 id="ch-scripts-hosts">
  131. <title>Customizing the /etc/hosts File</title>
  132. <indexterm zone="ch-scripts-hosts">
  133. <primary sortas="e-/etc/hosts">/etc/hosts</primary>
  134. </indexterm>
  135. <indexterm zone="ch-scripts-hosts">
  136. <primary sortas="d-localnet">localnet</primary>
  137. <secondary>/etc/hosts</secondary>
  138. </indexterm>
  139. <indexterm zone="ch-scripts-hosts">
  140. <primary sortas="d-network">network</primary>
  141. <secondary>/etc/hosts</secondary>
  142. </indexterm>
  143. <para>Decide on the IP address, fully-qualified domain name (FQDN), and
  144. possible aliases for use in the <filename>/etc/hosts</filename> file. The
  145. syntax is:</para>
  146. <screen><literal>IP_address myhost.example.org aliases</literal></screen>
  147. <para>Unless the computer is to be visible to the Internet (i.e., there is
  148. a registered domain and a valid block of assigned IP addresses&mdash;most
  149. users do not have this), make sure that the IP address is in the private
  150. network IP address range. Valid ranges are:</para>
  151. <screen><literal>Private Network Address Range Normal Prefix
  152. 10.0.0.1 - 10.255.255.254 8
  153. 172.x.0.1 - 172.x.255.254 16
  154. 192.168.y.1 - 192.168.y.254 24</literal></screen>
  155. <para>x can be any number in the range 16-31. y can be any number in the
  156. range 0-255.</para>
  157. <para>A valid private IP address could be 192.168.1.1. A valid FQDN for
  158. this IP could be lfs.example.org.</para>
  159. <para>Even if not using a network card, a valid FQDN is still required.
  160. This is necessary for certain programs to operate correctly.</para>
  161. <para>Create the <filename>/etc/hosts</filename> file by running:</para>
  162. <screen><userinput>cat &gt; /etc/hosts &lt;&lt; "EOF"
  163. <literal># Begin /etc/hosts
  164. 127.0.0.1 localhost
  165. 127.0.1.1 <replaceable>&lt;FQDN&gt;</replaceable> <replaceable>&lt;HOSTNAME&gt;</replaceable>
  166. <replaceable>&lt;192.168.1.1&gt;</replaceable> <replaceable>&lt;FQDN&gt;</replaceable> <replaceable>&lt;HOSTNAME&gt;</replaceable> <replaceable>[alias1] [alias2 ...]</replaceable>
  167. ::1 localhost ip6-localhost ip6-loopback
  168. ff02::1 ip6-allnodes
  169. ff02::2 ip6-allrouters
  170. # End /etc/hosts</literal>
  171. EOF</userinput></screen>
  172. <para>The <replaceable>&lt;192.168.1.1&gt;</replaceable>,
  173. <replaceable>&lt;FQDN&gt;</replaceable>, and
  174. <replaceable>&lt;HOSTNAME&gt;</replaceable> values need to be
  175. changed for specific uses or requirements (if assigned an IP address by a
  176. network/system administrator and the machine will be connected to an
  177. existing network). The optional alias name(s) can be omitted.</para>
  178. <!-- This is not very useful
  179. <para>If a network card is not going to be configured, create the
  180. <filename>/etc/hosts</filename> file by running:</para>
  181. <screen role="nodump"><userinput>cat &gt; /etc/hosts &lt;&lt; "EOF"
  182. <literal># Begin /etc/hosts (no network card version)
  183. 127.0.0.1 localhost
  184. 127.0.1.1 <replaceable>&lt;FQDN&gt;</replaceable> <replaceable>&lt;HOSTNAME&gt;</replaceable>
  185. ::1 localhost ip6-localhost ip6-loopback
  186. ff02::1 ip6-allnodes
  187. ff02::2 ip6-allrouters
  188. # End /etc/hosts (no network card version)</literal>
  189. EOF</userinput></screen> -->
  190. </sect2>
  191. </sect1>