How can I configure a Tunnel Interface VPN (Dynamic Routing BGP or OSPF) between two SonicWalls?

09/27/2023 586 People found this article helpful 510,628 Views

Description

How to Configure a Tunnel Interface VPN (Route-based VPN) between two SonicWall UTM appliances running SonicOS 5.9 firmware and above.

The advantages of Tunnel Interface VPN (Route-Based VPN) between two SonicWall UTM appliances include.

The network topology configuration is removed from the VPN policy configuration.
More flexibility on how traffic is routed. With this feature, users can now define multiple paths for overlapping networks over a clear or redundant VPN.

NOTE: Route-based VPN using a tunnel interface is not supported with 3rd party devices.This article applies only to the SonicWall UTM models above TZ 215 running SonicOS 5.9 firmware.

Network Diagram

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.

Log into the SonicWall on main site.
Navigate to Network| IPsec VPN| Rules and Settings| Policies and click Add. The General tab of Tunnel Interface VPN named Remote Site is shown w/ the IPSec Gateway equal to the other device's X1 IP address, 192.168.60.115.

NOTE: The settings used on the Proposals tab are not shown, but these must be identical on the Tunnel Interface VPN's done on both appliances.

Navigate to Network | System | Interfaces.
Configure the tunnel with the local subnet of the remote site which needs to be access through VPN tunnel as shown below.
The default route to reach the remote network gets automatically added as shown.

Log into the remote SonicWall, navigate to CNetwork| IPsec VPN| Rules and Settings| Policies and click Add.. The General tab of Tunnel Interface VPN named Main Site is shown w/ the IPSec Gateway equal to the other device's X1 IP address, 192.168.60.81.
Navigate to Network | System | Interfaces.
Configure the tunnel with the local subnet of the remote site which needs to be access through VPN tunnel as shown below.
The default route to reach the remote network gets automatically added as shown.

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.

Log into the SonicWall on main site.
Navigate to Manage | Connectivity | VPN | Base Settings and click Add. The General tab of Tunnel Interface VPN named Remote Site is shown w/ the IPSec Gateway equal to the other device's X1 IP address, 192.168.60.115.
NOTE: The settings used on the Proposals tab are not shown, but these must be identical on the Tunnel Interface VPN's done on both appliances.
Navigate to System Setup | Network | Interfaces.
Configure the tunnel with the local subnet of the remote site which needs to be access through VPN tunnel as shown below.
The default route to reach the remote network gets automatically added as shown.
Log into the remote SonicWall, navigate to Connectivity | VPN | Basic Settings and click Add. The General tab of Tunnel Interface VPN named Main Site is shown w/ the IPSec Gateway equal to the other device's X1 IP address, 192.168.60.81.

NOTE:The settings used on the Proposals tab are not shown, but these must be identical on the Tunnel Interface VPN's done on both appliances.
Navigate to Network | Interfaces.
Configure the tunnel with the local subnet of the remote site which needs to be access through VPN tunnel as shown below.
The default route to reach the main network gets automatically added as shown.

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.

Log into the SonicWall on main site.
Navigate to VPN | Settings and click Add. The General tab of Tunnel Interface VPN named Remote Site is shown w/ the IPSec gateway equal to the other device's X1 IP address, 192.168.60.115.

NOTE: The settings used on the Proposals tab are not shown, but these must be identical on the Tunnel Interface VPN's done on both appliances.
Navigate to Network | Interfaces.
Configure the tunnel with the local subnet of the remote site which needs to be access through VPN tunnel as shown below,
The default route to reach the remote network gets automatically added as shown.
Log into the remote SonicWall; navigate to VPN |Settings and click Add. The General tab of Tunnel Interface VPN named Main Site is shown w/ the IPSec Gateway equal to the other device's X1 IP address, 192.168.60.81.

NOTE:The settings used on the Proposals tab are not shown, but these must be identical on the Tunnel Interface VPN's done on both appliances.
Navigate to Network | Interfaces.
Configure the tunnel with the local subnet of the remote site which needs to be access through VPN tunnel as shown below.
The default route to reach the main network gets automatically added as shown.