Ipsec Interfaces - Red Hat ENTERPRISE LINUX 4.5.0 Reference Manual

Table of Contents

Advertisement

Chapter 8. Network Interfaces
in conjunction with
HWADDR
MASTER=<bond-interface>
which the interface the Ethernet interface is linked.
This directive is used in conjunction with the
Refer to
Section 2.3, "Channel Bonding Interfaces"
interfaces.
, where
NETMASK=<mask>
NETWORK=<address>
as the value is calculated automatically with
, where
ONBOOT=<answer>
— This device should be activated at boot-time.
yes
— This device should not be activated at boot-time.
no
, where
PEERDNS=<answer>
— Modify
yes
/etc/resolv.conf
default.
— Do not modify
no
SLAVE=<bond-interface>
— This device is controlled by the channel bonding interface specified in the
yes
directive.
— This device is not controlled by the channel bonding interface specified in the
no
directive.
This directive is used in conjunction with the
Refer to
Section 2.3, "Channel Bonding Interfaces"
SRCADDR=<address>
packets.
, where
USERCTL=<answer>
— Non-root users are allowed to control this device.
yes
— Non-root users are not allowed to control this device.
no

2.2. IPsec Interfaces

With Red Hat Enterprise Linux it is possible to connect to other hosts or networks using a
122
.
,where
<bond-interface>
is the netmask value.
<mask>
, where
is the network address. This directive is deprecated,
<address>
is one of the following:
<answer>
is one of the following:
<answer>
if the DNS directive is set. If using DHCP, then
.
/etc/resolv.conf
,where
<bond-interface>
, where
is the specified source IP address for outgoing
<address>
is one of the following:
<answer>
is the channel bonding interface to
directive.
SLAVE
for more about channel bonding
.
ifcalc
is one of the following:
directive.
MASTER
for more about channel bond interfaces.
is the
yes
MASTER
MASTER

Advertisement

Table of Contents
loading

Table of Contents