network.xml 3.6 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970717273747576777879808182838485868788
  1. <?xml version="1.0" encoding="ISO-8859-1"?>
  2. <!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
  3. <!ENTITY % general-entities SYSTEM "../general.ent">
  4. %general-entities;
  5. ]>
  6. <sect1 id="ch-scripts-network">
  7. <title>Configuring the network script</title>
  8. <?dbhtml filename="network.html"?>
  9. <indexterm zone="ch-scripts-network">
  10. <primary sortas="d-network">network</primary>
  11. <secondary>configuring</secondary></indexterm>
  12. <para>This section only applies if you're going to configure a network
  13. card.</para>
  14. <para>If you don't have any network cards, you are most likely not going to
  15. create any configuration files relating to network cards. If that is the
  16. case, you must remove the <filename>network</filename> symlinks from all the
  17. run-level directories
  18. (<filename class="directory">/etc/rc.d/rc*.d</filename>)</para>
  19. <sect2>
  20. <title>Creating network interface configuration files</title>
  21. <para>Which interfaces are brought up and down by the network script depends on
  22. the files in the /etc/sysconfig/network-devices directory. This
  23. directory should contain files in the form of ifconfig.xyz, where xyz is a
  24. network interface name (such as eth0 or eth0:1)</para>
  25. <para>If you decide to rename or move this /etc/sysconfig/network-devices
  26. directory, make sure you update the /etc/sysconfig/rc file as well and
  27. update the network_devices by providing it with the new path.</para>
  28. <para>Now, new files are created in that directory.
  29. The following command creates a sample ifconfig.eth0 file:</para>
  30. <screen><userinput>cat &gt; /etc/sysconfig/network-devices/ifconfig.eth0 &lt;&lt; "EOF"</userinput>
  31. ONBOOT=yes
  32. SERVICE=static
  33. IP=192.168.1.1
  34. GATEWAY=192.168.1.2
  35. NETMASK=255.255.255.0
  36. BROADCAST=192.168.1.255
  37. <userinput>EOF</userinput></screen>
  38. <para>Of course, the values of those variables have to be changed
  39. in every file to match the proper setup. If the ONBOOT variable is set
  40. to yes, the network script will bring up the equivalent NIC (Network Interface Card)
  41. during the booting of the system.
  42. If set to anything but yes, the equivalent NIC will be ignored by the network script
  43. and not brought up.</para>
  44. <para>The SERVICE entry defines the method of obtaining the IP address.
  45. The LFS bootscripts have a modular IP assignment format, and by creating
  46. additional files in /etc/sysconfig/network-devices/services, you can allow
  47. other IP assignment methods. This would commonly be used if you need DHCP,
  48. which is addressed in the BLFS book.</para>
  49. <para>Of course, GATEWAY should contain the IP of your default gateway, if you
  50. have one. If not, then comment out the variable entirely.</para>
  51. </sect2>
  52. <sect2>
  53. <title>Creating the /etc/resolv.conf file</title>
  54. <para>If you're going to be connected to the Internet then most likely you'll
  55. need some means of DNS name resolution to resolve Internet domain names to IP
  56. addresses. This is best achieved by placing the IP address of your DNS, available from your ISP (Internet Service Provider) or network administrator,
  57. into <filename>/etc/resolv.conf</filename>. Create the file by running the
  58. following:</para>
  59. <screen><userinput>cat &gt; /etc/resolv.conf &lt;&lt; "EOF"</userinput>
  60. # Begin /etc/resolv.conf
  61. nameserver &lt;IP address of your nameserver&gt;
  62. # End /etc/resolv.conf
  63. <userinput>EOF</userinput></screen>
  64. <para>Of course, replace &lt;IP address of your nameserver&gt; with the IP
  65. address of the DNS most appropriate for your setup. There will often be
  66. more than one entry (requirements demand secondary servers for fallback capability). The IP address may even be a router on your local network.</para>
  67. </sect2>
  68. </sect1>