User`s guide

Chapter 10 IPSec VPN Config Screens
LAN-Cell 2 User’s Guide
238
10.8 VPN and Remote Management
You can allow someone to use a service (like Telnet or HTTP) through a VPN tunnel to
manage the LAN-Cell. One of the LAN-Cell’s ports must be part of the VPN rule’s local
network. This can be the LAN-Cell’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 (see Chapter 15
on page 319).
In the following example, the VPN rule’s local network (A) includes the LAN-Cell’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 LAN-Cell’s LAN interface. Remote
management must also be configured to allow HTTP access on the LAN-Cell’s LAN
interface.
Figure 143 VPN for Remote Management Example
10.9 Hub-and-spoke VPN
Hub-and-spoke VPN connects VPN tunnels to form one secure network.
Local ID Type: DNS Peer ID Type: DNS
Local ID Content: UserB.com Peer ID Content: UserB.com
Local IP Address: 192.168.3.2 Remote Gateway Address: UserB.dydns.org
Remote Address 192.168.3.2
User C (UserC.dydns.org) Headquarters LAN-Cell Rule 3:
Local ID Type: E-mail Peer ID Type: E-mail
Local ID Content: [e-mail] Peer ID Content: [e-mail]
Local IP Address: 192.168.4.15 Remote Gateway Address: UserC.dydns.org
Remote Address 192.168.4.15
Table 86 Mobile Users Using Unique VPN Rules Example
MOBILE USERS HEADQUARTERS