| 123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110 | <?xml version="1.0" encoding="ISO-8859-1"?><!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [  <!ENTITY % general-entities SYSTEM "../general.ent">  %general-entities;]><sect1 id="ch-scripts-network"><title>Configuring the network Script</title><?dbhtml filename="network.html"?><indexterm zone="ch-scripts-network"><primary sortas="d-network">network</primary><secondary>configuring</secondary></indexterm><para>This section only applies if a network card is to beconfigured.</para><para>If a network card will not be used, there is likely no need tocreate any configuration files relating to network cards. If that isthe case, remove the <filename class="symlink">network</filename>symlinks from all run-level directories (<filenameclass="directory">/etc/rc.d/rc*.d</filename>).</para><sect2><title>Creating Network Interface Configuration Files</title><!-- Edit Me --><para>Which interfaces are brought up and down by the network scriptdepends on the files and directories in the <filenameclass="directory">/etc/sysconfig/network-devices</filename> hierarchy.This directory should contain a sub-directory for each interface to be configured,such as <filename>ifconfig.xyz</filename>, where <quote>xyz</quote> is anetwork interface name. Inside this directory would be files definingthe attributes to this interface, such as its IP address(es), subnetmasks, and so forth.</para><para>The following command creates a sample <filename>ipv4</filename> file forthe <emphasis>eth0</emphasis> device:</para><screen><userinput>cd /etc/sysconfig/network-devices &&mkdir -v ifconfig.eth0 &&cat > ifconfig.eth0/ipv4 << "EOF"<literal>ONBOOT=yesSERVICE=ipv4-staticIP=192.168.1.1GATEWAY=192.168.1.2PREFIX=24BROADCAST=192.168.1.255</literal>EOF</userinput></screen><para>The values of these variables must be changed in every file to match theproper setup. If the <envar>ONBOOT</envar> variable is set to <quote>yes</quote>the network script will bring up the Network Interface Card (NIC) during bootingof the system. If set to anything but <quote>yes</quote> the NIC will be ignoredby the network script and not be brought up.</para><para>The <envar>SERVICE</envar> variable defines the method used for obtainingthe IP address. The LFS-Bootscripts package has a modular IP assignment format,and creating additional files in the <filenameclass="directory">/etc/sysconfig/network-devices/services</filename> directoryallows other IP assignment methods. This is commonly used for Dynamic HostConfiguration Protocol (DHCP), which is addressed in the BLFS book.</para><para>The <envar>GATEWAY</envar> variable should containthe default gateway IP address, if one is present. If not, then comment outthe variable entirely.</para><para>The <envar>PREFIX</envar> variable needs to contain the number of bitsused in the subnet. Each octet in an IP address is 8 bits. If the subnet'snetmask is 255.255.255.0, then it is using the first three octets (24 bits) tospecify the network number. If the netmask is 255.255.255.240, it would be usingthe first 28 bits.  Prefixes longer than 24 bits are commonly used by DSL andcable-based Internet Service Providers (ISPs). In this example (PREFIX=24), thenetmask is 255.255.255.0. Adjust the <envar>PREFIX</envar> variable according toyour specific subnet.</para></sect2><sect2 id="resolv.conf"><title>Creating the /etc/resolv.conf File</title><indexterm zone="resolv.conf"><primary sortas="e-/etc/resolv.conf">/etc/resolv.conf</primary></indexterm><para>If the system is going to be connected to the Internet, it willneed some means of Domain Name Service (DNS) name resolution toresolve Internet domain names to IP addresses, and vice versa. This isbest achieved by placing the IP address of the DNS server, availablefrom the ISP or network administrator, into<filename>/etc/resolv.conf</filename>. Create the file by running thefollowing:</para><screen><userinput>cat > /etc/resolv.conf << "EOF"<literal># Begin /etc/resolv.confdomain {<replaceable>[Your Domain Name]</replaceable>}nameserver <replaceable>[IP address of your primary nameserver]</replaceable>nameserver <replaceable>[IP address of your secondary nameserver]</replaceable># End /etc/resolv.conf</literal>EOF</userinput></screen><para>Replace <replaceable>[IP address of thenameserver]</replaceable> with the IP address of the DNS mostappropriate for the setup. There will often be more than one entry(requirements demand secondary servers for fallback capability). Ifyou only need or want one DNS server, remove the second<emphasis>nameserver</emphasis> line from the file. The IP address mayalso be a router on the local network.</para></sect2></sect1>
 |