Site-to-site VPNs are VPNs that are established between dedicated VPN devices allowing the users residing on the LAN on either side to communicate securely. The advantage of site-to-site VPNs is that they negate the need to install VPN client software on the hosts that reside on either LAN. Instead, the secure connection between the VPN gateways is transparent to the end users. Cisco IOS software supports several site-to-site VPN solutions. These solutions, which are described in the following sections, include:
- Traditional IPsec (IP Security) VPN
- Cisco Easy VPN
- DMVPN
- Group Encrypted Transport VPN
NOTE: As previously stated, this is not a security exam. However, you should still have a basic understanding of the different site-to-site VPN solutions. The following sections simply provide a brief overview of each of these solutions. With the exception of the IPsec VPN, which is the most common and popular solution, the configuration of the other VPN solutions is beyond the scope of the ROUTE exam and will not be included in this chapter.
Traditional IPsec (IP Security) VPN
IPsec VPN solutions are very popular and are one or the most commonly implemented VPN solutions. For site-to-site VPN implementations, IPsec VPNs can be implemented simply between two sites, in a full-mesh deployment, or even in a partial mesh deployment. In all implementations, the IPsec VPN solution is used to secure communications between locations, e.g. remote and branch offices and the enterprise network, when data is sent across public networks such as the Internet.
In Cisco IOS software, a traditional site-to-site IPsec VPN is implemented between two routers. This allows traffic that resides on the LAN (internal) interface of each router to be secured before it is send to a remote network across the Internet, for example. As was previously stated, while the actual configuration of IPsec VPNs is beyond the scope of the ROUTE exam, the following section describes how to implement a basic site-to-site VPN based on the topology that is illustrated in Figure 10-16:

Fig. 10-16. Implementing Traditional IPsec Site-to-Site VPNs
In Cisco IOS software, a basic site-to-site IPsec VPN is configured using crypto configuration commands. These crypto commands are used to specify IPsec parameters such as the encryption algorithm to be used, the Diffie Hellman group and the shared secret to be used by the peer routers, amongst other things. In addition to the crypto commands, you must also configure an extended ACL specifying the traffic that will (or will not) be encrypted. Referencing the topology in Figure 10-16, the following configuration is implemented on R1:
| R1(config)#crypto isakmp policy 1 R1(config-isakmp)#encr 3des R1(config-isakmp)#authentication pre-share R1(config-isakmp)#group 2 R1(config-isakmp)#exit R1(config)#crypto isakmp key SECURE address 150.4.4.4 R1(config)#crypto ipsec transform-set ESP-3DES-SHA esp-3des esp-sha-hmac R1(cfg-crypto-trans)#exit R1(config)#crypto map VPN-EXAMPLE 1 ipsec-isakmp % NOTE: This new crypto map will remain disabled until a peer and a valid access list have been configured. R1(config-crypto-map)#description ‘Secure VPN Tunnel To 150.4.4.4 (R4)’ R1(config-crypto-map)#set peer 150.4.4.4 R1(config-crypto-map)#set transform-set ESP-3DES-SHA R1(config-crypto-map)#match address 100 R1(config-crypto-map)#exit R1(config)#access-l 100 permit ip 172.16.1.0 0.0.0.255 172.16.4.0 0.0.0.255 R1(config)#interface serial 0/0 R1(config-if)#description ‘Connected To Internet’ R1(config-if)#crypto map VPN-EXAMPLE R1(config-if)#exit R1(config)#ip route 0.0.0.0 0.0.0.0 serial 0/0 |
Before proceeding with the configuration on R4, the following section describes the commands used in the configuration of R1. The first section, shown below, is used to specify the IKE (ISAKMP) phase 1 parameters for SA. This includes the encryption algorithm, which is Triple DES in this example, as well as the Diffie Hellman group, which is group 2 in this example.
| R1(config)#crypto isakmp policy 1 R1(config-isakmp)#encr 3des R1(config-isakmp)#authentication pre-share R1(config-isakmp)#group 2 R1(config-isakmp)#exit |
NOTE: Diffie Hellman, or simply DH, allows two parties to establish a shared secret over some insecure communications channels, such as the Internet. Diffie-Hellman is a public-key distributing system, also known as key-exchange protocol, which uses asymmetric key cryptography. Cisco IOS supports three Diffie Hellman groups, which are listed in Table 10-4:
| DH Group Number | Description |
|---|---|
| 1 | This specifies the 768-bit Diffie-Hellman group |
| 2 | This specifies the 1024-bit Diffie-Hellman group |
| 3 | This specifies the 1536-bit Diffie-Hellman group |
Tab. 10-4. Cisco IOS Diffie Hellman Group Support
The following section, which is shown below, is used to define the pre-shared key for the two peers, as well as to specify IPsec encryption and authentication algorithms to be used.
| R1(config)#crypto isakmp key SECURE address 150.4.4.4 R1(config)#crypto ipsec transform-set ESP-3DES-SHA esp-3des esp-sha-hmac |
The following section is used to define IKE phase 2 SA parameters. The final configuration then defines the ACL, referenced in the crypto map configuration, which defines interesting traffic. Traffic that matches this ACL will be encrypted. And then finally, the crypto map configuration is applied to the Internet-facing Serial 0/0 interface.
| R1(config)#crypto map VPN-EXAMPLE 1 ipsec-isakmp % NOTE: This new crypto map will remain disabled until a peer and a valid access list have been configured. R1(config-crypto-map)#description ‘Secure VPN Tunnel To 150.4.4.4 (R4)’ R1(config-crypto-map)#set peer 150.4.4.4 R1(config-crypto-map)#set transform-set ESP-3DES-SHA R1(config-crypto-map)#match address 100 R1(config-crypto-map)#exit R1(config)#access-l 100 permit ip 172.16.1.0 0.0.0.255 172.16.4.0 0.0.0.255 R1(config)#interface serial 0/0 R1(config-if)#description ‘Connected To Internet’ R1(config-if)#crypto map VPN-EXAMPLE |
Following the same logic, the same configuration is mirrored on peer router R4 as follows:
| R4(config)#crypto isakmp policy 1 R4(config-isakmp)#encr 3des R4(config-isakmp)#authentication pre-share R4(config-isakmp)#group 2 R4(config-isakmp)#exit R4(config)#crypto isakmp key SECURE address 150.1.1.1 R4(config)#crypto ipsec transform-set ESP-3DES-SHA esp-3des esp-sha-hmac R4(cfg-crypto-trans)#exit R4(config)#crypto map VPN-EXAMPLE 1 ipsec-isakmp % NOTE: This new crypto map will remain disabled until a peer and a valid access list have been configured. R4(config-crypto-map)#description ‘Secure VPN Tunnel To 150.1.1.1 (R1)’ R4(config-crypto-map)#set peer 150.1.1.1 R4(config-crypto-map)#set transform-set ESP-3DES-SHA R4(config-crypto-map)#match address 100 R4(config-crypto-map)#exit R4(config)#access-l 100 permit ip 172.16.4.0 0.0.0.255 172.16.1.0 0.0.0.255 R4(config)#interface serial 0/0 R4(config-if)#description ‘Connected To Internet’ R4(config-if)#crypto map VPN-EXAMPLE R4(config-if)#exit R4(config)#ip route 0.0.0.0 0.0.0.0 serial 0/0 |
As can be seen in the configuration above, the configuration that is implemented on R4 mirrors the configuration implemented on R1. Following this, use the show crypto map command to validate the crypto map configuration, including peers and interfaces to which the configuration has been applied. The output of this command shows the following on router R4:
| R4#show crypto map Crypto Map “VPN-EXAMPLE” 1 ipsec-isakmp Description: ‘Secure VPN Tunnel To 150.1.1.1 (R1)’ Peer = 150.1.1.1 Extended IP access list 100 access-list 100 permit ip 172.16.4.0 0.0.0.255 172.16.1.0 0.0.0.255 Current peer: 150.1.1.1 Security association lifetime: 4608000 kilobytes/3600 seconds PFS (Y/N): N Transform sets={ ESP-3DES-SHA, } Interfaces using crypto map VPN-EXAMPLE: Serial0/0 |
Following this, a simple ping test between the two LAN interfaces of the routers can be used to verify the configuration as follows:
| R4#ping 172.16.1.1 source 172.16.4.4Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 172.16.1.1, timeout is 2 seconds: Packet sent with a source address of 172.16.4.4 .!!!! Success rate is 80 percent (4/5), round-trip min/avg/max = 8/10/12 ms |
NOTE: The first ping packet will time out as the SA is not established. Subsequent ping packets will be successful after this initial timeout. This is normal behavior.
To further validate your IPsec configuration, use the show crypto isakmp sa [detail] command to show information about the SA. When using this command, remember that SA is unidirectional. Following is the output printed by this command following the ping from the LAN interface of R4 to the LAN interface of R1:
| R4#show crypto isakmp sa dst src state conn-id slot status 150.1.1.1 150.4.4.4 QM_IDLE 1 0 ACTIVE |
On the remote end, R1, the same command shows the following:
| R1#show crypto isakmp sa dst src state conn-id slot status 150.1.1.1 150.4.4.4 QM_IDLE 1 0 ACTIVE |
From both routers, a single SA has been established, allowing for bi-directional communication between the two routers, i.e. ICMP echo and echo reply packets. And finally, you can use the show crypto ipsec sa command to view SA status, peer information, and tunnel settings, as well as to see the packet count for encrypted packets in addition to the other information that is also printed by this command:
| R4#show crypto ipsec sainterface: Serial0/0 Crypto map tag: VPN-EXAMPLE, local addr 150.4.4.4 protected vrf: (none) local crypto endpt.: 150.4.4.4, remote crypto endpt.: 150.1.1.1 inbound esp sas: inbound ah sas: inbound pcp sas: outbound esp sas: outbound ah sas: outbound pcp sas: |
Cisco Easy VPN
The Cisco Easy VPN (EzVPN) solution can be used for both remote sites and remote or mobile workers. This solution, which is based on the Cisco Unified Client Framework, allows for centralized VPN management, dynamic policy distribution and configuration simplicity. The EzVPN solution is comprised of two components:
- The Easy VPN Remote
- The Easy VPN Server
The EzVPN Server feature allows routers, Cisco Adaptive Security Appliances (ASAs), and also the legacy Cisco PIX Appliances to act as head-end VPN devices in site-to-site or remote-access VPNs. The feature pushes security policies defined at the central site to the remote device, so that it has up-to-date policies in place before a secure connection is established. It can also terminate VPN tunnels initiated by remote workers running the Cisco VPN Client software on computers, which allows mobile and remote workers to access critical data and applications on their corporate intranet.
The EzVPN Remote feature, which is also referred to as the EzVPN Client feature, minimizes the configuration requirements at remote locations by allowing routers, Cisco ASA 5505 Adaptive Security Appliances, Cisco PIX Security Appliances, and the Cisco VPN Client to receive security policies upon a VPN tunnel connection from a Cisco Easy VPN Server. This solution is ideal for remote offices with little IT support or for large deployments where it is impractical to configure multiple remote devices individually. This feature makes VPN configuration as easy as entering a password, which minimizes local IT support, increases productivity, and lowers costs.
Dynamic Multipoint VPN
Dynamic Multipoint VPN (DMVPN) is a Cisco IOS solution that allows network engineers to build and implement scalable IPsec VPNs. DMVPN allows IPsec VPNs to scale better than traditional hub-and-spoke or spoke-to-spoke VPN solution. With traditional IPsec VPNs, all endpoints must be specified when implementing the crypto configuration. This becomes cumbersome and labor-intensive as the number of sites that need to communicate securely grows. DMVPN allows for such large implementations with relative ease by allowing dynamic hub-to-spoke and spoke-to-spoke (remote branch) IPsec tunnels with minimal configuration.
While both traditional IPsec VPN and DMVPN solutions use standards-based IPsec encryption protocols, DMVPN is different from the traditional IPsec VPN in many ways and offers more advantages for large-scale IPsec VPN implementations. The differences between traditional IPsec VPN and DMVPN implementation include the following:
- Generic Routing Encapsulation Tunneling
- Dynamic Address Resolution
- Dynamic Tunnel Creation
- Dynamic Routing Protocol Support
Unlike traditional IPsec VPNs, DMVPN uses the Cisco Generic Routing Encapsulation protocol to encapsulate packets. GRE uses IP protocol number 47 and was described earlier in this chapter. The Cisco IOS DMVPN solution uses the Next Hop Resolution Protocol (NHRP) to allow routers to dynamically learn the addresses of other routers with which they wish to send data. This negates the need to implement the static peer configuration commands used when configuring traditional IPsec VPNs, which ultimately allows for greater scalability.
With traditional IPsec VPN implementation, all point-to-point IPsec tunnels must be configured on all the routers, even if some of these tunnels are not running or needed at all times, following the sequence of steps illustrated in the previous configuration example. This is applicable to both hub-and-spoke and spoke-to-spoke implementations and communication. With DMVPN, however, only the tunnel between the hub router and different spoke routers is continuously up. When data needs to be securely exchanged between spoke sites, the spokes use NHRP to dynamically determine the required destination address of the destination spoke. A tunnel is the established to the destination spoke router allowing for secure data exchange. After the data transfer, the tunnel is dynamically torn down after a period of inactivity.
Because the DMVPN solution is based on GRE tunnels, which support the tunneling of Unicast, Multicast and Broadcast packets, it also supports dynamic routing protocols, versus the traditional IPsec VPN solution. Routing protocol adjacencies are established between the hub and spoke routers, while NHRP is used for spoke-to-spoke routing logic.
Group Encrypted Transport VPN
The Cisco IOS Group Encrypted Transport VPN, or GET VPN, solution allows for VPN service without tunnels by retaining the original IP packet header and encrypting only the payload or data. GET VPN solution does this by copying the original IP packet header and placing it before the IPsec header. The advantage of retaining the IP header is that policy implementation, such as QoS markings, can be maintained as this information is not lost or encapsulated. Additional advantages of using the GET VPN solution include, but are not limited to, the following:
- A single SA and key pair is used for entire any-to-any group communication
- It allows for any-to-any group communication
- It uses no overlay, e.g. tunneling
- It allows the IP header, and information contained therein, e.g. QoS, to be retained
- It allows for the use of native routing
As previously stated, this is not a security exam. The ultimate objective here is to simply have a basic fundamental understanding of the different site-to-site VPN solutions supported in Cisco IOS software. Table 10-5 summarizes the different site-to-site VPN solutions described above:
| VPN Solution | Characteristics |
|---|---|
| Traditional IPsec VPN |
|
| Cisco Easy VPN |
|
| DMVPN |
|
| GET VPN |
|
Tab. 10-5. Summarizing Site-to-Site VPN Solutions