Table 58 Telecommuters Using Unique VPN Rules Example
TELECOMMUTERS | HEADQUARTERS |
|
|
Telecommuter C (telecommuterc.dydns.org) | Headquarters ZyXEL Device Rule 3: |
|
|
Local ID Type: | Peer ID Type: |
|
|
Local ID Content: myVPN@myplace.com | Peer ID Content: myVPN@myplace.com |
|
|
Local IP Address: 192.168.4.15 | Remote Gateway Address: |
| telecommuterc.dydns.org |
|
|
| Remote Address 192.168.4.15 |
|
|
13.11 VPN and Remote Management
You can allow someone to use a service (like Telnet or HTTP) through a VPN tunnel to manage the ZyXEL Device. One of the ZyXEL Device’s ports must be part of the VPN rule’s local network. This can be the ZyXEL Device’s LAN port if you do not want to allow remote management on the WAN port. You also have to configure remote management (REMOTE MGMT) to allow management access for the service through the specific port.
In the following example, the VPN rule’s local network (A) includes the ZyXEL Device’s LAN IP address of 192.168.1.7. Someone in the remote network (B) can use a service (like HTTP for example) through the VPN tunnel to access the ZyXEL Device’s LAN interface.
Remote management must also be configured to allow HTTP access on the ZyXEL Device’s LAN interface.
Figure 99 VPN for Remote Management Example
168 | Chapter 13 IPSec VPN |