This article explains how to route the Internet traffic for a specific IP or subnet to use the secondary WAN.
If you would like to configure WAN Failover, the article is: How to configure Failover when there are two or more WAN Interfaces?
Static Routes are used to push traffic to the right gateway device/interface. When a SonicWall has two or more Internet Service Provider WAN Links, and you want to force only certain IP Addresses or types of traffic through one specific ISP, you must create a policy-based route to push that traffic as per requirement.
Let's consider WAN X1 as the Primary and WAN X2 as the Secondary ISP. There is a new subnet on X3. The requirement is that all devices on the X3 subnet should use the secondary WAN X2. The same steps can be used if instead of a subnet, you only need a specific IP or group of IPs.
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.
CAUTION: Remember when creating a Route that it will take effect immediately. Always make sure to have your Gateway and Interface set properly to avoid problematic routing.
---- Route with custom address group
NOTE: The Metric field refers to what weight this Route should have. The lower metric is a higher priority. In this example, we've chosen 10.
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.
CAUTION: Remember when creating a Route that it will take effect immediately. Always make sure to have your Gateway and Interface set properly to avoid problematic routing.
NOTE: The Metric field refers to what weight this Route should have. The lower metric is a higher priority. In this example, we've chosen 10.