Ethernet Interfaces
One of the most common interface files is ifcfg-eth0
, which controls the first Ethernet network interface card or NIC in the system. In a system with multiple NICs, there are multiple ifcfg-eth
files (where <X>
<X>
is a unique number corresponding to a specific interface). Because each device has its own configuration file, an administrator can control how each interface functions individually.
The following is a sample ifcfg-eth0
file for a system using a fixed IP address:
DEVICE=eth0 BOOTPROTO=none ONBOOT=yes NETWORK=10.0.1.0 NETMASK=255.255.255.0 IPADDR=10.0.1.27 USERCTL=no
The values required in an interface configuration file can change based on other values. For example, the ifcfg-eth0
file for an interface using DHCP looks different because IP information is provided by the DHCP server:
DEVICE=eth0 BOOTPROTO=dhcp ONBOOT=yes
The Network Administration Tool (system-config-network
) is an easy way to make changes to the various network interface configuration files (refer to Network Configuration for detailed instructions on using this tool).
However, it is also possible to manually edit the configuration files for a given network interface.
Below is a listing of the configurable parameters in an Ethernet interface configuration file:
BONDING_OPTS=
<parameters>
-
sets the configuration parameters for the bonding device, and is used in
/etc/sysconfig/network-scripts/ifcfg-bond
(see "Channel Bonding Interfaces"). These parameters are identical to those used for bonding devices in<N>
/sys/class/net/
, and the module parameters for the bonding driver as described in<bonding device>
/bondingbonding
Module Directives.
This configuration method is used so that multiple bonding devices can have different configurations. If you use BONDING_OPTS
in ifcfg-
, do not use <name>
/etc/modprobe.conf
to specify options for the bonding device.
BOOTPROTO=
<protocol>
-
where
is one of the following:<protocol>
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
is the broadcast address. This directive is deprecated, as the value is calculated automatically with<address>
ipcalc
. DEVICE=
<name>
-
where
is the name of the physical device (except for dynamically-allocated PPP devices where it is the logical name).<name>
DHCP_HOSTNAME=
<name>
-
where
is a short hostname to be sent to the DHCP server. Use this option only if the DHCP server requires the client to specify a hostname before receiving an IP address.<name>
DNS
{1,2}
=<address>
-
where
is a name server address to be placed in<address>
/etc/resolv.conf
if thePEERDNS
directive is set toyes
. ETHTOOL_OPTS=
<options>
-
where
are any device-specific options supported by<options>
ethtool
. For example, if you wanted to force 100Mb, full duplex:ETHTOOL_OPTS="autoneg off speed 100 duplex full"
Instead of a custom initscript, use
ETHTOOL_OPTS
to set the interface speed and duplex settings. Custom initscripts run outside of the network init script lead to unpredictable results during a post-boot network service restart.Changing speed or duplex settings almost always requires disabling autonegotiation with the
autoneg off
option. This needs to be stated first, as the option entries are order-dependent. GATEWAY=
<address>
-
where
<address>
is the IP address of the network router or gateway device (if any). HOTPLUG=
<answer>
-
where
<answer>
is one of the following:yes
- This device should be activated when it is hot-plugged (this is the default option).
no
- This device should not be activated when it is hot-plugged.
The
HOTPLUG=no
option can be used to prevent a channel bonding interface from being activated when a bonding kernel module is loaded.Refer to "Channel Bonding Interfaces" for more about channel bonding interfaces.
HWADDR=
<MAC-address>
-
where
<MAC-address>
is the hardware address of the Ethernet device in the formAA:BB:CC:DD:EE:FF
. This directive must be used in machines containing more than one NIC to ensure that the interfaces are assigned the correct device names regardless of the configured load order for each NIC's module. This directive should not be used in conjunction withMACADDR
. IPADDR=
<address>
-
where
is the IP address.<address>
LINKDELAY=
<time>
-
where
<time>
is the number of seconds to wait for link negotiation before configuring the device. MACADDR=
<MAC-address>
-
where
<MAC-address>
is the hardware address of the Ethernet device in the formAA:BB:CC:DD:EE:FF
. This directive is used to assign a MAC address to an interface, overriding the one assigned to the physical NIC. This directive should not be used in conjunction withHWADDR
. MASTER=
<bond-interface>
-
where
is the channel bonding interface to which the Ethernet interface is linked.<bond-interface>
This directive is used in conjunction with the
SLAVE
directive.Refer to "Channel Bonding Interfaces" for more information about channel bonding interfaces.
NETMASK=
<mask>
-
where
is the netmask value.<mask>
NETWORK=
<address>
-
where
is the network address. This directive is deprecated, as the value is calculated automatically with<address>
ipcalc
. ONBOOT=
<answer>
-
where
is one of the following:<answer>
yes
- This device should be activated at boot-time.
no
- This device should not be activated at boot-time.
PEERDNS=
<answer>
-
where
is one of the following:<answer>
yes
- Modify/etc/resolv.conf
if the DNS directive is set. If using DHCP, thenyes
is the default.
no
- Do not modify/etc/resolv.conf
.
SLAVE=
<answer>
-
where
is one of the following:<answer>
yes
- This device is controlled by the channel bonding interface specified in theMASTER
directive.
no
- This device is not controlled by the channel bonding interface specified in theMASTER
directive.
This directive is used in conjunction with the
MASTER
directive.Refer to "Channel Bonding Interfaces" for more about channel bonding interfaces.
SRCADDR=
<address>
-
where
is the specified source IP address for outgoing packets.<address>
USERCTL=
<answer>
-
where
is one of the following:<answer>
yes
- Non-root users are allowed to control this device.
no
- Non-root users are not allowed to control this device.