Red Hat LINUX 7.2 Reference Manual page 184

184
The values required in an interface configuration file can change based on other values. For example,
the ifcfg-eth0 file for an interface utilizing DHCP looks quite a bit different, due to the fact that
IP information is now provided by the DHCP server:
DEVICE=eth0
BOOTPROTO=dhcp
ONBOOT=yes
Most of the time, you will probably want to use a GUI utility, such as Network Configurator (red-
hat-config-network) or netconfig to make changes to the various interface configuration
files. See the Official Red Hat Linux Customization Guide for instructions on using these tools.
Within each of the interface configuration files, the following values are common:
• BOOTPROTO= <protocol> , where <protocol> is one of the following:
– none — No boot-time protocol should be used.
– bootp — The BOOTP protocol should be used.
– dhcp — The DHCP protocol should be used.
• BROADCAST= <address> , where <address> is the broadcast address.
• DEVICE= <name> , where <name> is the name of the physical device (except dynamically-al-
located PPP devices where it is the logical name).
• IPADDR= <address> , where <address> is the IP address.
• NETMASK= <mask> , where <mask> is the netmask value.
• NETWORK= <address> , where <address> is the network address.
• ONBOOT= <answer> , where <answer> is one of the following:
– yes — This device should be activated at boot-time.
– no — This device should not be activated at boot-time.
• USERCTL= <answer> , where <answer> is one of the following:
– true — Non-root users are allowed to control this device.
– false — Non-root users are not allowed to control this device.
Other common interface configuration files that use these options include ifcfg-lo, which con-
trols the IP protocol's local loopback device, ifcfg-irlan0, which arranges settings for the first
infrared device, ifcfg-plip0, which controls the first PLIP device, and ifcfg-tr0, used with
the first Token Ring device.
Chapter 12:Network Scripts