SonicOS 7.0 Rules and Policies for Classic Mode
- SonicOS 7.0 Rules and Policies
- Access Rules
- Setting Firewall Access Rules
- About Connection Limiting
- Using Bandwidth Management with Access Rules
- Creating Access Rules
- Configuring Access Rules for IPv6
- Enabling and Disabling Access Rules
- Editing Access Rules
- Deleting Access Rules
- Restoring Access Rules to Default Settings
- Displaying Access Rules
- Displaying Access Rule Traffic Statistics
- Configuring Access Rules for NAT64
- Configuring Access Rules for a Zone
- Access Rules for DNS Proxy
- User Priority for Access Rules
- Access Rule Configuration Examples
- Setting Firewall Access Rules
- NAT Rules
- About NAT in SonicOS
- About NAT Load Balancing
- About NAT64
- About FQDN-based NAT
- About Source MAC Address Override
- Viewing NAT Policy Entries
- Adding or Editing NAT or NAT64 Rule Policies
- Deleting NAT Policies
- Creating NAT Rule Policies: Examples
- Creating a One-to-One NAT Policy for Inbound Traffic
- Creating a One-to-One NAT Policy for Outbound Traffic
- Inbound Port Address Translation via One-to-One NAT Policy
- Inbound Port Address Translation via WAN IP Address
- Creating a Many-to-One NAT Policy
- Creating a Many-to-Many NAT Policy
- Creating a One-to-Many NAT Load Balancing Policy
- Creating a NAT Load Balancing Policy for Two Web Servers
- Creating a WAN-to-WAN Access Rule for a NAT64 Policy
- DNS Doctoring
- Routing
- Content Filter Rules
- App Rules
- About App Rules
- Rules and Policies > App Rules
- Verifying App Rules Configuration
- App Rules Use Cases
- Creating a Regular Expression in a Match Object
- Policy-based Application Rules
- Logging Application Signature-based Policies
- Compliance Enforcement
- Server Protection
- Hosted Email Environments
- Email Control
- Web Browser Control
- HTTP Post Control
- Forbidden File Type Control
- ActiveX Control
- FTP Control
- Bandwidth Management
- Bypass DPI
- Custom Signature
- Reverse Shell Exploit Prevention
- Endpoint Rules
- SonicWall Support
Adding Static Routes
To add a static route
-
Navigate to the POLICY | Rules and Policies > Route Policy page.
-
Click +Add (in the bottom left corner). The Adding Rule dialog displays.
- Enter a friendly name for this route policy in Name.
- Type a descriptive comment into the Description field and any appropriate Tags.
- Indicate the Type as IPv4 or IPv6.
- In the Lookup tab,
- Select the source address object from Source.
- Select the destination address object from Destination.
- Specify the type of service that is routed from Service or Application.
-
In the Next Hop tab, choose the type of route:
- Standard (default)
- Multi-Path
- SD-WAN
- Select the interface through which these packets are routed from Interface.
- Select the address object that acts as a gateway for packets matching these settings from Gateway.
- Specify the RIP metric in the Metric field.
- Click Add or click to the Advanced tab to continue the configuration.
- Optionally select Disable route when the interface is disconnected.
- Select Allow VPN path to take precedence to allow a matching VPN network to take precedence over the static route when the VPN tunnel is up. This option is not selected by default.
- Enter the ToS hexadecimal value in the TOS (Hex) field.
- Enter the ToS Mask hexadecimal value in the TOS Mask (Hex) field.
- Enter a value for the Admin Distance, or select Auto for an automatically created Admin Distance.
- Click Add or click to the Probe tab to continue the configuration.
- Select a probe type from Probe. The default is None. If a probe type is selected additional options become available.
- Select Disable route when probe succeeds. This option is not selected by default.
- Select Probe default state is UP.
- When you are finished, click Add. The route settings are configured for the selected SonicWall appliance(s).
Was This Article Helpful?
Help us to improve our support portal