User's Manual

Table Of Contents
Fortress ES-Series CLI Guide: Network Security, Authentication and Auditing
138
The Mesh Point at the other end of the IPsec SA would
transparently and dynamically expand the SPD rule in the
example for
dynamic client IP addresses, above, into:
Policy Name:
VPPNclients
Priority:
94
Interface:
eth2
Local:
10.0.0.0/255.0.0.0
Remote: 10.10.10.46/255.255.255.255
Action:
Apply
Peer Address: 4.1.1.50
Policy Name:
VPPNclients
Priority:
94
Interface:
eth2
Local:
10.0.0.0/255.0.0.0
Remote:
0.0.0.0/0.0.0.0
Action:
Apply
Peer Address:
0.0.0.0
Once dynamic peers are established, view them with show
spd
:
# show spd -dynamicpeers
Priority: 90, policy name: Dynamo
Local: 0.0.0.0/0.0.0.0, Remote: 0.0.0.0/0.0.0.0
Interface: DM, Action: apply, peer address: 0.0.0.0
Dynamic Peers:
10.14.150.211
10.14.150.212
10.14.150.213
10.14.150.214
10.14.150.215
10.14.150.216
1 SPD entry registered
6 Dynamic peers registered
4.4.4 IPsec Pre-Shared Keys
As an alternative to using a digital certificate, the identity a
given IPsec peer can be authenticated by a static pre-shared
key (PSK), as configured on both parties to the initial ISAKMP
transaction.
PSKs on the Mesh Point can be specified as a string of ASCII
characters or a series of hex bytes (hexadecimal pairs).
Alternatively, you can generate a random key of a specified
length.
To configure a PSK for an IPsec peer manually:
# set ipsec-psk -peer
<peer>
-ascii
<keystring>
|-hex
<hexdigitstring>
Specify the IP address of the IPsec peer to be authenticated by
the PSK, then specify and enter either an
-ascii
string or a
series of
-hex
bytes.
To automatically generate a PSK for an IPsec peer:
# set ipsec-psk -peer
<peerIPaddr>
-generate -length
<length>