Internet Key Exchange

Similar documents
Configuring a VPN Using Easy VPN and an IPSec Tunnel, page 1

VPN Ports and LAN-to-LAN Tunnels

VPN Overview. VPN Types

IPsec Dead Peer Detection Periodic Message Option

Implementing Internet Key Exchange Security Protocol

Configuring LAN-to-LAN IPsec VPNs

Set Up a Remote Access Tunnel (Client to Gateway) for VPN Clients on RV016, RV042, RV042G and RV082 VPN Routers

Table of Contents 1 IKE 1-1

LAN-to-LAN IPsec VPNs

Configuring Internet Key Exchange Version 2

Configuring Remote Access IPSec VPNs

Configuration of an IPSec VPN Server on RV130 and RV130W

Virtual Tunnel Interface

BiGuard C01 BiGuard VPN Client Quick Installation Guide (BiGuard series VPN enabled devices) Secure access to Company Network

Internet. SonicWALL IP Cisco IOS IP IP Network Mask

Configuring a Hub & Spoke VPN in AOS

Defining IPsec Networks and Customers

Internet Key Exchange Security Protocol Commands

Configuring Internet Key Exchange Version 2 and FlexVPN Site-to-Site

Cisco Exam Questions & Answers

Sample excerpt. Virtual Private Networks. Contents

Configuration Guide. How to connect to an IPSec VPN using an iphone in ios. Overview

Configuring Internet Key Exchange Security Protocol

Configuration of Shrew VPN Client on RV042, RV042G and RV082 VPN Routers through Windows

Digi Application Guide Configure VPN Tunnel with Certificates on Digi Connect WAN 3G

Quick Note. Configure an IPSec VPN tunnel in Aggressive mode between a TransPort LR router and a Cisco router. Digi Technical Support 7 October 2016

IPsec Dead Peer Detection Periodic Message Option

IPv6 over IPv4 GRE Tunnel Protection

Packet Tracer - Configure and Verify a Site-to-Site IPsec VPN Using CLI

Configuring IPsec and ISAKMP

Quick Note. Configure an IPSec VPN tunnel between a Digi TransPort LR router and a Digi Connect gateway. Digi Technical Support 20 September 2016

IPSec VPN Setup with IKE Preshared Key and Manual Key on WRVS4400N Router

Firepower Threat Defense Site-to-site VPNs

L2TP IPsec Support for NAT and PAT Windows Clients

How to Configure a Site-to-Site IPsec IKEv1 VPN Tunnel

Release Notes. NCP Android Secure Managed Client. 1. New Features and Enhancements. 2. Improvements / Problems Resolved. 3.

Network Security 2. Module 4 Configure Site-to-Site VPN Using Pre-Shared Keys

IKE and Load Balancing

Configuring WAN Backhaul Redundancy

Configuring VPN from Proventia M Series Appliance to Proventia M Series Appliance

Network Security CSN11111

Lab 9: VPNs IPSec Remote Access VPN

Configuring Security for VPNs with IPsec

VPN Auto Provisioning

L2TP over IPsec. About L2TP over IPsec/IKEv1 VPN

Virtual Private Networks

Quick Note 65. Configure an IPSec VPN tunnel between a TransPort WR router and an Accelerated SR router. Digi Technical Support 7 June 2018

Chapter 8 Lab Configuring a Site-to-Site VPN Using Cisco IOS

Dynamic Multipoint VPN between CradlePoint and Cisco Router Example

How to Configure a Site-to-Site IPsec IKEv1 VPN Tunnel

Chapter 5 Virtual Private Networking

Service Managed Gateway TM. Configuring IPSec VPN

Configuring VPNs in the EN-1000

Configuring Cisco VPN Concentrator to Support Avaya 96xx Phones Issue 1.0. Issue th October 2009 ABSTRACT

IKE. Certificate Group Matching. Policy CHAPTER

NCP Secure Enterprise macos Client Release Notes

Lab - Configuring a Site-to-Site VPN Using Cisco IOS and CCP

Configuring IPSec tunnels on Vocality units

Securizarea Calculatoarelor și a Rețelelor 29. Monitorizarea și depanarea VPN-urilor IPSec Site-to-Site

IPsec Anti-Replay Window Expanding and Disabling

In the event of re-installation, the client software will be installed as a test version (max 10 days) until the required license key is entered.

This version of the des Secure Enterprise MAC Client can be used on Mac OS X 10.7 Lion platform.

IPsec Dead Peer Detection PeriodicMessage Option

Securizarea Calculatoarelor și a Rețelelor 28. Implementarea VPN-urilor IPSec Site-to-Site

How to Configure Forcepoint NGFW Route-Based VPN to AWS with BGP TECHNICAL DOCUMENT

SSL VPN - IPv6 Support

SSL VPN - IPv6 Support

Virtual Tunnel Interface

NCP Secure Entry macos Client Release Notes

IPSec Site-to-Site VPN (SVTI)

Google Cloud VPN Interop Guide

Configuring VPN from Proventia M Series Appliance to NetScreen Systems

How to Configure an IPsec VPN to an AWS VPN Gateway with BGP

IPSec Network Applications

Release Notes. NCP Secure Enterprise Mac Client. 1. New Features and Enhancements. 2. Improvements / Problems Resolved. 3.

MWA Deployment Guide. VPN Termination from Smartphone to Cisco ISR G2 Router

How to Configure BGP over IKEv2 IPsec Site-to- Site VPN to an Google Cloud VPN Gateway

IPsec Dead Peer Detection Periodic Message Option

How to Configure an IKEv1 IPsec VPN to an AWS VPN Gateway with BGP

NCP Secure Managed Android Client Release Notes

Security for VPNs with IPsec Configuration Guide, Cisco IOS XE Release 3S

keepalive (isakmp profile)

Index. Numerics 3DES (triple data encryption standard), 21

VPN Configuration Guide. NETGEAR FVG318 / FVS318G / FVS336G / FVS338 / DGFV338 FVX538 / SRXN3205 / SRX5308 / ProSecure UTM Series

Chapter 6 Virtual Private Networking

IPsec NAT Transparency

LAN to LAN IPsec Tunnel Between a Cisco VPN 3000 Concentrator and Router with AES Configuration Example

The EN-4000 in Virtual Private Networks

ACADEMIA LOCAL CISCO UCV-MARACAY CONTENIDO DE CURSO CURRICULUM CCNA. SEGURIDAD SEGURIDAD EN REDES. NIVEL II. VERSION 2.0

IPsec and ISAKMP. About Tunneling, IPsec, and ISAKMP

VNS3 IPsec Configuration. VNS3 to Cisco ASA ASDM 5.2

IPsec and ISAKMP. About Tunneling, IPsec, and ISAKMP

Router Allows VPN Clients to Connect IPsec and Internet Using Split Tunneling Configuration Example

IPsec and ISAKMP. About Tunneling, IPsec, and ISAKMP

Crypto Templates. Crypto Template Parameters

Security for VPNs with IPsec Configuration Guide, Cisco IOS Release 15M&T

Case 1: VPN direction from Vigor2130 to Vigor2820

VPN Option Guide for Site-to-Site VPNs

Quick Note 060. Configure a TransPort router as an EZVPN Client (XAUTH and MODECFG) to a Cisco Router running IOS 15.x

How to Configure an IKEv1 IPsec VPN to an AWS VPN Gateway with BGP

Transcription:

CHAPTER16 The help topics in this section describe the (IKE) configuration screens. (IKE) What Do You Want to Do? (IKE) is a standard method for arranging for secure, authenticated communications. IKE establishes session keys (and associated cryptographic and networking configuration) between two hosts across the network. Cisco SDM lets you create IKE policies that will protect the identities of peers during authentication. Cisco SDM also lets you create pre-shared keys that peers exchange. If you want to: Learn more about IKE. Enable IKE. You must enable IKE for VPN connections to use IKE negotiations. Do this: Click More About IKE. Click Global Settings, and then click Edit to enable IKE and make other global settings for IKE. 16-1

(IKE) Chapter 16 If you want to: Create an IKE policy. Cisco SDM provides a default IKE policy, but there is no guarantee that the peer has the same policy. You should configure other IKE policies so that the router is able to offer an IKE policy that the peer can accept. Create a pre-shared key. If IKE is used, the peers at each end must exchange a pre-shared key to authenticate each other. Create an IKE profile. Do this: Click the IKE Policy node on the VPN tree. See IKE Policies for more information. Click the Pre-Shared Key node on the VPN tree. See IKE Pre-shared Keys for more information. Click the IKE Profile node on the VPN tree. See IKE Profiles for more information. IKE Policies IKE negotiations must be protected; therefore, each IKE negotiation begins by each peer agreeing on a common (shared) IKE policy. This policy states which security parameters will be used to protect subsequent IKE negotiations. This window shows the IKE policies configured on the router, and allows you to add, edit, or remove an IKE policy from the router s configuration. If no IKE policies have been configured on the router, this window shows the default IKE policy. After the two peers agree on a policy, the security parameters of the policy are identified by a security association established at each peer. These security associations apply to all subsequent IKE traffic during the negotiation. The IKE policies in this list are available to all VPN connections. Priority An integer value that specifies the priority of this policy relative to the other configured IKE policies. Assign the lowest numbers to the IKE policies that you prefer that the router use. The router will offer those policies first during negotiations. Encryption The type of encryption that should be used to communicate this IKE policy. 16-2

Chapter 16 (IKE) Hash The authentication algorithm for negotiation. There are two possible values: Secure Hash Algorithm (SHA) Message Digest 5 (MD5) Authentication The authentication method to be used. Pre-SHARE. Authentication will be performed using pre-shared keys. RSA_SIG. Authentication will be performed using digital signatures. Type What Do You Want to Do? Either SDM_DEFAULT or User Defined. SDM_DEFAULT policies cannot be edited. If you want to: Learn more about IKE policies. Add an IKE policy to the router s configuration. Cisco SDM provides a default IKE policy, but there is no guarantee that the peer has the same policy. You should configure other IKE policies so that the router is able to offer an IKE policy that the peer can accept. Edit an existing IKE policy. Remove an IKE policy from the router s configuration. Do this: See More About IKE Policies. Click Add, and configure a new IKE policy in the Add IKE policy window. Choose the IKE policy that you want to edit, and click Edit. Then edit the IKE policy in the Edit IKE policy window. Default IKE policies are read only. They cannot be edited. Choose the IKE policy that you want to remove, and click Remove. 16-3

(IKE) Chapter 16 Add or Edit IKE Policy Add or edit an IKE policy in this window. Note Not all routers support all encryption types. Unsupported types will not appear in the screen. Not all IOS images support all the encryption types that Cisco SDM supports. Types unsupported by the IOS image will not appear in the screen. If hardware encryption is turned on, only those encryption types supported by both hardware encryption and the IOS image will appear in the screen. Priority An integer value that specifies the priority of this policy relative to the other configured IKE policies. Assign the lowest numbers to the IKE policies that you prefer that the router use. The router will offer those policies first during negotiations. Encryption The type of encryption that should be used to communicate this IKE policy. Cisco SDM supports a variety of encryption types, listed in order of security. The more secure an encryption type, the more processing time it requires. Note If your router does not support an encryption type, the type will not appear in the list. Cisco SDM supports the following types of encryption: Data Encryption Standard (DES) This form of encryption supports 56-bit encryption. Triple Data Encryption Standard (3DES) This is a stronger form of encryption than DES, supporting 168-bit encryption. AES-128 Advanced Encryption Standard (AES) encryption with a 128-bit key. AES provides greater security than DES and is computationally more efficient than triple DES. 16-4

Chapter 16 (IKE) AES-192 Advanced Encryption Standard (AES) encryption with a 192-bit key. AES-256 Advanced Encryption Standard (AES) encryption with a 256-bit key. Hash The authentication algorithm to be used for the negotiation. There are two options: Secure Hash Algorithm (SHA) Message Digest 5 (MD5) Authentication The authentication method to be used. Pre-SHARE. Authentication will be performed using pre-shared keys. RSA_SIG. Authentication will be performed using digital signatures. D-H Group Diffie-Hellman (D-H) Group. Diffie-Hellman is a public-key cryptography protocol that allows two routers to establish a shared secret over an unsecure communications channel. The options are as follows: group1 768-bit D-H Group. D-H Group 1. group2 1024-bit D-H Group. D-H Group 2. This group provides more security than group 1, but requires more processing time. group5 1536-bit D-H Group. D-H Group 5. This group provides more security than group 2, but requires more processing time. Note If your router does not support group5, it will not appear in the list. Easy VPN servers do not support D-H Group 1. 16-5

(IKE) Chapter 16 Lifetime This is the lifetime of the security association, in hours, minutes and seconds. The default is one day, or 24:00:00. IKE Pre-shared Keys Icon This window allows you to view, add, edit, and remove IKE pre-shared keys in the router s configuration. A pre-shared key is exchanged with a remote peer during IKE negotiation. Both peers must be configured with the same key. If a pre-shared key is read-only, the read-only icon appears in this column. A pre-shared key will be marked as read-only if it is configured with the no-xauth CLI option Peer IP/Name Network Mask Pre-Shared Key An IP address or name of a peer with whom this key is shared. If an IP address is supplied, it can specify all peers in a network or subnetwork, or just an individual host. If a name is specified, then the key is shared by only the named peer. The network mask specifies how much of the peer IP address is used for the network address and how much is used for the host address. A network mask of 255.255.255.255 indicates that the peer IP address is an address for a specific host. A network mask containing zeros in the least significant bytes indicates that the peer IP address is a network or subnet address. For example a network mask of 255.255.248.0 indicates that the first 22 bits of the address are used for the network address and that the last 10 bits are for the host part of the address. The pre-shared key is not readable in Cisco SDM windows. If you need to examine the pre shared key, go to View->Running Config. This will display the running configuration. The key is contained in the crypto isakmp key command. 16-6

Chapter 16 (IKE) If you want to: Add a pre-shared key to the router s configuration. Edit an existing pre-shared key. Remove an existing pre-shared key. Do this: Click Add, and add the pre-shared key in the Adda new Pre Shared Key window. Select the pre-shared key, and click Edit. Then edit the key in the Edit Pre Shared Key window. Select the pre-shared key, and click Remove. Add or Edit Pre Shared Key Key Reenter Key Peer Hostname Use this window to add or edit a pre-shared key. This is an alphanumeric string that will be exchanged with the remote peer. The same key must be configured on the remote peer. You should make this key difficult to guess. Question marks (?) and spaces must not be used in the pre-shared key. Enter the same string that you entered in the Key field, for confirmation. Select Hostname if you want the key to apply to a specific host. Select IP Address if you want to specify a network or subnetwork, or if you want to enter the IP address of a specific host because there is no DNS server to translate host names to IP addresses This field appears if you selected Hostname in the Peer field. Enter the peer s host name. There must be a DNS server on the network capable of resolving the host name to an IP address. 16-7

(IKE) Chapter 16 IP Address/Subnet Mask User Authentication [Xauth] These fields appear if you selected IP Address in the Peer field. Enter the IP address of a network or subnet in the IP Address field. The pre-shared key will apply to all peers in that network or subnet. For more information, refer to IP Addresses and Subnet Masks. Enter a subnet mask if the IP address you entered is a subnet address, and not the address of a specific host. Check this box if site-to-site VPN peers use XAuth to authenticate themselves. If Xauth authenticationn is enabled in VPN Global Settings, it is enabled for site-to-site peers as well as for Easy VPN connections. IKE Profiles IKE Profiles IKE profiles, also called ISAKMP profiles, enable you to define a set of IKE parameters that you can associate with one or more IPSec tunnels. An IKE profile applies parameters to an incoming IPSec connection identified uniquely through its concept of match identity criteria. These criteria are based on the IKE identity that is presented by incoming IKE connections and includes IP address, fully qualified domain name (FQDN), and group (the virtual private network [VPN] remote client grouping). For more information on ISAKMP profiles, and how they are configured using the Cisco IOS CLI, go to Cisco.com and follow this path: Products and Services > Cisco IOS Software > Cisco IOS Security > Cisco IOS IPSec > Product Literature > White Papers > ISAKMP Profile Overview The IKE Profiles area of the screen lists the configured IKE profiles and includes the profile name, the IPSec profile it is used by, and a description of the profile if one has beenprovided. If no IPSec profile uses the selected IKE profile, the value <none> appears in the Used By column. When you create an IKE profile from this window, the profile is displayed in the list. IKE profiles created when you create 16-8

Chapter 16 (IKE) Details of IKE Profile The details area of the screen lists the configuration values for the selected profile. You can use it to view details without clicking the Edit button and displaying an additional dialog. If you need to make changes, click Edit and make the changes you need in the displayed dialog. To learn more about the information shown in this area, click Add or Edit an IKE Profile. Add or Edit an IKE Profile IKE Profile Name Virtual Tunnel Interface Match Identity Type Enter information andmake settings in this dialog to create an IKE profile and associate it with a virtual tunnel interface. Enter a name for this IKE profile. If you are editing a profile, this field is enabled. Choose the virtual tunnel interface to which you want to associate this IKE profile from the Virtual Tunnel Interface list. If you need to create a virtual tunnel interface, click Add and create the interface in the displayed dialog. The IKE profile includes match criteria that allow the router to identify the incoming and outgoing connections to which the IKE connection parameters are to apply. Match criteria can currently be appliedto VPN groups. Group is automatically chosen in the Match Identity Type field. Click Add to build a list of the groups that you want to be included in the match criteria. Choose Add External Group Name to add the name of a group that is not configured on the router, and enter the name in the dialog displayed. Choose Select From Local Groups to add the name of a group that is configured on the router. In the displayed dialog, check the box next to the group that you want to add. If all the local groups are used in other IKE profiles, SDM informs you that all groups have been selected. 16-9

(IKE) Chapter 16 Mode Configuration Group Policy Lookup Authorization Policy User Authentication Policy Dead Peer Discovery Description Choose Respond in the Mode Configuration field if the router is to respond to mode configuration requests. Choose Initiate if the router is to initiate mode configuration requests. Choose Both if the router is to both initiate and respond to mode configuration requests. You must specify an authorization policy that controls access to group policy information on the AAA server. Choose default if you want to grant access to group policy lookup information. To specify a policy, choose an existing policy in the list, or click Add to create a policy in the displayed dialog. You can specify a user authentication policy to use for XAuth logins. Choose default if you want to allow XAuth logins. To specify a policy to control XAuth logins, choose an existing policy in the list, or click Add to create a policy in the displayed dialog. Click Dead Peer Discovery to enable the router to send dead peer detection (DPD) messages to peers. If a peer does not respond to DPD messages, the connection with it is dropped. Specify the number of seconds between DPD messages in the Keepalive Interval field. The range is from 1 to 3600 seconds. Specify the number of seconds between retries if DPD messages fail in the Retries field. The range is from 2 to 60 seconds. Dead peer discovery helps manage connections without administrator intervention, but it generates packets that both peers must process in order to maintain the connection. You can add a description of the IKE profile that you are adding or editing. 16-10

Chapter 16 (IKE) 16-11

(IKE) Chapter 16 16-12