[673b0d8] | 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 | ]>
|
---|
[3be4d97] | 6 | <sect1 id="ch-scripts-network">
|
---|
[00a2bd12] | 7 | <title>Configuring the network script</title>
|
---|
[673b0d8] | 8 | <?dbhtml filename="network.html"?>
|
---|
| 9 |
|
---|
| 10 | <indexterm zone="ch-scripts-network">
|
---|
| 11 | <primary sortas="d-network">network</primary>
|
---|
| 12 | <secondary>configuring</secondary></indexterm>
|
---|
[00a2bd12] | 13 |
|
---|
| 14 | <para>This section only applies if you're going to configure a network
|
---|
| 15 | card.</para>
|
---|
| 16 |
|
---|
[6547aa1] | 17 | <para>If you don't have any network cards, you are most likely not going to
|
---|
| 18 | create any configuration files relating to network cards. If that is the
|
---|
[f67f5cf] | 19 | case, you must remove the <filename class="symlink">network</filename> symlinks from all the
|
---|
[673b0d8] | 20 | run-level directories
|
---|
[6547aa1] | 21 | (<filename class="directory">/etc/rc.d/rc*.d</filename>)</para>
|
---|
| 22 |
|
---|
[00a2bd12] | 23 | <sect2>
|
---|
| 24 | <title>Creating network interface configuration files</title>
|
---|
| 25 |
|
---|
| 26 | <para>Which interfaces are brought up and down by the network script depends on
|
---|
[f67f5cf] | 27 | the files in the <filename class="directory">/etc/sysconfig/network-devices</filename> directory. This
|
---|
| 28 | directory should contain files in the form of <filename>ifconfig.xyz</filename>, where <quote>xyz</quote> is a
|
---|
[00a2bd12] | 29 | network interface name (such as eth0 or eth0:1)</para>
|
---|
| 30 |
|
---|
[f67f5cf] | 31 | <para>If you decide to rename or move this <filename class="directory">/etc/sysconfig/network-devices</filename>
|
---|
| 32 | directory, make sure you update the <filename>/etc/sysconfig/rc</filename> file as well and
|
---|
| 33 | update the <quote>network_devices</quote> by providing it with the new path.</para>
|
---|
[e92f48b] | 34 |
|
---|
[673b0d8] | 35 | <para>Now, new files are created in that directory.
|
---|
[f67f5cf] | 36 | The following command creates a sample <filename>ifconfig.eth0</filename> file:</para>
|
---|
[00a2bd12] | 37 |
|
---|
[f67f5cf] | 38 | <screen><userinput>cat > /etc/sysconfig/network-devices/ifconfig.eth0 << "EOF"
|
---|
[00a2bd12] | 39 | ONBOOT=yes
|
---|
[673b0d8] | 40 | SERVICE=static
|
---|
[00a2bd12] | 41 | IP=192.168.1.1
|
---|
[ba85054d] | 42 | GATEWAY=192.168.1.2
|
---|
[00a2bd12] | 43 | NETMASK=255.255.255.0
|
---|
| 44 | BROADCAST=192.168.1.255
|
---|
[f67f5cf] | 45 | EOF</userinput></screen>
|
---|
[00a2bd12] | 46 |
|
---|
| 47 | <para>Of course, the values of those variables have to be changed
|
---|
[3c8d339] | 48 | in every file to match the proper setup. If the ONBOOT variable is set
|
---|
[f67f5cf] | 49 | to <quote>yes</quote>, the network script will bring up the equivalent NIC (Network Interface Card)
|
---|
[673b0d8] | 50 | during the booting of the system.
|
---|
[f67f5cf] | 51 | If set to anything but <quote>yes</quote>, the equivalent NIC will be ignored by the network script
|
---|
[673b0d8] | 52 | and not brought up.</para>
|
---|
| 53 |
|
---|
| 54 | <para>The SERVICE entry defines the method of obtaining the IP address.
|
---|
| 55 | The LFS bootscripts have a modular IP assignment format, and by creating
|
---|
[f67f5cf] | 56 | additional files in <filename class="directory">/etc/sysconfig/network-devices/services</filename>, you can allow
|
---|
[673b0d8] | 57 | other IP assignment methods. This would commonly be used if you need DHCP,
|
---|
| 58 | which is addressed in the BLFS book.</para>
|
---|
[00a2bd12] | 59 |
|
---|
[ba85054d] | 60 | <para>Of course, GATEWAY should contain the IP of your default gateway, if you
|
---|
[4a80bec] | 61 | have one. If not, then comment out the variable entirely.</para>
|
---|
[ba85054d] | 62 |
|
---|
[00a2bd12] | 63 | </sect2>
|
---|
| 64 |
|
---|
[f67f5cf] | 65 | <sect2 id="resolv.conf">
|
---|
[45340ae] | 66 | <title>Creating the /etc/resolv.conf file</title>
|
---|
[f67f5cf] | 67 | <indexterm zone="resolv.conf"><primary sortas="e-/etc/resolv.conf">/etc/resolv.conf</primary></indexterm>
|
---|
[45340ae] | 68 |
|
---|
[673b0d8] | 69 | <para>If you're going to be connected to the Internet then most likely you'll
|
---|
| 70 | need some means of DNS name resolution to resolve Internet domain names to IP
|
---|
| 71 | addresses. This is best achieved by placing the IP address of your DNS, available from your ISP (Internet Service Provider) or network administrator,
|
---|
[45340ae] | 72 | into <filename>/etc/resolv.conf</filename>. Create the file by running the
|
---|
| 73 | following:</para>
|
---|
| 74 |
|
---|
[f67f5cf] | 75 | <screen><userinput>cat > /etc/resolv.conf << "EOF"
|
---|
[45340ae] | 76 | # Begin /etc/resolv.conf
|
---|
| 77 |
|
---|
[f67f5cf] | 78 | nameserver <replaceable>[IP address of your nameserver]</replaceable>
|
---|
[45340ae] | 79 |
|
---|
| 80 | # End /etc/resolv.conf
|
---|
[f67f5cf] | 81 | EOF</userinput></screen>
|
---|
[45340ae] | 82 |
|
---|
[f67f5cf] | 83 | <para>Of course, replace <replaceable>[IP address of your nameserver]</replaceable> with the IP
|
---|
[673b0d8] | 84 | address of the DNS most appropriate for your setup. There will often be
|
---|
| 85 | more than one entry (requirements demand secondary servers for fallback capability). The IP address may even be a router on your local network.</para>
|
---|
[45340ae] | 86 |
|
---|
| 87 | </sect2>
|
---|
| 88 |
|
---|
[00a2bd12] | 89 | </sect1>
|
---|