How can I configure a main mode VPN between a SonicWall and Fortinet firewall?

10/14/2021 385 People found this article helpful 491,439 Views

Download

Print

Share

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

Description

When configuring a Site-to-Site VPN tunnel in SonicOS Enhanced firmware using Main Mode with the SonicWall appliances (Site A) and Fortinet Firewall (Site B) must have routable Static WAN IP address. 

Network Setup

Resolution

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.

Creating Address Objects for VPN subnets 

1. Login to the SonicWall management Interface.
2. Click Manage in the top navigation menu.
3. Navigate to Objects | Address Objects.
4. Click Address objects Tab.
5. Click Add Configure the Address Objects as mentioned in the figure above, click Add and click close when finished.
   

Configuring a VPN policy on Site A SonicWall 

1. Click Manage in the top navigation menu.
2. Navigate to VPN | Base Settings page.
3. Click Add button. The VPN Policy window is displayed.
   
   
   
4. Click General tab. 
   
   
   • Select IKE using Preshared Secret from the Authentication Method menu.
   • Enter a name for the policy in the Name field.
   • Enter the WAN IP address of the remote connection in the IPSec Primary Gateway Name or Address field (Enter Site B's Palo Alto WAN IP address).
   • 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.

   • 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. 
5. Click Network tab.
    
   
   
   
   • Under Local Networks, select a local network from Choose local network from list: and select the address object X0 Subnet (LAN Primary Subnet).
   • Under Destination Networks, select Choose destination network from list: and select the address object Remote network (Site B network).
     
     
6. Click Proposals tab.
    
   
   
   • 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.
   • 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.

   •  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 Advanced tab.
    
   
   
   • 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.
   • Select Enable Windows Networking (NetBIOS) Broadcast to allow access to remote network resources by browsing the Windows® Network Neighborhood.
   • To manage the local SonicWall through the VPN tunnel, select HTTP, HTTPS, or both from Management via this SA. Select HTTP, HTTPS, or both in the User login via this SA to allow users to login using the SA.
   • If you wish to use a router on the LAN for traffic entering this tunnel destined for an unknown subnet, for example, if you configured the other side to Use this VPN Tunnel as default route for all Internet traffic, you should enter the IP address of your router into the Default LAN Gateway (optional) field.
   • 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.

    

8. Click OK.

Configuring a VPN policy on Site B Fortinet Firewall 

• Fortinet Interfaces with LAN and WAN.
  
  
  

Deployment Steps on Fortinet Firewall

1. Creating Address Objects for Local Subnets and VPN subnets.
2. Configuring a VPN policy Phase 1 and Phase 2.
3. Creating Static Route for the destination Network.
4. Create a policy to allow traffic through VPN Tunnel.

 Creating Address Objects for Local Subnets and VPN subnets:

1. Login to the Fortinet Management Interface.
2. Navigate to Firewall Objects | Addresses, on the right and click on Create New button.
   
   
   
3. Configure the Address Objects as mentioned in the figure below for Local Subnet and Remote Subnet, click OK .
   

Configuring a VPN policy Phase 1 and Phase 2

1. Navigate to VPN | IPSec VPN | Auto key IKE, on the right and click on Create Phase 1.
   
   
   
2. Configure Phase 1 VPN as below.
   
   
   
   • Name: SW-FT (Choose the Name for the VPN)
   • Remote Gateway: Static
   • IP Address: 1.1.1.1 (SonicWall WAN IP Address)
   • Local Interface: Port3 WAN (Through which port we are connecting)
   • Mode: Main Mode (as we selected on SonicWall)
   • Authentication Method: Preshared Key (as we selected on SonicWall)
   • Preshared Key: test@123 (Same as SonicWall)
   • Peer Option: IKE Version 1
   • Local Gateway IP: 3.3.3.3 which is the WAN IP of the Fortinet.
   • P1 Proposal: Encryption-DES, Authentication-SHA1 (Same as SonicWall)
   • DH Group: Group 2 (Same as SonicWall)
   • Key life: 28800 (Same as SonicWall)
     
     
3. Click OK .
   
   

 Now Create Phase 2 and configure as below

1. Name: SW-FT (Choose any name for the Phase 2).
2. Click on Advanced to configure the P2 Proposals.
3. Encryption-DES, Authentication-SHA1
4. Key Life: 28800 Seconds.
5. Auto key Keep Alive: Enabled.
6. Quick Mode Selector:
7. Source Address: Select LAN Subnet which we had created an address object.
8. Destination Address: Select Remote Subnet which we had created an address object.
9. Click OK .

Creating Static Route for the destination Network.

1. Navigate to Router | Static Route and Create New.
   
   
   
2. Destination IP/Mask: 192.168.168.0/255.255.255.0 (SonicWall Local Subnet).
3. Device: Select the VPN that is SW-FT in our case.
4. Distance: 10.
   
   
   
5. Click OK .

Create a policy to allow traffic through VPN Tunnel

1. Navigate to Policy | Create New Policy.
   
   
   
2. We need to create 2 policies for inbound and outbound.
    

Policy 1 INBOUND

1. Incoming Interface- Port2 LAN and Outgoing Interface SW-FT (VPN).
2. Source Address- LAN Subnets.
3. Destination Address- Remote Subnets.
4. Services- ALL
5. Action- ACCEPT. 
6. Click OK .
   

Policy 2 OUTBOUND

1. Incoming Interface- SW-FT (VPN) and Outgoing Interface- Port2 LAN.
2. Source Address- Remote Subnets.
3. Destination Address- LAN Subnets.
4. Services- ALL.
5. Action- ACCEPT.
6. Click OK .

How to Test this Scenario

1. Check the tunnel is UP on both the devices and try to ping addresses from Site A to Site B or Vice Versa. 
2. Tunnel is UP on SonicWall.
   
   
   
3. Windows XP PC behind SonicWall which is 192.168.168.144 able to ping Windows XP PC which is behind Fortinet 10.1.1.4.
   
   
   
4. Tunnel is UP on Fortinet.
5. Windows XP PC behind Fortinet which is 10.1.1.4 able to ping Windows XP PC which is behind SonicWall 192.168.168.144.
   

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.

Creating Address Objects for VPN subnets 

1. Login to the SonicWall management Interface.
2. Navigate to Network | Address Objects, scroll down to the bottom of the page and click ADD.
3. Configure the Address Objects as mentioned in the figure above, click Add and click close when finished.
   
   
   

 Configuring a VPN policy on Site A SonicWall

1. Navigate to VPN | Settings page and Click Add. The VPN Policy window is displayed.
   
   
   
2. Click General tab.
   
   
   • Select IKE using Preshared Secret from the Authentication Method menu.
   • Enter a name for the policy in the Name field.
   • Enter the WAN IP address of the remote connection in the IPSec Primary Gateway Name or Address field (Enter Site B's Palo Alto WAN IP address).
   • 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.

   • 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.
3. Click Network tab.
    
   
   
   
   • Under Local Networks, select a local network from Choose local network from list: and select the address object X0 Subnet (LAN Primary Subnet).
   • Under Destination Networks, select Choose destination network from list: and select the address object Remote network (Site B network).
     
     
4. Click the Proposals tab.
    
   
   
   • 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.
   • 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.

   • 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.
5. Click  Advanced tab.
    
   
   
   • 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.
   • Select Enable Windows Networking (NetBIOS) Broadcast to allow access to remote network resources by browsing the Windows® Network Neighborhood.
   • To manage the local SonicWall through the VPN tunnel, select HTTP, HTTPS, or both from Management via this SA. Select HTTP, HTTPS, or both in the User login via this SA to allow users to login using the SA.
   • If you wish to use a router on the LAN for traffic entering this tunnel destined for an unknown subnet, for example, if you configured the other side to Use this VPN Tunnel as default route for all Internet traffic, you should enter the IP address of your router into the Default LAN Gateway (optional) field.
   • 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. 
6. Click OK.

Configuring a VPN policy on Site B Fortinet Firewall 

• Fortinet Interfaces with LAN and WAN.
  

Deployment Steps on Fortinet Firewall

1. Creating Address Objects for Local Subnets and VPN subnets.
2. Configuring a VPN policy Phase 1 and Phase 2.
3. Creating Static Route for the destination Network.
   1. Create a policy to allow traffic through VPN Tunnel.
      
      

 Creating Address Objects for Local Subnets and VPN subnets:

1. Login to the Fortinet management Interface.
2. Navigate to Firewall Objects | Addresses, on the right and click on Create New button.
   
   
   
3. Configure Address Objects as mentioned in the figure below for Local Subnet and Remote Subnet, click OK .
   

 Configuring a VPN policy Phase 1 and Phase 2.

1. Navigate to VPN | IPSec VPN | Auto key IKE, on the right and click  Create Phase 1.
   
   
   
2. Configure Phase 1 VPN as below.
   
   
   
   
3. Name: SW-FT (Choose the Name for the VPN)
4. Remote Gateway: Static
5. IP Address: 1.1.1.1 (SonicWall WAN IP Address)
6. Local Interface: Port3 WAN (Through which port we are connecting)
7. Mode: Main Mode (as we selected on SonicWall)
8. Authentication Method: Preshared Key (as we selected on SonicWall)
9. Preshared Key: test@123 (Same as SonicWall)
10. Peer Option: IKE Version 1
11. Local Gateway IP: 3.3.3.3 which is the WAN IP of the Fortinet.
12. P1 Proposal: Encryption-DES, Authentication-SHA1 (Same as SonicWall)
13. DH Group: Group 2 (Same as SonicWall)
14. Key life: 28800 (Same as SonicWall)
15. Click OK .

 Now Create Phase 2 and configure as below

• Name: SW-FT (Choose any name for the Phase 2).
• Click on Advanced to configure the P2 Proposals.
• Encryption-DES, Authentication-SHA1
• Key Life: 28800 Seconds.
• Auto key Keep Alive: Enabled.
• Quick Mode Selector:
• Source Address: Select LAN Subnet which we had created an address object.
• Destination Address: Select Remote Subnet which we had created an address object.
• Click OK .

Creating Static Route for the destination Network

1. Navigate to Router | Static Route and Create New.
   
   
   
2. Destination IP/Mask: 192.168.168.0/255.255.255.0 (SonicWall Local Subnet).
3. Device: Select the VPN that is SW-FT in our case.
4. Distance: 10.
   
5. Click OK.

Create a policy to allow traffic through VPN Tunnel.

1. Navigate to Policy | Create New Policy.
   
   
   
2. We need to create 2 policies for inbound and outbound.
    

Policy 1 INBOUND

1. Incoming Interface- Port2 LAN and Outgoing Interface SW-FT (VPN).
2. Source Address- LAN Subnets.
3. Destination Address- Remote Subnets.
4. Services- ALL.
5. Action- ACCEPT.
6. Click OK .
   

Policy 2 OUTBOUND

1. Incoming Interface- SW-FT (VPN) and Outgoing Interface- Port2 LAN.
2. Source Address- Remote Subnets.
3. Destination Address- LAN Subnets.
4. Services- ALL.
5. Action- ACCEPT. 
6. Click  OK .

How to Test this Scenario

1. Check the tunnel is UP on both the devices and try to ping addresses from Site A to Site B or Vice Versa.
2. Tunnel is UP on SonicWall.
   
   
   
3. Windows XP PC behind SonicWall which is 192.168.168.144 able to ping Windows XP PC which is behind Fortinet 10.1.1.4.
   
   
   
4. Tunnel is UP on Fortinet.
5. Windows XP PC behind Fortinet which is 10.1.1.4 able to ping Windows XP PC which is behind SonicWall 192.168.168.144.
   
   
   
   

Related Articles

• Initial and Advanced Firewall Setup for high security environments
• How to Create URI List Objects/Groups on SonicOSX 7?
• How to block Hotspot Shield proxy/VPN using Advanced Application Control

Categories

• Firewalls > SonicWall SuperMassive 9000 Series > VPN
• Firewalls > SonicWall SuperMassive E10000 Series > VPN
• Firewalls > TZ Series > VPN
• Firewalls > NSa Series > VPN
• Firewalls > NSv Series > VPN