Chapter 3
Configuration via Local Pages
Trusted Network The Local and Remote Trusted Network parameters describe which terminals have access to the secure connection at the local and remote peers, respectively. Two fields must be completed for each peer: Trusted Network Type and Trusted Network IP. The Trusted Network Type determines which type of value to use for the Trusted
Network IP field.
The following network types are supported.
Type |
| IP | |
|
|
| |
Valid network types are: | Keyword: | Examples: | |
|
|
| |
a single IP address | address | 10.0.0.15 | |
|
|
| |
a single IP subnet | subnet | 10.0.0.0/24 | |
|
|
| |
a contiguous IP address | range | ||
range | |||
| |||
|
|
|
The Trusted Network IP values are used during the Phase 1 negotiations, and must comply with the values configured at the remote Security Gateway.
In the example above, it is assumed that all the hosts in the private (sub)networks communicate via the secure connection. The local and remote networks cover the complete LAN segments (10.0.0.0/24 and 20.0.0.0/24, respectively).
Protocol In this field you can optionally restrict the IPSec connection to a single protocol.
Valid entries are listed in the following table.
Protocol
ah | egp | esp |
|
|
|
ggp | gre | hmp |
|
|
|
icmp | igmp | pup |
|
|
|
rdp | rsvp | tcp |
|
|
|
udp | vines | |
|
|
|
6to4 |
|
|
|
|
|
Select any if you do not want to restrict the connection to a specific protocol.
If you want to restrict the protocols on your secure VPN link, and you need multiple protocols, then you define a new connection for every individual protocol. Separate IPSec tunnels will be established for each protocol.
48 | |
|
