Channel Bonding Interfaces - Red Hat ENTERPRISE LINUX 4.5.0 Reference Manual

Chapter 8. Network Interfaces
(preshared keys) method.
•
IKE_CERTFILE=<cert-file>
•
IKE_PEER_CERTFILE=<cert-file>
remote host.
•
IKE_DNSSEC=<answer>
host's X.509 certificate via DNS. If a
parameter.
For more information about the encryption algorithms available for IPsec, refer to the
man page. For more information about
pages.

2.3. Channel Bonding Interfaces

Red Hat Enterprise Linux allows administrators to bind multiple network interfaces together into
a single channel using the
channel bonding interface. Channel bonding enables two or more network interfaces to act as
one, simultaneously increasing the bandwidth and providing redundancy.
To create a channel bonding interface, create a file in the
directory called
ifcfg-bond<N>
The contents of the file can be identical to whatever type of interface that is getting bonded,
such as an Ethernet interface. The only difference is that the
, replacing
bond<N> <N>
The following is a sample channel bonding configuration file:
DEVICE=bond0 BOOTPROTO=none ONBOOT=yes NETWORK=10.0.1.0
NETMASK=255.255.255.0 IPADDR=10.0.1.27 USERCTL=no
After the channel bonding interface is created, the network interfaces to be bound together must
be configured by adding the
configuration files for each of the channel bonded interfaces can be nearly identical.
For example, if channel bonding two Ethernet interfaces, both
following example:
DEVICE=eth<N> BOOTPROTO=none ONBOOT=yes MASTER=bond0 SLAVE=yes USERCTL=no
In this example, replace
For a channel bonding interface to be valid, the kernel module must be loaded. To insure that
the module is loaded when the channel bonding interface is brought up, add the following line to
/etc/modprobe.conf
124
, where
<cert-file>
, where
, where
<answer>
IKE_PEER_CERTFILE
racoon
kernel module and a special network interface called a
bonding
, replacing
<N>
with the number for the interface.
and
MASTER= SLAVE=
with the numerical value for the interface.
<N>
:
is a valid X.509 certificate file for the host.
is a valid X.509 certificate file for the
<cert-file>
is . The daemon retrieves the remote
yes racoon
is specified, do not include this
, refer to the
racoon
/etc/sysconfig/network-scripts/
with the number for the interface, such as
DEVICE=
directives to their configuration files. The
eth0
setkey
and man
racoon.conf
0
directive must be
and may look like the
eth1
.