6.2. Interface Configuration Files
Interface configuration files control the software interfaces for individual network devices. As the system boots, it uses these files to determine what interfaces to bring up and how to configure them. These files are usually named
ifcfg-name , where
name refers to the name of the device that the configuration file controls.
6.2.1. 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-ethX files (where
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 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.
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:
-
sets the configuration parameters for the bonding device, and is used in
/etc/sysconfig/network-scripts/ifcfg-bond(see Section 6.2.2, “Channel Bonding Interfaces”). These parameters are identical to those used for bonding devices inN/sys/class/net/, and the module parameters for the bonding driver as described inbonding device/bondingbondingModule Directives.This configuration method is used so that multiple bonding devices can have different configurations. It is highly recommended to place all of your bonding options after theBONDING_OPTSdirective inifcfg-. Do not specify options for the bonding device inname/etc/modprobe.d/, or in the deprecatedbonding.conf/etc/modprobe.conffile. -
where
protocol-
none— No boot-time protocol should be used. -
bootp— The BOOTP protocol should be used. -
dhcp— The DHCP protocol should be used.
-
-
where
addressipcalc. -
where
name -
where
nameis 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. -
where
address/etc/resolv.confif thePEERDNSdirective is set toyes. -
where
optionsethtool. For example, if you wanted to force 100Mb, full duplex:ETHTOOL_OPTS="autoneg off speed 100 duplex full"Instead of a custom initscript, useETHTOOL_OPTSto 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.Set "autoneg off" before changing speed or duplex settings
Changing speed or duplex settings almost always requires disabling autonegotiation with theautoneg offoption. This needs to be stated first, as the option entries are order-dependent. -
where
addressis the IP address of the network router or gateway device (if any). -
where
answeris 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.
TheHOTPLUG=nooption can be used to prevent a channel bonding interface from being activated when a bonding kernel module is loaded.Refer to Section 6.2.2, “Channel Bonding Interfaces” for more information about channel bonding interfaces. -
-
where
MAC-addressis 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. -
where
address -
where
timeis the number of seconds to wait for link negotiation before configuring the device. -
where
MAC-addressis 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. -
where
bond-interfaceThis directive is used in conjunction with theSLAVEdirective.Refer to Section 6.2.2, “Channel Bonding Interfaces” for more information about channel bonding interfaces. -
where
mask -
where
addressipcalc. -
where
answer-
yes— This device should be activated at boot-time. -
no— This device should not be activated at boot-time.
-
-
where
answer-
yes— Modify/etc/resolv.confif the DNS directive is set. If using DHCP, thenyesis the default. -
no— Do not modify/etc/resolv.conf.
-
-
where
answer-
yes— This device is controlled by the channel bonding interface specified in theMASTERdirective. -
no— This device is not controlled by the channel bonding interface specified in theMASTERdirective.
This directive is used in conjunction with theMASTERdirective.Refer to Section 6.2.2, “Channel Bonding Interfaces” for more about channel bonding interfaces. -
-
where
address -
where
answer-
yes— Non-rootusers are allowed to control this device. -
no— Non-rootusers are not allowed to control this device.
-
BONDING_OPTS=parameters
BOOTPROTO=protocol
BROADCAST=address
DEVICE=name
DHCP_HOSTNAME=name
DNS{1,2}=address
ETHTOOL_OPTS=options
GATEWAY=address
HOTPLUG=answer
HWADDR=MAC-address
IPADDR=address
LINKDELAY=time
MACADDR=MAC-address
MASTER=bond-interface
NETMASK=mask
NETWORK=address
ONBOOT=answer
PEERDNS=answer
SLAVE=answer
SRCADDR=address
USERCTL=answer
扫一扫
3777
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
