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 |
|
---|
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 you're going to configure a network
|
---|
15 | card.</para>
|
---|
16 |
|
---|
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
|
---|
19 | case, you must remove the <filename class="symlink">network</filename> symlinks from all the
|
---|
20 | run-level directories
|
---|
21 | (<filename class="directory">/etc/rc.d/rc*.d</filename>)</para>
|
---|
22 |
|
---|
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
|
---|
27 | the files in the <filename class="directory">/etc/sysconfig/network-devices</filename> directory. This
|
---|
28 | directory should contain subdirectories in the form of
|
---|
29 | <filename>ifconfig.xyz</filename>, where <quote>xyz</quote> is a network
|
---|
30 | interface name (such as eth0)</para>
|
---|
31 |
|
---|
32 | <para>If you decide to rename or move this
|
---|
33 | <filename class="directory">/etc/sysconfig/network-devices</filename> directory,
|
---|
34 | make sure you update the <filename>/etc/sysconfig/rc</filename> file as well and
|
---|
35 | update the <quote>network_devices</quote> by providing it with the new path.</para>
|
---|
36 |
|
---|
37 | <para>Now, new files are created in that directory. The following command
|
---|
38 | creates a sample <filename>ipv4</filename> file for the
|
---|
39 | <filename>eth0</filename> device:</para>
|
---|
40 |
|
---|
41 | <screen><userinput>cd /etc/sysconfig/network-devices &&
|
---|
42 | mkdir ifconfig.eth0 &&
|
---|
43 | cat > ifconfig.eth0/ipv4 << "EOF"
|
---|
44 | ONBOOT=yes
|
---|
45 | SERVICE=ipv4-static
|
---|
46 | IP=192.168.1.1
|
---|
47 | GATEWAY=192.168.1.2
|
---|
48 | PREFIX=24
|
---|
49 | BROADCAST=192.168.1.255
|
---|
50 | EOF</userinput></screen>
|
---|
51 |
|
---|
52 | <para>Of course, the values of those variables have to be changed in every file
|
---|
53 | to match the proper setup. If the ONBOOT variable is set to <quote>yes</quote>,
|
---|
54 | the network script will bring up the equivalent interface during the booting of
|
---|
55 | the system. If set to anything but <quote>yes</quote>, the equivalent interface
|
---|
56 | will be ignored by the network script and not brought up.</para>
|
---|
57 |
|
---|
58 | <para>The SERVICE entry defines the method of obtaining the IP address. The LFS
|
---|
59 | bootscripts have a modular IP assignment format, and by creating additional
|
---|
60 | files in
|
---|
61 | <filename class="directory">/etc/sysconfig/network-devices/services</filename>,
|
---|
62 | you can allow other IP assignment methods. This would commonly be used if you
|
---|
63 | need DHCP, which is addressed in the BLFS book.</para>
|
---|
64 |
|
---|
65 | <para>Of course, GATEWAY should contain the IP of your default gateway, if you
|
---|
66 | have one. If not, then don't include the GATEWAY line in the configuration
|
---|
67 | file.</para>
|
---|
68 |
|
---|
69 | </sect2>
|
---|
70 |
|
---|
71 | <sect2 id="resolv.conf">
|
---|
72 | <title>Creating the /etc/resolv.conf file</title>
|
---|
73 | <indexterm zone="resolv.conf"><primary sortas="e-/etc/resolv.conf">/etc/resolv.conf</primary></indexterm>
|
---|
74 |
|
---|
75 | <para>If you're going to be connected to the Internet then most likely you'll
|
---|
76 | need some means of DNS name resolution to resolve Internet domain names to IP
|
---|
77 | addresses. This is best achieved by placing the IP address of your assigned DNS
|
---|
78 | resolver, available from your ISP (Internet Service Provider) or network
|
---|
79 | administrator, into <filename>/etc/resolv.conf</filename>. Create the file by
|
---|
80 | running the following:</para>
|
---|
81 |
|
---|
82 | <screen><userinput>cat > /etc/resolv.conf << "EOF"
|
---|
83 | # Begin /etc/resolv.conf
|
---|
84 |
|
---|
85 | domain {<replaceable>[Your Domain Name]</replaceable>}
|
---|
86 | nameserver <replaceable>[IP address of your nameserver]</replaceable>
|
---|
87 |
|
---|
88 | # End /etc/resolv.conf
|
---|
89 | EOF</userinput></screen>
|
---|
90 |
|
---|
91 | <para>Of course, replace
|
---|
92 | <replaceable>[IP address of your nameserver]</replaceable> with the IP address
|
---|
93 | of the DNS resolver assigned for your use. There will often be more than one
|
---|
94 | entry (requirements demand secondary servers for fallback capability). The IP
|
---|
95 | address may even be a router on your local network.</para>
|
---|
96 |
|
---|
97 | </sect2>
|
---|
98 |
|
---|
99 | </sect1>
|
---|