Configuration of an IPSec VPN Server on RV130 and RV130W

Available Languages

Download Options

PDF (233.5 KB)
View with Adobe Reader on a variety of devices
ePub (288.2 KB)
View in various apps on iPhone, iPad, Android, Sony Reader, or Windows Phone
Mobi (Kindle) (860.1 KB)
View on Kindle device or Kindle app on multiple devices

Updated:December 10, 2018

Document ID:SMB4990

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

Configuration of an IPSec VPN Server on RV130 and RV130W

Objective

IPSec VPN (Virtual Private Network) enables you to securely obtain remote access to corporate resources by establishing an encrypted tunnel across the Internet.

The objective of this document is to show you how to configure an IPSec VPN Server on RV130 and RV130W.

Note: For information about how to configure an IPSec VPN Server with the Shrew Soft VPN Client on RV130 and RV130W, refer to the article Use Shrew Soft VPN Client with IPSec VPN Server on RV130 and RV130W.

Applicable Devices

• RV130W Wireless-N VPN Firewall
• RV130 VPN Firewall

Software Version

• v1.0.1.3

Setup IPSec VPN Server

Step 1. Log in to the web configuration utility and choose VPN > IPSec VPN Server > Setup. The Setup page opens.

Step 2. Check the Server Enable checkbox to enable the certificate.

Step 3. (Optional) If your VPN router or VPN Client is behind a NAT gateway, click Edit to configure NAT Traversal. Otherwise, leave NAT Traversal disabled.

Note: For more information about how to configure NAT Traversal settings, refer to Internet Key Exchange (IKE) Policy Settings on RV130 and RV130W VPN Routers.

Step 4. Enter a key between 8 to 49 characters long that will be exchanged between your device and the remote endpoint in the Pre-Shared Key field.

Step 5. From the Exchange Mode drop down list, choose the mode for the IPSec VPN connection. Main is the default mode. However, if your network speed is low, choose the Aggressive mode.

Note: Aggressive mode exchanges the IDs of the end points of the tunnel in clear text during the connection, which requires less time to exchange but is less secure.

Step 6. From the Encryption Algorithm drop-down list, choose the appropriate encryption method to encrypt the Pre-Shared Key in Phase 1. AES-128 is recommended for its high security and fast performance.The VPN tunnel needs to use the same encryption method for both of its ends.

The available options are defined as follows:

• DES — Data Encryption Standard (DES) is a 56-bit, old encryption method which is not very secure, but may be required for backwards compatibility.

• 3DES — Triple Data Encryption Standard (3DES) is a 168-bit, simple encryption method used to increase the key size because it encrypts the data three times. This provides more security than DES but less security than AES.

• AES-128 — Advanced Encryption Standard with 128-bit key (AES-128) uses a 128-bit key for AES encryption. AES is faster and more secure than DES. In general, AES is also faster and more secure than 3DES. AES-128 is faster but less secure than AES-192 and AES-256.

• AES-192 — AES-192 uses a 192-bit key for AES encryption. AES-192 is slower but more secure than AES-128, and faster but less secure than AES-256.

• AES-256 — AES-256 uses a 256-bit key for AES encryption. AES-256 is slower but more secure than AES-128 and AES-192.

Step 7. From the Authentication Algorithm drop-down list, choose the appropriate authentication method to determine how the Encapsulating Security Payload (ESP) protocol header packets are validated in Phase 1. The VPN tunnel needs to use the same authentication method for both ends of the connection.

The available options are defined as follows:

• MD5 — MD5 is a one-way hashing algorithm that produces a 128-bit digest. MD5 computes faster than SHA-1, but is less secure than SHA-1. MD5 is not recommended.

• SHA-1 — SHA-1 is a one-way hashing algorithm that produces a 160-bit digest. SHA-1 computes slower than MD5, but is more secure than MD5.

• SHA2-256 — Specifies the Secure Hash Algorithm SHA2 with the 256-bit digest.

Step 8. From the DH Group drop-down list, choose the appropriate Diffie-Hellman (DH) group to be used with the key in Phase 1. Diffie-Hellman is a cryptographic key exchange protocol which is used in the connection to exchange pre-shared key sets. The strength of the algorithm is determined by bits.

The available options are defined as follows:

• Group1 (768-bit) — Computes the key the fastest, but is the least secure.

• Group2 (1024-bit) — Computes the key slower, but is more secure than Group1.

• Group5 (1536-bit) — Computes the key the slowest, but is the most secure.

Step 9. In the IKE SA Life Time field, enter the time, in seconds, that the automatic IKE key is valid. Once this time expires, a new key is negotiated automatically.

Step 10. From the Local IP drop down list, choose Single if you would like a single local LAN user to access the VPN tunnel, or choose Subnet if you would like multiple users to be able to access it.

Step 11. If Subnet was chosen in Step 10, enter the Network IP address of the sub-network in the IP Address field. If Single was chosen in Step 10, enter the IP address of the single user and skip to Step 13.

Step 12. (Optional) If Subnet was chosen in Step 10, enter the subnet mask of the local network in the Subnet Mask field.

Step 13. In the IPSec SA Lifetime field, enter the time in seconds that the VPN connection remains active in Phase 2. Once this time expires, the IPSec Security Association for the VPN connection is renegotiated.

Step 14. From the Encryption Algorithm drop-down list, choose the appropriate encryption method to encrypt the Pre-Shared key in Phase 2. AES-128 is recommended for its high security and fast performance.The VPN tunnel needs to use the same encryption method for both of its ends.

The available options are defined as follows:

• DES — Data Encryption Standard (DES) is a 56-bit, old encryption method which is the least secure, but may be required for backwards compatibility.

• AES-192 — AES-192 uses a 192-bit key for AES encryption. AES-192 is slower but more secure than AES-128, and faster but less secure than AES-256.

• AES-256 — AES-256 uses a 256-bit key for AES encryption. AES-256 is slower but more secure than AES-128 and AES-192.

Step 15. From the Authentication Algorithm drop-down list, choose the appropriate authentication method to determine how the Encapsulating Security Payload (ESP) protocol header packets are validated in Phase 2.The VPN tunnel needs to use the same authentication method for both of its ends.

The available options are defined as follows:

• MD5 — MD5 is a one-way hashing algorithm that produces a 128-bit digest. MD5 computes faster than SHA-1, but is less secure than SHA-1. MD5 is not recommended.

• SHA-1 — SHA-1 is a one-way hashing algorithm that produces a 160-bit digest. SHA-1 computes slower than MD5, but is more secure than MD5.

• SHA2-256 — Specifies the Secure Hash Algorithm SHA2 with the 256-bit digest.

Step 16. (Optional) In the PFS Key Group field, check the Enable checkbox. Perfect Forward Secrecy (PFS) creates an additional layer of security in protecting your data by ensuring a new DH key in Phase 2. The process is done in case the DH key generated in Phase 1 is compromised in transit.