Set Up an IKE Gateway
To set up a VPN tunnel, the VPN peers or gateways must authenticate each other using preshared keys or digital certificates and establish a secure channel in which to negotiate the IPSec security association (SA) that will be used to secure traffic between the hosts on each side.
- Define the IKE Gateway.
- Select, clickNetworkNetwork ProfilesIKE GatewaysAdd, and on theGeneraltab, enter theNameof the gateway.
- ForVersion, selectIKEv1 only mode,IKEv2 only mode, orIKEv2 preferred mode. The IKE gateway begins its negotiation with its peer in the mode specified here. If you selectIKEv2 preferred mode, the two peers will use IKEv2 if the remote peer supports it; otherwise they will use IKEv1.(TheVersionselection also determines which options are available on theAdvanced Optionstab.)
- Establish the local endpoint of the tunnel (gateway).
- ForAddress Type, clickIPv4orIPv6.
- Select the physical, outgoingInterfaceon the firewall where the local gateway resides.
- From theLocal IP Addressdrop-down, select the IP address that will be used as the endpoint for the VPN connection. This is the external-facing interface with a publicly routable IP address on the firewall.
- Establish the peer at the far end of the tunnel (gateway).
- Select thePeer IP Typeto be aStaticorDynamicaddress assignment.
- If thePeer IP Addressis static, enter the IP address of the peer.
- Specify how the peer is authenticated.
- Configure a pre-shared key.
- Enter aPre-shared Key, which is the security key to use for authentication across the tunnel. Re-enter the value toConfirm Pre-shared Key. Use a maximum of 255 ASCII or non-ASCII characters.Generate a key that is difficult to crack with dictionary attacks; use a pre-shared key generator, if necessary.
- ForLocal Identification, choose from the following types and enter a value that you determine:FQDN (hostname),IP address,KEYID (binary format ID string in HEX),User FQDN (email address). Local identification defines the format and identification of the local gateway. If no value is specified, the local IP address will be used as the local identification value.
- ForPeer Identification, choose from the following types and enter the value:FQDN (hostname),IP address,KEYID (binary format ID string in HEX),User FQDN (email address). Peer identification defines the format and identification of the peer gateway. If no value is specified, the peer IP address will be used as the peer identification value.
- Proceed to Step 7 and continue from there.
- Configure certificate-based authentication.Perform the remaining steps in this procedure if you selectedCertificateas the method of authenticating the peer gateway at the opposite end of the tunnel.
- Select aLocal Certificatethat is already on the firewall from the drop-down, orImporta certificate, orGenerateto create a new certificate.
- Click theHTTP Certificate Exchangecheck box if you want to configure Hash and URL (IKEv2 only). For an HTTP certificate exchange, enter theCertificate URL. For more information, see Hash and URL Certificate Exchange.
- Select theLocal Identificationtype from the following:Distinguished Name (Subject), FQDN (hostname),IP address,User FQDN (email address), and enter the value. Local identification defines the format and identification of the local gateway.
- Select thePeer Identificationtype from the following:Distinguished Name (Subject), FQDN (hostname),IP address,User FQDN (email address), and enter the value. Peer identification defines the format and identification of the peer gateway.
- Select one type ofPeer ID Check:
- Exact—Check this to ensure that the local setting and peer IKE ID payload match exactly.
- Wildcard—Check this to allow the peer identification to match as long as every character before the wildcard (*) matches. The characters after the wildcard need not match.
- ClickPermit peer identification and certificate payload identification mismatchif you want to allow a successful IKE SA even when the peer identification does not match the peer identification in the certificate.
- Choose aCertificate Profilefrom the drop-down. A certificate profile contains information about how to authenticate the peer gateway.
- ClickEnable strict validation of peer’s extended key useif you want to strictly control how the key can be used.
- Configure advanced options for the gateway.
- Select theAdvanced Optionstab.
- In the Common Options section,Enable Passive Modeif you want the firewall to only respond to IKE connection requests and never initiate them.
- Enable NAT Traversalif you have a device performing NAT between the gateways, to have UDP encapsulation used on IKE and UDP protocols, enabling them to pass through intermediate NAT devices.
- If you choseIKEv1 only modeearlier, on the IKEv1 tab:
If the exchange mode is not set toauto, you must configure both peers with the same exchange mode to allow each peer to accept negotiation requests.
- Chooseauto,aggressive, ormainfor theExchange Mode. When a device is set to useautoexchange mode, it can accept bothmainmode andaggressivemode negotiation requests; however, whenever possible, it initiates negotiation and allows exchanges inmainmode.
- (Only if using certificate-based authentication and the exchange mode is not set toaggressivemode) ClickEnable Fragmentationto enable the firewall to operate with IKE Fragmentation.
- ClickDead Peer Detectionand enter anInterval(range is 2-100 seconds). ForRetry,define the time to delay (range is 2-100 seconds) before attempting to re-check availability. Dead peer detection identifies inactive or unavailable IKE peers by sending an IKE phase 1 notification payload to the peer and waiting for an acknowledgment.
- If you choseIKEv2 only modeorIKEv2 preferred modein Step 1, on the IKEv2 tab:
- Select anIKE Crypto Profilefrom the drop-down, which configures IKE Phase 1 options such as the DH group, hash algorithm, and ESP authentication. For information about IKE crypto profiles, see IKE Phase 1.
- Enable Liveness Checkand enter anInterval (sec)(default is 5)if you want to have the gateway send a message request to its gateway peer, requesting a response. If necessary, the Initiator attempts the liveness check up to 10 times. If it doesn’t get a response, the Initiator closes and deletes the IKE_SA and CHILD_SA. The Initiator will start over by sending out another IKE_SA_INIT.
- Save the changes.ClickOKandCommit.
Recommended For You
Recommended videos not found.