108
8.2.4. Alias and Clone Files
Two lesser-used types of interface configuration files are alias and clone files.
Alias
interface
ifcfg- if-name : alias-value
single interface.
For example, an
ifcfg-eth0:0
IP address of 10.0.0.2, serving as an alias of an Ethernet interface already configured to receive its
IP information via DHCP in
address, but the same physical network card can receive request via the fixed, 10.0.0.2 IP address.
Caution
Alias interfaces do not support DHCP.
A
clone
interface
ifcfg- if-name - clone-name
interface, a clone file is used to specify additional options for an interface. For example, a standard
DHCP Ethernet interface called
DEVICE=eth0
ONBOOT=yes
BOOTPROTO=dhcp
Since the default value for the
interface up and down. To give users the ability to control the interface, create a clone by copying
to
ifcfg-eth0
ifcfg-eth0-user
USERCTL=yes
This way a user can bring up the
cause the configuration options from
is a very basic example, this method can be used with a variety of options and interfaces.
The easiest way to create alias and clone interface configuration files is to use the graphical Network
Administration Tool. For more on using this tool, refer to the chapter called Network Configuration
in the Red Hat Enterprise Linux System Administration Guide.
8.2.5. Dialup Interfaces
If connecting to the Internet via a dialup connection, a configuration file is necessary for the interface.
PPP interface files are named using the following format
number corresponding to a specific interface).
The PPP interface configuration file is created automatically when
tration Tool or Kppp is used to create a dialup account. It is also possible to create and edit this file
manually.
The following is a typical
DEVICE=ppp0
NAME=test
WVDIALSECT=test
MODEMPORT=/dev/modem
configuration
files
. They are used primarily to bind multiple addresses to a
file could be configured to specify
. Under this configuration,
ifcfg-eth0
configuration
file
. While an alias file allows multiple addresses for an existing
, may look similar to this:
eth0
directive is
USERCTL
and add the following line to
interface using the
eth0
ifcfg-eth0
file:
ifcfg-ppp0
Chapter 8. Network Interfaces
are
follow
DEVICE=eth0:0
eth0
should
follow
this
if it is not specified, users cannot bring this
no
ifcfg-eth0-user
/sbin/ifup eth0-user
and
ifcfg-eth0-user
ifcfg-ppp X
wvdial
the
this
naming
and a static
is bound to a dynamic IP
naming
convention,
:
command be-
are combined. While this
(where
is a unique
X
, the Network Adminis-
Need help?
Do you have a question about the ENTERPRISE LINUX 3 and is the answer not in the manual?