Browse All Articles > Network Traffic Routing in Sonicwall
Network traffic routing plays key role in your network, if you have single site with heavy browsing or multiple sites, replicating important application data from your Primary Default Gateway ,you have to route your other network traffic from your primary gateway to secondary gateway.
This article will step through configuring static routes in your SonicWALL Network Appliance to route HTTP / HTTPS or any specific traffic to Secondary Default Gateway. This article applies all SonicWALL Network Appliance supporting Sonicwall Enhance OS.
This article assumes that you have Two (2) ISP, and both connected to your Sonicwall Appliance via ISP Modem/Router.
NOTE: It is assumed that both WAN connection are configured and active.
HTTP Rule :
Login to the SonicWALL Network Appliance and go to Network >Routing > Add (refer to Figure 1) >
Source: LAN Subnet or Any
Destination: Any
Service: HTTP
Gateway: Secondary Default Gateway
Interface: X2
Metric: 20
Comment: HTTP Route
(Optional) Select the Disable route when the interface is disconnected checkbox to have the route automatically disabled when the interface is disconnected. i Recomend to CHECK this BOX.
(Optional) The Allow VPN path to take precedence.I Recomend to leave this box UN-CHECKED.
HTTPS Rule :
Login to the SonicWALL Network Appliance and go to Network >Routing > Add (refer to Figure 2) >
Source: LAN Subnet or Any
Destination: Any
Service: HTTPS
Gateway: Secondary Default Gateway
Interface: X2
Metric: 20
Comment: HTTPS Route
Once both rules created you can also verify, logon to your SonicWALL Network Appliance> Network >Routing. you will be able to see new created rules (refer to Figure 3)
You can create as many rules as you want, if you have two or three ISP i would strongly suggest you to route trraffic on Multiple ISP. Custom routes can also be created for IT staff Downloading or Uploading Data.
Figure-1.png
Figure-2.png
Figure-3.png
This article will step through configuring static routes in your SonicWALL Network Appliance to route HTTP / HTTPS or any specific traffic to Secondary Default Gateway. This article applies all SonicWALL Network Appliance supporting Sonicwall Enhance OS.
This article assumes that you have Two (2) ISP, and both connected to your Sonicwall Appliance via ISP Modem/Router.
NOTE: It is assumed that both WAN connection are configured and active.
HTTP Rule :
Login to the SonicWALL Network Appliance and go to Network >Routing > Add (refer to Figure 1) >
Source: LAN Subnet or Any
Destination: Any
Service: HTTP
Gateway: Secondary Default Gateway
Interface: X2
Metric: 20
Comment: HTTP Route
(Optional) Select the Disable route when the interface is disconnected checkbox to have the route automatically disabled when the interface is disconnected. i Recomend to CHECK this BOX.
(Optional) The Allow VPN path to take precedence.I Recomend to leave this box UN-CHECKED.
HTTPS Rule :
Login to the SonicWALL Network Appliance and go to Network >Routing > Add (refer to Figure 2) >
Source: LAN Subnet or Any
Destination: Any
Service: HTTPS
Gateway: Secondary Default Gateway
Interface: X2
Metric: 20
Comment: HTTPS Route
Once both rules created you can also verify, logon to your SonicWALL Network Appliance> Network >Routing. you will be able to see new created rules (refer to Figure 3)
You can create as many rules as you want, if you have two or three ISP i would strongly suggest you to route trraffic on Multiple ISP. Custom routes can also be created for IT staff Downloading or Uploading Data.
Figure-1.png
Figure-2.png
Figure-3.png
Have a question about something in this article? You can receive help directly from the article author. Sign up for a free trial to get started.
Comments (4)
Commented:
we can achive this by using load balance in sonicwall?? why we will craete static routes?
Author
Commented:Thank you for your commets, actually there is a big difference. lets take one example
Customer has a two office, One is HO and other is DR, both connected via VPN and you have 2 ISP connection @ your HO
ISP A-----Leased line----6MB UP/Down
ISP B-----ADSL Line-----512/KB UP / 10MB Down
Customer is using ISP for Mail server, Mail CCR replication to DR, Application replicating to DR or SAN to SAN replication to DR location via 6MB line and he doest not want to use this line @ the same time he want to use this line as a backup if both ADSl fails.
so the solution is to route HTTP, HTTPS, FTP traffic to Secondary default gateway and @ the same time you can enjoy load blance on Primary and Secondary Gateway.
once you will route traffic in normal case the route will go to Secondary gateway and wil not consume your primary gateway bandwidth. but once Secondary GW fails the primary will act on request.
Commented:
Commented:
A client system needed to connect to a secured site with session control. The session was managed probably via a cookie that recorded the referrer IP address.
With load balancing the browser was being directed through both ISP connections and each time the router switched the user would lose her session forcing her to log in again. Within minutes her session was lost yet again because of the load balancing.
I had to create a static route directing all traffic to that particular site through a specific interface.