# Define endpoints for VPN Gateway elements

Each endpoint is dedicated for one VPN Gateway element.

##

Any IP address that is already an endpoint for another VPN Gateway element is not shown on the Endpoints list for other Gateways that you create for the same Security Engine. Each VPN Gateway element can be used in several policy-based VPNs or Route-based Tunnels. However, you cannot use the same pair of local and remote endpoints in different VPN configurations for the same Security Engine.

For more details about the product and how to configure features, click Help or press F1.

## Steps

1. Select Engine.
2. Right-click the Engine, then select Edit Single Engine or Edit Engine Cluster.
3. Browse to VPN > Endpoints.
4. (Optional) Change the selection of IP addresses that you want to use as endpoints in VPNs.
   - Typically, these are IP addresses that belong to interfaces toward the Internet, which are automatically selected based on the engine’s default routing table.
   - If loopback IP addresses are defined for the Security Engine, you can select a loopback IP address as the endpoint IP address. On clustered engines, the IP addresses are CVIs.
   - (Optional) If you have more than one Internet connection, select an IP address from each ISP.
5. Double-click the endpoint, then configure the following optional settings according to your environment.
   1. (Optional) In the Name field, enter a descriptive name for the endpoint.
   2. (Multi-Link tunnels only) From the Connection Type drop-down list, select the Connection Type element that defines how the endpoint is used in a Multi-Link configuration.
      You can override these settings in each individual VPN.
   3. (Optional) From the Use NAT-T drop-down list, select an option to activate encapsulation for NAT traversal in site-to-site VPNs.
      You might need NAT traversal to traverse a NAT device at the local or at the remote gateway end. The gateway always allows VPN clients to use NAT-T regardless of these settings. NAT-T always uses the standard UDP port 4500.
      Note: If a private external IP address is translated to a public IP address by an external NAT device, make sure that Contact Addresses and Locations are defined for the Engine.
6. In the Phase-1 ID settings, select an option from the ID Type drop-down list according to your environment.
   The ID identifies the Gateways during the IKE SA negotiations.
7. In the ID Value field, enter an ID value according to the selected ID type.
   - If you selected DNS Name, enter a DNS name.
   - If you selected Email, enter an email address.
   - If you selected Distinguished Name, enter the distinguished name that is used in the gateway certificate.
   - If you selected IP Address and the endpoint has a static IP address, the value is filled in automatically. If the endpoint has a dynamic IP address, you must manually enter an IP address.
8. (Optional) If the endpoint must use different Phase-1 ID settings in individual policy-based VPNs, add VPN-specific exceptions.
   1. Click Exceptions.
   2. Click Add, then select the type of ID from the drop-down list.
   3. Select a Policy-Based VPN element, then click Select.
   4. In the ID Value cell, enter the value of the ID.
   5. Click OK.
9. (Optional) In the VPN Type settings, restrict the types of VPNs that the endpoint can be used in.
   1. Select Selected types only.
   2. Select one or more types of VPNs.
10. Click OK to save your changes to the endpoint.
11. Save the changes.
    - To save the changes, click Save.
    - To save the changes and refresh the security policy on the engine, click Save and Refresh.

## Engine Editor > VPN > Endpoints

Use this branch to change the endpoint settings that are used when the Security Engine acts as a VPN gateway.

Option | Definition
--- | ---
Enabled | When selected, the endpoint IP address is active.
Name | Shows the name of the endpoint. If the endpoint does not have a descriptive name, the IP address of the endpoint is shown.
IP Address | Shows the IP address of the endpoint.
Connection Type | Defines how the endpoint is used in a Multi-Link configuration.
Options | Shows the optional settings that have been selected for the endpoint.
Phase-1 ID | Shows the value of the phase-1 ID that identifies the gateway during the IKE phase-1 negotiations.
VPN Type | Shows the types of VPNs that the endpoint can be used in.
Edit | Allows you to change the properties of the selected endpoint.

## Endpoint Properties dialog box

Use this dialog box to define the properties of internal endpoints.

Option | Definition
--- | ---
Name | The name of the endpoint. If no name is entered, the IP address is used.
IP Address | The IP address of the endpoint.
Dynamic | Automatically selected if the endpoint has a dynamic IP address.
Connection Type | Defines how the endpoint is used in a Multi-Link configuration.
NAT-T | Detects when an IPsec VPN tunnel goes through a NAT device. If NAT is detected, the VPN automatically uses UDP port 4500 for IKE negotiation messages, and encapsulates ESP packets in UDP packets that use port 4500. Disabled — NAT traversal is disabled. Enabled — Select this option to allow encapsulating the IPsec communications in standard NAT-T UDP packets in site-to-site VPNs when the gateways detect that a NAT operation is applied to the communications. If both gateways do not support this option, the option is ignored. Forced — Select this option to force NAT-T even when the gateways do not detect a NAT operation being applied to the communications. If both gateways do not support this option, the VPN fails to establish.
Contact Addresses section | This section cannot be edited. The contact addresses for endpoints are defined in the Interface properties.
Default | Used by default whenever a component that belongs to another Location connects to this interface.
Dynamic | Used when the endpoint has a dynamic IP address. Note: Dynamic contact addresses are not supported on SSID Interfaces.
Exceptions | Opens the Exceptions dialog box.
Phase-1 ID section
ID Type | Identifies the Gateways during the IKE phase-1 negotiations. DNS Name — A DNS name identifies the gateway. E-mail — An email address identifies the gateway. Distinguished Name — The Distinguished Name (DN) field in the gateway's certificate identifies the gateway. You can only add one DN value for each VPN Gateway. IP Address — An IP address identifies the gateway. If the endpoint has a static IP address, the value is filled in automatically. If the endpoint has a dynamic IP address, you must manually enter an IP address. To add VPN-specific exceptions for the Phase-1 ID, click Exceptions.
Exceptions | Allows you to create VPN-specific exceptions if the endpoint must use different Phase-1 ID settings in individual policy-based VPNs.
ID Value | Specifies the details of the ID Type.
VPN Type section
All types | Restricts the types of VPNs that the endpoint can be used in.
Selected types only | Select one or more options. IPsec VPN — The endpoint can be used in IPsec tunnels. SSL VPN Tunnel — The endpoint can be used in SSL VPN tunnels. Application Access Portal — The endpoint can be used to access the Application Access Portal. Note: The endpoint must have an IPv4 address if you want to use it in SSL VPN tunnels or to access the Application Access Portal.

## Connection Type Properties dialog box

Use this dialog box to create and edit Connection Type elements that define which endpoints can communicate with each other, and how endpoints are used in a Multi-Link configuration.

Option | Definition
--- | ---
Name | The name of the element.
Link Type | Identifies the type of ISP connection.
Mode | Defines how the endpoint is used in a Multi-Link configuration. Active — The link is always used. If there are multiple links in Active mode between the Gateways, the VPN traffic is load-balanced between the links based on the load of the links. VPN traffic is directed to the link that has the lowest load. Aggregate — The link is always used, and each VPN connection is load-balanced in round-robin fashion between all the links that are in Aggregate mode. For example, if there are two links in Aggregate mode, a new VPN connection is directed to both links. Standby — The link is used only when all Active or Aggregate mode links are unusable.
Connectivity Group | The connectivity group to which the endpoint belongs. Tunnels are created only between endpoints that belong to the same connectivity group.
Category (Optional) | Includes the element in predefined categories. Click Select to select a category.
Comment (Optional) | A comment for your own reference.

## Exceptions dialog box (VPN endpoints)

Use this dialog box to add VPN-specific exceptions for the phase-1 ID in policy-based VPNs.

Option | Definition
--- | ---
VPN | Shows the VPN to which the exception applies.
ID Type | Shows the phase-1 ID type used in the exception. Distinguished Name — The Distinguished Name field in the gateway's certificate identifies the gateway. DNS Name — A DNS name identifies the gateway. E-mail — An email address identifies the gateway. IP Address — An IP address identifies the gateway. If the endpoint has a static IP address, the value is filled in automatically. If the endpoint has a dynamic IP address, you must manually enter an IP address.
ID Value | Specifies the value of the phase-1 ID used in the exception.
Add | Adds a phase-1 ID of the selected type and opens the Select VPN dialog box.
Remove | Removes the selected row from the table.