Proroute GEM420 4G M2M Router
GEM420 User Manual
125
3. Full Tunnel:
All traffic from Intranet of Business Security Gateway goes over the
IPSec VPN tunnel if these packets don’t match the Remote Subnet of other
IPSec tunnels. That is, both application data and Internet access packets land
up at the VPN concentrator.
4.
Remote subnet:
The subnet of LAN site of remote Business Security Gateway.
It can be a host, a partial subnet, the whole subnet or multiple subnets of LAN
site of remote gateway. Since the device supports VPN hub and spoke function,
there are 5 remote subnets to be defined here and any packets want to these 5
remote subnets will be transferred via this VPN tunnel.
5.
Remote Netmask:
The remote netmask and associated remote subnet IP can
define a subnet domain for the remote devices connected via the VPN tunnel.
There are 5 remote subnet domains to be defined here for hub and spoke
function.
6.
Remote Gateway:
Enter the IP address or FQDN of remote Business Security
Gateway.
3.2.3.1.6 Authentication
1.
Key Management:
Select “IKE+Pre-shared Key” or “Manually”. Other options
depend on product models. By default, “IKE+Pre-shared Key” method is
adopted for key management. It is the first key used in IKE phase for both VPN
tunnel initiator and responder to negotiate further security keys to be used in
IPSec phase. The pre-shared key must be the same for both VPN tunnel initiator
and responder. When “Manually” key management is adopted, the Pre-shared is
not necessary.
2.
Local ID:
The Type and the Value of the local Business Security Gateway must
be the same as that of the Remote ID of the remote VPN peer. There are 4 types
for Local ID: User Name, FQDN, User@FQDN and Key ID.
3.
Remote ID:
The Type and the Value of the local Business Security Gateway
must be the same as that of the local ID of the remote VPN peer. There are also
4 types for Remote ID: User Name, FQDN, User@FQDN and Key ID.
3.2.3.1.7 IKE Phase
