Mar 27, 2015

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: This article covers how to configure a BGP route based VPN between a SonicWall firewall and Microsoft Azure. The following networks will be used for demonstration purposes during this article. Your networks may be different. Azure Side Resources. Gateway subnet: 10.10.1.0/24; LAN subnet: 10.10.2.0/24; Public IP: 52.172.214.101; SonicWall Side Navigate to VPN | Settings and click Add. The General tab of Tunnel Interface VPN is shown with the IPSec Gateway equal Navigate to Network | Routing and click Add . The Route Policy example shown below is one in which the source is Any, and the destination is the sitea_subnet, the Now we are wanting to change our Site-to-Site VPN to a Tunnel Interface/Route Based VPN. I see the Apply NAT policy still applies is there on Site A sonicwall. Here is the next caveat Site A has separate LAN segment that needs to communicate with Site B on separate LAN segment there hence why we wanted to setup the Route Based VPN tunnel.

I have a number of policy sonicwall to route based screenos tunnels running. So the connections can be made. But I see a number of potential mismatches in the configuration. What I am not sure about is the 5GT software setup. I assume from the screenshots you have a version 5.x screenos. I've only worked on 6.x versions. Sonicwall

Route-based VPN: RIP, OSPF: Certificate support : Verisign, Thawte, Cybertrust, RSA Keon, Entrust and Microsoft CA for SonicWall-to-SonicWall VPN, SCEP: VPN features : Dead Peer Detection, DHCP Over VPN, IPSec NAT Traversal, Redundant VPN Gateway, Route-based VPN: Global VPN client platforms supported Route-based VPN: RIP, OSPF: Certificate support : Verisign, Thawte, Cybertrust, RSA Keon, Entrust and Microsoft CA for SonicWall-to-SonicWall VPN, SCEP: VPN features : Dead Peer Detection, DHCP Over VPN, IPSec NAT Traversal, Redundant VPN Gateway, Route-based VPN: Global VPN client platforms supported The SonicWall Global Management System (GMS) enables deployment and management of SonicWall TZ Series firewalls from a single system at the central office.The products include fully tested routing features for IPv4 and IPv6, including route-based VPN protocols OSPF and RIP v1/v2.

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.

Oct 19, 2013 · Sonicwall has a fair amount of information in their knowledgebase about route-based VPN’s as well as some (thin) information about VPN interaction with other vendor firewalls. If you want to provide some more details I’ll be glad to help as I can.