SonicOS/X 7 IPSec VPN
- SonicOS and SonicOSX 7 IPSec VPN
- IPSec VPN Overview
- Site to Site VPNs
- VPN Auto Provisioning
- Rules and Settings
- Advanced
- DHCP over VPN
- L2TP Servers and VPN Client Access
- AWS VPN
- SonicWall Support
Rules and Settings
This describes how to configure Tunnel Interface Route-based VPN policies, which provide a route-based VPN solution. Tunnel Interface VPN policies differ from site to site VPN policies, which force the VPN policy configuration to include the network topology configuration. This makes it difficult to configure and maintain the VPN policy with a constantly changing network topology. Refer to Site to Site VPNs for details.
With the route-based VPN approach, network topology configuration is removed from the VPN policy configuration. The VPN policy configuration creates an unnumbered Tunnel Interface between two end points. Static or dynamic routes can then be added to the Tunnel Interface. The route-based VPN approach moves network configuration from the VPN policy configuration to static or dynamic route configuration.
Route-based VPN makes configuring and maintaining the VPN policy easier, and provides flexibility on how traffic is routed. You can define multiple paths for overlapping networks over a clear or redundant VPN.
For auto provisioning of VPN networks, refer to VPN Auto Provisioning for details.
- Adding a Tunnel Interface
- Route Entries for Different Network Segments
- Redundant Static Routes for a Network
Was This Article Helpful?
Help us to improve our support portal