Microsoft Azure Site-to-Site VPN with SonicWALL OS | Netwoven
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. The Route Based VPN approach moves network configuration from the VPN policy configuration to Static or Dynamic Route configuration. Not only does Route Based VPN make configuring and maintaining the VPN policy easier, a major advantage of the Route Based VPN feature is that it provides flexibility on how traffic is routed. Click Manage in the top navigation menu Navigate to the Network | Interfaces page. Add Interface. Click on VPN Tunnel interface. Zone is VPN Select the policy Name under VPN policy dropdown menu. Mode/IP assignment 11.11.11.1/30 matching the same subnet on tunnel interface on Cisco device. Enable Route Based VPN configuration is a two-step process. The first step involves creating a Tunnel Interface. The crypto suites used to secure the traffic between two end-points are defined in the Tunnel Interface. The second step involves creating a static or dynamic route using Tunnel Interface. Route Based VPN configuration, introduced in SonicOS Enhanced 5.5, creates a Tunnel Interface between two end points. Static routes can then be added to the Tunnel Interface for reaching the remote networks.The static route may contain the source, destination and service to the Tunnel Interface. The advantages of Route Based VPN are:
There are several advantages to implementing a route-based VPN (a.k.a. tunnel interface VPN) instead of a site-to-site one. While both establish a secure tunnel between appliances, a route policy controls the traffic that passes through the tunnel, giving you mo re flexibility for the services (ports) you want to open across the tunnel as well as redundancy to reroute traffic in case of an
like policy based, you need separate ipsec vpn statements for each pair of networks in each tunnel. on the sonicwall (or cisco/checkpoint) you just put all of the networks into a single vpn connection. for the route based vpn, you need to add that bind-interface command to the vpn statement. don't try to use multipoint vpns with nhtb on the st0
SRX Series,vSRX. Understanding Traffic Selectors in Route-Based VPNs, Example: Configuring Traffic Selectors in a Route-Based VPN
FortiGate to Sonicwall IPSec VPN | Fortinet Technical