ANTlabs InnGate 3 E-series, Руководство администратора

Страница: 56 / 164

Connectivity Made Easy
Page 56 of 164
It is quite common for the User Provision Routed Scope to be configured as
set of public IP addresses although private addresses are also accepted.
Section 3.2.1.2 discusses the common scenarios where public IP addresses
may be needed by the LAN clients.
For clients without DHCP enabled or configured with a static IP, the
InnGate will not be able to assign a routed IP to it.
Figure 3-9 Routed IP addresses
Some applications such as VPN and video conferencing require that the clients
be assigned a public IP address and the User Provision Routed Scope with a
set of public IP addresses can be used to accommodate such scenarios:
1. Connecting to Virtual Private Networks – Often, clients on the
LAN may need to connect to a VPN server, for example, to access a
corporate enterprise network securely from a remote location. This is a
common requirement of business travelers or telecommuters.
Although quite uncommon, some VPN applications do not always work
with devices performing NAPT between the VPN server and the
connecting client. This is because the process of network address
translation modifies the IP header (and the TCP port) thus violating the
IPSec checksum integrity used by some VPN and the resulting packets
will be dropped by the VPN server.
As such, clients that need access to VPN services will need to select the
public IP option. Once the InnGate assigns a public IP address to the
client, packets sent by the client through the InnGate will not be