AMX NI-3100 Especificaciones Pagina 135

  • Descarga
  • Añadir a mis manuales
  • Imprimir
  • Pagina
    / 160
  • Tabla de contenidos
  • MARCADORES
  • Valorado. / 5. Basado en revisión del cliente
Vista de pagina 134
Appendix A: IPSec Configuration File
125
NetLinx Integrated Controllers- WebConsole & Programming Guide (FMv3)
Appendix A: IPSec Configuration File
IPSec Config file
The IPSec Configuration file contains user specified IPSec rule definitions to be applied to the running IPSec
database. The IPSec Configuration file is read at boot-up and the individual lines are applied to the IPSec
database. Configuration lines are applied to the database in the order that they appear in the configuration file.
Each line of the configuration file represents an individual rule. All lines follow the format:
<config action>=<config string>
All characters of a configuration line, both the action and the string, are case sensitive and white space is
relevant.
Lines beginning with a ‘#’ symbol are considered comments and are subsequently ignored during the loading
process.
All references to the Master’s IP address in configuration lines can be substituted by %LOCAL_ADDR% in
order to provide flexibility and reuse of an IPSec Config file. At boot, all occurrences of %LOCAL_ADDR%
will be replaced by the actual IP address of the Master. In this way, a single IPSec configuration file can be
uploaded to multiple Masters that are to be configured with the same IPSec configuration without having to
specify the Masters local IP Address directly.
The IPSec Configuration file is loaded onto the Master via the Master’s Web interface under Security->
IPSec Security Settings.
The following are the list of configuration lines supported by the AMX IPSec Configuration file.
Internet Key Exchange (IKE)
ikeAddPeerAuth
ikeAddPeerAuth
NAME ikeAddPeerAuth – add a peer's authentication information
SYNOPSIS
ikeAddPeerAuth=configString
DESCRIPTION This rule is used to specify IKE authentication information between the host and a peer.
This rule may be called multiple times to define a set of peers with which the host will conduct
IKE negotiations.
NOTE Specifying KEYPFS to this function will not enable perfect forward secrecy when negotiating
with the peer unless a DHGROUP is also specified in the Phase 2 attributes, set via
spdSetPropAttrib.
Rule Value
Rule Value = configString
A string formatted as follows:
peerIpAddress,interfaceIpAddress,proposalName,PFS,authenticationMethod,
authenticationInfo
where
- peerIpAddress is the address of the IKE peer.
- interfaceIpAddress is the local IP address that is to communicate with the peer.
- proposalName is an existing Phase 1 proposal name, defined via ikeSetProp.
- authenticationMethod is PSK (pre-shared key) or RSA (certificate support).
- authenticationInfo depends on authenticationMethod. See below.
When authenticationMethod is PSK, authenticationInfo is the pre-shared key, represented as
printable ASCII.
When authenticationMethod is RSA, authenticationInfo is a string formatted as follows:
localKey,localKeyPassword,localCertificate[,PEER_CERT,peerCertificate]
localKey - The filename where the local peer's key is stored.
localKeyPassword - The password for the local peer's key. Specify NOPASS if there is no
password. Note that the maximum password length is
MAX_PRIVATE_KEY_PASSWORD_LENGTH.
localKey - The filename where the local peer's key is stored.
Vista de pagina 134
1 2 ... 130 131 132 133 134 135 136 137 138 139 140 ... 159 160

Comentarios a estos manuales

Sin comentarios