ZyWALL 2 Series User’s Guide
FIELDS | TELECOMMUTERS |
| HEADQUARTERS |
|
|
| |
My IP Address: | 0.0.0.0 (dynamic IP address | Public static IP address | |
| assigned by the ISP) |
|
|
|
|
|
|
Secure Gateway | Public static IP address | 0.0.0.0 | With this IP address only the |
IP Address: |
| telecommuter can initiate the IPSec tunnel. | |
Local IP Address: | Telecommuter A: 192.168.2.12 | 192.168.1.10 | |
| Telecommuter B: 192.168.3.2 |
|
|
| Telecommuter C: 192.168.4.15 |
|
|
Remote IP | 192.168.1.10 | 0.0.0.0 (N/A) | |
Address: |
|
|
|
|
|
|
|
14.18.2Telecommuters Using Unique VPN Rules Example
In this example the telecommuters (A, B and C in the figure) use IPSec routers with domain names that are mapped to their dynamic WAN IP addresses (use Dynamic DNS to do this).
With aggressive negotiation mode (see section 14.12.1), the ZyWALL can use the ID types and contents to distinguish between VPN rules. Telecommuters can each use a separate VPN rule to simultaneously access a ZyWALL at headquarters. They can use different IPSec parameters. The local IP addresses (or ranges of addresses) of the rules configured on the ZyWALL at headquarters can overlap. The local IP addresses of the rules configured on the telecommuters’ IPSec routers should not overlap.
VPN Screens |