User's Manual

Table Of Contents
Fortress ES-Series CLI Guide: Network Security, Authentication and Auditing
137
Action: Apply Peer Address: 0.0.0.0
...can replace the multiple SPD entries that would need to be
configured with static IP addresses for multiple VPN clients
connecting from the 192.168.10.0/255.255.255.0 subnet:
policy name: clientFT-1
Priority: 1 Interface: lan7
Local: 0.0.0.0/0.0.0.0
Remote: 192.168.10.101/255.255.255.255
Action: Apply Peer Address: 10.1.101.1
policy name: clientFT-2
Priority: 2 Interface: lan7
Local: 0.0.0.0/0.0.0.0
Remote: 192.168.10.102/255.255.255.255
Action: Apply Peer Address: 10.1.102.1
...etc.
In a second example, the same IPsec peers in the above
statically configured set could be permitted access by an SPD
rule triggered by incoming traffic from
any subnet:
policy name: dynmc-clientsFT-all
Priority: 50 Interface: lan7
Local: 0.0.0.0/0.0.0.0
Remote: 0.0.0.0/0.0.0.0
Action: Apply Peer Address: 0.0.0.0
Note that the rule in the second example (above) selects all
traffic to and from any subnet connected to the interface:
Local : 0.0.0.0/0.0.0.0
Remote: 0.0.0.0/0.0.0.0
A dynamic SPD rule configured in this way will preempt any
SPD entry subsequent to it in priority order and permit access
on the associated interface to any successfully authenticated
connecting client.
for partner Mesh Points
IPsec dynamic endpoint functionality can also be triggered by a
32-bit SPD rule configured on an IPsec SA partner Mesh Point,
most typically an ES210 Mesh Point.
For example, if an ES210 Mesh Point with the public IP
address 4.1.1.50 and private IP address 10.10.10.46 is
configured with this SPD entry:
Policy Name:
Client46
Priority:
11
Interface:
eth2
Local:
10.10.10.46/255.255.255.255
Remote:
10.0.0.0/255.0.0.0
Action:
Apply
Peer Address: 192.168.42.35