For example, if ifcfg-eth0 and ifcfg-eth files are present, NetworkManager creates two connections, which will cause confusion. For more information on using this tool, see the Fedora Networking Guide.
Alias interface configuration files, which are used to bind multiple addresses to a single interface, use the ifcfg- if-name : alias-value naming scheme. Do not confuse alias ifcfg file and interface names with VLAN ifcfg file and interface names which take the form: ifcfg- if-name. Under this configuration, eth0 is bound to a dynamic IP address, but the same physical network card can receive requests via the fixed, Alias interfaces do not support DHCP.
A clone interface configuration file should use the following naming convention: ifcfg- if-name - clone-name. While an alias file allows multiple addresses for an existing interface, a clone file is used to specify additional options for an interface. To give users the ability to control the interface, create a clone by copying ifcfg-eth0 to ifcfg-eth0-user and add the following line to ifcfg-eth0-user :.
While this is a very basic example, this method can be used with a variety of options and interfaces. It is no longer possible to create alias and clone interface configuration files using a graphical tool.
However, as explained at the beginning of this section, it is no longer necessary to use this method as it is now possible to directly assign multiple IP address to the same interface. Dialup Interfaces. Red Hat Enterprise Linux allows administrators to bind multiple network interfaces together into a single channel using the bonding kernel module and a special network interface called a channel bonding interface.
Channel bonding enables two or more network interfaces to act as one, simultaneously increasing the bandwidth and providing redundancy. The contents of the file can be identical to whatever type of interface is getting bonded, such as an Ethernet interface. For more information about racoon , refer to the racoon and racoon. Red Hat Enterprise Linux allows administrators to bind multiple network interfaces together into a single channel using the bonding kernel module and a special network interface called a channel bonding interface.
Channel bonding enables two or more network interfaces to act as one, simultaneously increasing the bandwidth and providing redundancy. The contents of the file can be identical to whatever type of interface is getting bonded, such as an Ethernet interface. The configuration files for each of the channel-bonded interfaces can be nearly identical. For example, if two Ethernet interfaces are being channel bonded, both eth0 and eth1 may look like the following example:.
For a channel bonding interface to be valid, the kernel module must be loaded. Important aspects of the channel bonding interface are controlled through the kernel module. For more information about controlling the bonding modules, refer to Section Two lesser-used types of interface configuration files are alias and clone files. Under this configuration, eth0 is bound to a dynamic IP address, but the same physical network card can receive requests via the fixed, While an alias file allows multiple addresses for an existing interface, a clone file is used to specify additional options for an interface.
To give users the ability to control the interface, create a clone by copying ifcfg-eth0 to ifcfg-eth0-user and add the following line to ifcfg-eth0-user :. While this 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 information on using this tool, refer to Chapter 14, Network Configuration. If you are connecting to the Internet via a dialup connection, a configuration file is necessary for the interface. The PPP interface configuration file is created automatically when wvdial , the Network Administration Tool or Kppp is used to create a dialup account.
It is also possible to create and edit this file manually. SLIP files have interface configuration file names such as ifcfg-sl0. This option is primarily used in conjunction with SLIP interfaces. As a system administrator, you can configure a network interface manually, editing the ifcfg files. Interface configuration ifcfg 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 the suffix name refers to the name of the device that the configuration file controls.
0コメント