Configuring Aggressive Mode Site to Site VPN when a Site has Dynamic WAN Public IP address

10/28/2021 2,792 People found this article helpful 511,711 Views

Download

Print

Share

• LinkedIn
• Twitter
• Facebook
• Email
• Copy URL The link has been copied to clipboard

Description

Configuring a Site to Site VPN on the central location (Static WAN IP address)

• Central location network configuration

1. LAN Subnet: 192.168.168.0
2. Subnet Mask: 255.255.255.0
3. WAN IP: 66.249.72.115
4. Local IKE ID SonicWall Identifier: Chicago (This could be any string except it has to match the remote location VPN's Peer IKE ID SonicWall Identifier)

CAUTION: The IP Address can be dynamic but it should always be Public.
Private IP Addresses on WAN cause a Double NAT Effect that is unpredictable due to the uncertainty of the ISP Setup of the NAT Layers - this is why in certain scenarios VPNs may not work correctly when a private IP is specified.

Resolution

Resolution for SonicOS 7.X

This release includes significant user interface changes and many new features that are different from the SonicOS 6.5 and earlier firmware. The below resolution is for customers using SonicOS 7.X firmware.

This solution explains the configuration of a Site to Site VPN on SonicWall appliances when a site has a dynamic WAN IP address.

The VPN policy is setup using Aggressive Mode.

Configuring a Site to Site VPN on the Central location

Creating Address Object for remote Site

• Login to the Central location SonicWall appliance.
• Navigate to Objects | Match Objects | Addresses, Click on Add button, enter the following settings.
  
  
  • Name – Remote Vpn,
  • Zone – VPN,
  • Type – Network,
  • Network – 192.168.168.0
  • Netmask – 255.255.255.0
  • Click Save.
    
    
    

Configuring a VPN Policy 

• Navigate to Network|IPSec VPN|Rules and Settings
• Click the Add button under the VPN Policies section. The VPN Policy window pops up.

General Tab 

•   Select the Authentication method as  IKE Using Preshared Secret.
• Name Remote-Site VPN.
•  IPSec Primary Gateway Name or Address: 0.0.0.0.
   NOTE: Since the WAN IP address changes frequently, it is recommended to use the 0.0.0.0 IP address as the Primary Gateway.
• IPSec Secondary Gateway Name or Address: 0.0.0.0.
• Shared Secret: SonicWall (The Shared Secret would be the same at both SonicWall’s. You can choose any Secret Key, but it should be entered the same on both sites).
• Local IKE ID: SonicWall Identifier -Central_Site(This could be any string except it has to match the remote location VPN's Peer IKE ID SonicWall Identifier)..
• Peer IKE ID: SonicWall Identifier - Remote_Site(This could be any string except it has to match the remote location VPN's Local IKE ID SonicWall Identifier).
  
  

 Network Tab 

• Select Choose local network from list, and select the Address Object – X0 Subnet (LAN subnet).
• Select Choose destination network the list, and select the Address Object – Remote Vpn.
  
  

Proposals Tab

• IKE (Phase 1) Proposal.
• Exchange:  Aggressive Mode.
• DH Group:  Group 2.
• Encryption: AES-128.
• Authentication: SHA1.
• Life Time (seconds): 28800.
• IPSec (Phase 2) Proposal.
• Protocol:  ESP
• Encryption: AES-128.
• Authentication: SHA1.
• Enable Perfect Forward Secrecy(not checked).
• Life Time (seconds): 28800. 
  
  
  
  

Advanced tab

• Ensure that the VPN Policy bound to: Zone WAN.
• Click Save.
  
  NOTE: KeepAlive option will be disabled when Vpn policy configured with Primary Gateway Name or Address as 0.0.0.0.
  
  
  

Configuring a Site to Site VPN on the remote location (Dynamic WAN IP address)

Network Configuration 

•  LAN Subnet: 192.168.168.0
• Subnet Mask: 255.255.255.0.
• WAN IP: DHCP (As this is a Dynamic IP Address).
• Local IKE ID SonicWall Identifier:Remote_Site(This has to match the central location VPN's Peer IKE ID SonicWall Identifier).

Creating Address Object for remote site

• Login to the Remote location SonicWall appliance.
• Navigate to Objects | Match Objects | Addresses, Click on Add button, enter the following settings.
  
  
  • Name – Central Vpn,
  • Zone – VPN,
  • Type – Network,
  • Network – 192.168.0.0
  • Netmask – 255.255.255.0
  • Click Save.
    
    
    

Configuration VPN Policy

• Navigate to Network|IPSec VPN|Rules and Settings
• Click the Add button under the VPN Policies section. The VPN Policy window pops up.

General Tab 

•   Select the Authentication method as  IKE Using Preshared Secret.
• Name Central-Site VPN.
•  IPSec Primary Gateway Name or Address: 66.249.72.115 (Gateway of the main site, which is static IP)
• IPSec Secondary Gateway Name or Address: 0.0.0.0.
• Shared Secret: SonicWall (The Shared Secret would be the same at both SonicWall’s. You can choose any Secret Key, but it should be entered the same on both sites).
• Local IKE ID: SonicWall Identifier -Remote_Site(This could be any string except it has to match the remote location VPN's Peer IKE ID SonicWall Identifier)
• Peer IKE ID: SonicWall Identifier - Central_Site(This could be any string except it has to match the remote location VPN's Local IKE ID SonicWall Identifier) 
  
  
  

 Network Tab 

• Select Choose local network from list, and select the Address Object – X0 Subnet .
• Select Choose destination network from list, and select the Address Object – Central Vpn.
  
  
  

Proposals Tab

• IKE (Phase 1) Proposal.
• Exchange:  Aggressive Mode.
• DH Group:  Group 2.
• Encryption: AES-128 .
• Authentication: SHA1.
• Life Time (seconds): 28800  .
• IPSec (Phase 2) Proposal.
• Protocol:  ESP.
• Encryption: AES-128.
• Authentication: SHA1.
• Enable Perfect Forward Secrecy (not checked) .
• DH Group:  Group 2.
• Life Time (seconds): 28800.
  
  

 Advanced Tab

• Enable Keep Alive box should be checked.
• VPN Policy bound to: Zone WAN.
• Click Save.
  

How to Test

• From the remote location try to ping an IP address on the central location.
  

  NOTE: Before receiving successful replies, you might see couple of “Request Timed Out“ messages while the VPN tunnel is still establishing.

  
  
  
  
  

Resolution for SonicOS 6.5

This release includes significant user interface changes and many new features that are different from the SonicOS 6.2 and earlier firmware. The below resolution is for customers using SonicOS 6.5 firmware.

This solution explains the configuration of a Site to Site VPN on SonicWall appliances when a site has dynamic WAN IP address.

The VPN policy is setup using Aggressive Mode.

Configuring a Site to Site VPN on the Central location

• Creating Address Object for remote Site

1. Login to the central location SonicWall appliance.
2. Navigate to Manage | Policies | Objects | AddressObjects  page.
3. Click Add button, enter the following settings.
   
   
   • Name – newyork vpn,
   • Zone – VPN,
   • Type – Network,
   • Network – 10.10.10.0,
   • Netmask – 255.255.255.0
     
     
4. Click OK.
   
   
   

• Configuring a VPN Policy 

1. Navigate to Manage | Connectivity | VPN | Base Settings.
2. Check the box “Enable VPN” under Global VPN Settings.
3. Click Add button under VPN Policies section. The VPN Policy window pops up.

General Tab 

•   Select the Authentication method as  IKE Using Preshared Secret.
• Name: New York Aggressive Mode VPN.
•  IPSec Primary Gateway Name or Address: 0.0.0.0.
  
  
  

  NOTE: Since the WAN IP address changes frequently, it is recommended to use the 0.0.0.0 IP address as the Primary Gateway.

• IPSec Secondary Gateway Name or Address: 0.0.0.0.
• Shared Secret: SonicWall (The Shared Secret would be the same at both SonicWall’s. You can choose any Secret Key, but it should be entered sam on both sites).
• Local IKE ID: SonicWall Identifier - Chicago (This could be any string except it has to match the remote location VPN's Peer IKE ID SonicWall Identifier)..
• Peer IKE ID: SonicWall Identifier - newyork (This could be any string except it has to match the remote location VPN's Local IKE ID SonicWall Identifier).
  
  

 
Network Tab 

• Select Choose local network from list, and select the Address Object – X0 Subnet (LAN subnet).
• Select Choose destination network from list, and select the Address Object – newyork vpn.
  
  
  

Proposals Tab

• IKE (Phase 1) Proposal.
• Exchange:  Aggressive Mode.
• DH Group:  Group 2.
• Encryption: 3DES.
• Authentication: SHA1.
• Life Time (seconds): 28800 .
• IPSec (Phase 2) Proposal.
• Protocol:  ESP.
• Encryption: 3DES.
• Authentication: SHA1.
• Enable Perfect Forward Secrecy(not checked).
• Life Time (seconds): 28800. 
  
  
  
  

Advanced tab

• Ensure that the VPN Policy bound to: Zone WAN.
• Click OK 
  
  
  
  
  
  

Configuring a Site to Site VPN on the remote location (Dynamic WAN IP address)

NOTE: The Dynamic WAN IP Address must be Public.

Network Configuration 

1.  LAN Subnet: 10.10.10.0.
2. Subnet Mask: 255.255.255.0.
3.  WAN IP: DHCP (As this is a Dynamic IP Address).
4. Local IKE ID SonicWall Identifier: newyork (This has to match the central location VPN's Peer IKE ID SonicWall Identifier).

• Creating Address Object for remote site

1. Login to the Remote location SonicWall appliance.
2. Navigate to Manage | Policies | Objects | AddressObjects page.
3. Click Add button, enter the following settings.
   
   
   • Name – Chicago vpn.
   • Zone – VPN.
   • Type – Network.
   • Network – 192.168.168.0.
   • Netmask – 255.255.255.0.
     
4. Click OK .
   

• Configuration VPN Policy

1. Navigate to Manage | Connectivity | VPN | Base Settings.
2. Check the box  Enable VPN under Global VPN Settings.
3.  Click  Add button under the VPN Policies section. The VPN Policy window pops up.

General Tab

•  Select the Authentication method as IKE Using Preshared Secret.
•   Name: Chicago Aggressive Mode VPN.
•  IPSec Primary Gateway Name or Address: 66.249.72.115 ( Gateway of the main site, which is static IP).
• IPSec Secondary Gateway Name or Address: 0.0.0.0.
• Shared Secret: SonicWall.
•  Local IKE ID: SonicWall Identifier - newyork (This has to match the central location VPN's Peer IKE ID SonicWall Identifier).
• Peer IKE ID: SonicWall Identifier – Chicago (This has to match the central location VPN's Local IKE ID SonicWall Identifier).
  

 Network Tab 

• Select Choose local network from list, and select the Address Object – LAN Primary Subnet .
• Select Choose destination network from list, and select the Address Object – Chicago vpn.
  
  

Proposals Tab

• IKE (Phase 1) Proposal.
• Exchange:  Aggressive Mode.
• DH Group:  Group 2.
• Encryption: 3DES .
• Authentication: SHA1.
• Life Time (seconds): 28800  .
• IPSec (Phase 2) Proposal.
• Protocol:  ESP.
• Encryption: 3DES .
• Authentication: SHA1.
• Enable Perfect Forward Secrecy (not checked) .
• DH Group:  Group 2.
• Life Time (seconds): 28800.
  
  

 Advanced Tab

• Enable Keep Alive box should be checked.
• VPN Policy bound to: Zone WAN.
• Click OK .
  

How to Test

• From the remote location try to ping an IP address on the central location.
  

  NOTE:Before receiving successful replies, you might see couple of “Request Timed Out“ messages while the VPN tunnel is still establishing.

Related Articles

• How can I enable Enhanced Audit Logging Support?
• How to stop the creation of Auto-Added Access Rules and enable the ability to edit or delete the existing rules?
• How to re-deploy a NSv in the existing resource group in azure platform

Categories

• Firewalls > NSa Series > VPN
• Firewalls > NSv Series > VPN
• Firewalls > TZ Series > VPN