How do I configure a route based VPN between SonicWall and Cisco?

03/26/2020 42 11670

DESCRIPTION:

When configuring a Route Bases VPN in SonicOS Enhanced firmware using Main Mode both the SonicWall appliances and Cisco ASA firewall (Site A and Site B) must have a routable Static WAN IP address.

RESOLUTION:

Deployment Steps:

Step 1: Configuring a VPN policy on Site A SonicWall.

Step 2: Configuring a VPN policy on Site B Cisco ASA Firewall

Step 3: How to test this scenario.

To manually configure a VPN Policy using IKE with Preshared Secret, follow the steps below:

The below screen shot of SonicWall with basic configuration LAN and WAN.

Configuring a VPN policy on Site A SonicWall

 Login to the SonicWall Management GUI

1. Click Manage in the top navigation menu
2. Navigate to VPN | Base Settings
3. Enable VPN
4. Click Add. The VPN Policy window is displayed.
5. Click the General tab
   
   1. Select Tunnel Interface from the Policy Type menu
   2. Select IKE using Preshared Secret from the Authentication Method menu.
   3. Enter a name for the policy in the Name field.
   4. Enter the WAN IP address of the remote connection in the IPsec Primary Gateway Name or Address field (Enter Site B's WAN IP address).
   5. If the Remote VPN device supports more than one endpoint, you may optionally enter a second host name or IP address of the remote connection in the IPsec Secondary Gateway Name or Address field.
      Note: Secondary gateways are not supported with IKEv2.
   6. Enter a Shared Secret password to be used to setup the Security Association the Shared Secret and Confirm Shared Secret fields. The Shared Secret must be at least 4 characters long, and should comprise both numbers and letters. Optionally, you may specify a Local IKE ID (optional) and Peer IKE ID (optional) for this Policy. By default, the IP Address (ID_IPv4_ADDR) is used for Main Mode negotiations, and the SonicWall Identifier (ID_USER_FQDN) is used for Aggressive Mode.
      
6. Click the Proposal tab.
   1. Under IKE (Phase 1) Proposal, select Main Mode from the Exchange menu. Aggressive Mode is generally used when WAN addressing is dynamically assigned. IKEv2 causes all the negotiation to happen via IKE v2 protocols, rather than using IKE Phase 1 and Phase 2. If you use IKE v2, both ends of the VPN tunnel must use IKE v2.
   2. Under IKE (Phase 1) Proposal, the default values for DH Group, Encryption, Authentication, and Life Time are acceptable for most VPN configurations. Be sure the Phase 1 values on the opposite side of the tunnel are configured to match. You can also choose AES-128, AES-192, or AES-256 from the Authentication menu instead of 3DES for enhanced authentication security.
      Note: The Windows 2000 L2TP client and Windows XP L2TP client can only work with DH Group 2. They are incompatible with DH Groups 1 and 5.
   3. Under IPsec (Phase 2) Proposal, the default values for Protocol, Encryption, Authentication, Enable Perfect Forward Secrecy, DH Group, and Lifetime are acceptable for most VPN SA configurations. Be sure the Phase 2 values on the opposite side of the tunnel are configured to match.
7. Click the Advanced tab
   
   1. Select Enable Keep Alive to use heartbeat messages between peers on this VPN tunnel. If one end of the tunnel fails, using Keepalives will allow for the automatic renegotiation of the tunnel once both sides become available again without having to wait for the proposed Life Time to expire.
   2. Select Enable Windows Networking (NetBIOS) Broadcast to allow access to remote network resources by browsing the Windows Network Neighborhood.
   3. Select an interface or zone from the VPN Policy bound to menu. A Zone WAN is the preferred selection if you are using WAN Load Balancing and you wish to allow the VPN to use either WAN interface.
   4. Click OK to apply the settings.

Creating and Configuring a VPN tunnel interface.

1. Click Manage in the top navigation menu
2. Navigate to the Network | Interfaces page.
3. Add Interface. Click on VPN Tunnel interface.
   
   
4. Zone is VPN
5. Select the policy Name under VPN policy dropdown menu.
6. Mode/IP assignment 11.11.11.1/30 matching the same subnet on tunnel interface on Cisco device.
7. Enable Ping for verifying.

Configuring a VPN policy on Site B Cisco ASA

1. Login to Cisco device.
2. Configure WAN and LAN. The screen shot below with WAN configured as Outside with IP 23.45.67.89 and LAN configured as LAN with IP 20.20.20.1.
   

Verifying the initial Configuration on Cisco ASA.

In the below screenshot we checking the connectivity to upstream modem(ISP) and also remote end SonicWall WAN IP by pinging the IP address.

First Ping to Cisco gateway- 2.2.2.1 –Passed

Second Ping to SonicWall WAN IP-1.1.1.2-Passed

Now we configure the route based VPN.

1. Create a pre-shared key
   
2. Create a ISAKMP Policy
   
3. Create a ISAKMP Profile
   
4. Define an IPsec transform-set
   
5. Define an IPsec Profile
   
6. Create a VPN Tunnel Interface
   

How to test this Scenario:

Find the screen shot below on SonicWall with active VPN Tunnel.

Screenshot below on Cisco with active VPN Tunnel

Resolution for SonicOS 6.2 and Below

The below resolution is for customers using SonicOS 6.2 and earlier firmware. For firewalls that are generation 6 and newer we suggest to upgrade to the latest general release of SonicOS 6.5 firmware.

Deployment Steps:

Step 1: Configuring a VPN policy on Site A SonicWall.

Step 2: Configuring a VPN policy on Site B Cisco ASA Firewall

Step 3: How to test this scenario.

Procedure: 

To manually configure a VPN Policy using IKE with Preshared Secret, follow the steps below:

The below screen shot of SonicWall with basic configuration LAN and WAN.

Configuring a VPN policy on Site A SonicWall

1. Navigate to VPN | Settings page and Click Add button. The VPN Policy window is displayed.
   
2. Click the General tab
   1. Select Tunnel Interface from the Policy Type menu.
   2. Select IKE using Preshared Secret from the Authentication Method menu.
   3. Enter a name for the policy in the Name field.
   4. Enter the WAN IP address of the remote connection in the IPsec Primary Gateway Name or Address field (Enter Site B's WAN IP address).
   5. If the Remote VPN device supports more than one endpoint, you may optionally enter a second host name or IP address of the remote connection in the IPsec Secondary Gateway Name or Address field.
      Note: Secondary gateways are not supported with IKEv2.
   6. Enter a Shared Secret password to be used to setup the Security Association the Shared Secret and Confirm Shared Secret fields. The Shared Secret must be at least 4 characters long, and should comprise both numbers and letters. Optionally, you may specify a Local IKE ID (optional) and Peer IKE ID (optional) for this Policy. By default, the IP Address (ID_IPv4_ADDR) is used for Main Mode negotiations, and the SonicWall Identifier (ID_USER_FQDN) is used for Aggressive Mode.
      
3. Click the Proposals tab.
   1. Under IKE (Phase 1) Proposal, select Main Mode from the Exchange menu. Aggressive Mode is generally used when WAN addressing is dynamically assigned. IKEv2 causes all the negotiation to happen via IKE v2 protocols, rather than using IKE Phase 1 and Phase 2. If you use IKE v2, both ends of the VPN tunnel must use IKE v2.
   2. Under IKE (Phase 1) Proposal, the default values for DH Group, Encryption, Authentication, and Life Time are acceptable for most VPN configurations. Be sure the Phase 1 values on the opposite side of the tunnel are configured to match. You can also choose AES-128, AES-192, or AES-256 from the Authentication menu instead of 3DES for enhanced authentication security.
      Note: The Windows 2000 L2TP client and Windows XP L2TP client can only work with DH Group 2. They are incompatible with DH Groups 1 and 5.
   3. Under IPsec (Phase 2) Proposal, the default values for Protocol, Encryption, Authentication, Enable Perfect Forward Secrecy, DH Group, and Lifetime are acceptable for most VPN SA configurations. Be sure the Phase 2 values on the opposite side of the tunnel are configured to match.
4. Click the Advanced tab
   
   1. Select Enable Keep Alive to use heartbeat messages between peers on this VPN tunnel. If one end of the tunnel fails, using Keepalives will allow for the automatic renegotiation of the tunnel once both sides become available again without having to wait for the proposed Life Time to expire.
   2. Select Enable Windows Networking (NetBIOS) Broadcast to allow access to remote network resources by browsing the Windows® Network Neighborhood.
   3. Select an interface or zone from the VPN Policy bound to menu. A Zone WAN is the preferred selection if you are using WAN Load Balancing and you wish to allow the VPN to use either WAN interface.
   4. Click OK to apply the settings.

Creating and Configuring a VPN tunnel interface.

1. Navigate to Network | Interfaces. Select VPN Tunnel Interface under Add Interface.
   
   
   1. Zone is VPN
   2. Select the policy Name under VPN policy dropdown menu.
   3. Mode/IP assignment 11.11.11.1/30 matching the same subnet on tunnel interface on Cisco device.
   4. Enable Ping for verifying.

Configuring a VPN policy on Site B Cisco ASA

1. Login to Cisco device.
2. Configure WAN and LAN. The screen shot below with WAN configured as Outside with IP 23.45.67.89 and LAN configured as LAN with IP 20.20.20.1.
   

Verifying the initial Configuration on Cisco ASA.

In the below screenshot we checking the connectivity to upstream modem(ISP) and also remote end SonicWall WAN IP by pinging the IP address.

First Ping to Cisco gateway- 2.2.2.1 –Passed

Second Ping to SonicWall WAN IP-1.1.1.2-Passed

Now we configure the route based VPN.

1. Create a pre-shared key
   
2. Create a ISAKMP Policy
   
3. Create a ISAKMP Profile
   
4. Define an IPsec transform-set
   
5. Define an IPsec Profile
   
6. Create a VPN Tunnel Interface
   

How to test this Scenario:

Find the screen shot below on SonicWall with active VPN Tunnel.

Screenshot below on Cisco with active VPN Tunnel