Options of Configuring IKE VPN

The options in the IKE VPN Configuration dialog are described below:

Step 1: Peer

Configuring a peer is divided into two parts: basic configuration and advanced configuration. Options are described as follows:

Basic

Peer name: Specifies or displays the name of the ISAKMP gateway. To import a configured ISAKMP gateway or create a new ISAKMP gateway, click Import or New.

Interface: Specifies the interface bound to the ISAKMP gateway.

Mode: Specifies the mode of IKE negotiation. There are two IKE negotiation modes: Main and Aggressive. The main mode is the default mode. The aggressive mode cannot protect identity. You have no choice but to use the aggressive mode in the situation that the IP address of the center device is static and the IP address of client device is dynamic.

Type: Specifies the type of the peer IP. If the peer IP is static, type the IP address into the Peer Address box; if the peer IP type is user group, select the AAA server you need from the AAA server drop-down list.

Local ID: Specifies the local ID. System supports three types of ID: FQDN, U-FQDN and Asn1dn (only for license). Click the ID type you want, and then type the content for this ID into the Local ID value box.

Peer ID: Specifies the peer ID. System supports three types of ID: FQDN, U-FQDN and Asn1dn (only for license). Click the ID type you want and then type the content for this ID into the Peer ID value box. If Radius server is used for authentication, you should select the Wildcard check box.

Proposal 1: Specifies a P1 proposal for ISAKMP gateway.To add more P1 proposals, click . You can specify up to 4 P1 proposals.

Pre-shared key: If you choose to use pre-shared key for authentication, type the key into the box.

Trust domain: If you choose to use digital certificate for authentication, select a trust domain.

User key: Click Generate. In the Generate user key dialog, type the IKE ID into the IKE ID box, and then click Generate. The generated user key will be displayed in the Generate result box. The PnPVPN client uses this key as the password to authenticate the login users.

Advanced: Click the Advance tab. Options are described as follows:

Connection type: Specifies the connection type for ISAKMP gateway:

NAT transversal: This option must be enabled when there is a NAT device in the IPSec or IKE tunnel and the device implements NAT. By default, this function is disabled.

Generate route: Select the check box to enable the auto routing function. By default, this function is disabled. This function allows the device to automatically add routing entries which are from the center device to the branch, avoiding the problems caused by manually configured routing.

DPD: Click this option button to enable the DPD (Delegated Path Discovery) function. By default, this function is disabled. When DPD is enabled, the responder will initiate a DPD request to the peer to test if the ISAKMP gateway exists on condition that it cannot receive the peer's packets for a long period.

Description: Type the description for the ISAKMP gateway.

Step 2: Tunnel

Configuring a tunnel is divided into two parts: basic settings and advanced settings. Options are described as follows:

Basic

Name: Type a name for the tunnel.

Mode: Specifies the mode, including tunnel mode and transport mode.

P2 proposal: Specifies the P2 proposal for tunnel.

Proxy ID: Specifies ID of Phase 2 for the tunnel which can be Auto or Manual.

Advanced: Click the Advanced tab. Options are described as follows:

DNS1: Specifies the IP address of the DNS server allocated to the client by the PnPVPN server. To add more DNS servers, click . You can define one primary DNS server and three backup DNS servers.

WINS1: Specifies the IP address of WINS server allocated to the client by the PnPVPN server. To add more WINS servers, click . You can define one primary WINS server and one backup WINS server.

Idle time: Select the check box to enable the idle time function. By default, this function is disabled. This time length is the longest time the tunnel can exist without traffic passing through. When the time is over, SA will be cleared.

DF-Bit: Select the check box to allow the forwarding device execute IP packet fragmentation. The options are:

Anti-replay: Anti-replay is used to prevent hackers from attacking the device by resending the sniffed packets, i.e., the receiver rejects the obsolete or repeated packets. By default, this function is disabled.

Note: When the network condition is poor, choose a larger window.

Commit bit: Select the Enable check box to make the corresponding party configure the commit bit function, which can avoid packet loss and time difference. However, commit bit may slow the responding speed.

Auto connect: Select the Enable check box to enable the auto connection funciton. By default, this function is disabled. The device has two methods of establishing SA: auto and traffic intrigued. When it is auto, the device checks SA status every 60 seconds and initiates negotiation request when SA is not established; when it is traffic intrigued, the tunnel sends negotiation request only when there is traffic passing through the tunnel. By default, traffic intrigued mode is used.

Note: Auto connection works only when the peer IP is static and the local device is initiator.

Tunnel route: Click More. In the Tunnel Route Configuration dialog, add one or more tunnel routes. You can add up to 128 tunnel routes.

Description: Type the description for the tunnel.