UTM: How to Configure Static Routes in SonicOS (Standard and Enhanced)
Page 1 of 4
Home
Welcome Guest | Log In | Unread Messages : 0
E-mail
Print
Subscribe ?
Related
Bookmark
Search
View all items in: UTM/Firewall/VPN > 1.3 Network > Routing UTM/Firewall/VPN > 2.8 Other Documents > Technical Notes
Rating: 8.46 out of 10 (11 Ratings) Rate
Question/Topic
UTM: How to Configure Static Routes in SonicOS (Standard and Enhanced)
Answer/Article
Article Applies To:
SonicWALL Security Appliance Platforms: Gen5: NSA E8500, NSA E7500, NSA E6500, NSA E5500, NSA 5000, NSA 4500, NSA 3500, NSA 2400, NSA 2400MX, NSA 240 Gen4: PRO series: PRO 5060, PRO 4100, PRO 4060,PRO 3060, PRO 2040, PRO 1260 TZ series: TZ 210, TZ 210 Wireless, TZ 190, TZ 190 W, TZ 180, TZ 180 W, TZ 170, TZ 170 W, TZ 170 SP, TZ 170 SP Wireless, TZ 150, TZ 150 W, TZ 150 Wireless (RevB) Gen3: PRO series: PRO 330, PRO 300, PRO 230, PRO 200, PRO 100 SOHO3/TELE3/GX series: SOHO TZW, SOHO3, TELE3, TELE3 SP, TELE3 TZ, TELE3 TZX, GX 650, GX 250 Firmware versions: All Gen5 and Gen4 firmware versions (SonicOS Standard and Enhanced) Gen3 SonicWALL firmware version 6.5.x.x and later Services: Routing - Static Routes
Overview / Scenario:
If you have routers on your interfaces and if you want to access the computers attached to the router, you need to configure static routes on the SonicWALL security appliance on the Network > Routing page. The static route policies will create static routing entries that make decisions based upon source address, source netmask, destination address, destination netmask, service, interface, gateway and metric.
[Link]
22-01-2012
UTM: How to Configure Static Routes in SonicOS (Standard and Enhanced)
Page 2 of 4
In the above example: a NAT-enabled SonicWALL UTM appliance is configfured with a LAN IP of [Link] / [Link] and the computers on the LAN network are on the similar IP range. The IP address of the local router is [Link] /24 with the Gateway IP as [Link], which connects to another network numbered 10.10.20.x
Procedure:
Configuring Static Routes on Firmware 6.x Configuring Static Routes on SonicOS Standard Configuring Static Routes on SonicOS Enhanced
Configuring Static Routes on Firmware 6.x
In Firmware 6.X, this configuration is performed on the Advanced > Routes page. Destination network: [Link] Subnet mask: [Link] Gateway: [Link] Link: LAN
Configuring Static Routes on SonicOS Standard
1. Login to the SonicWALL Management Interface 2. Select Network > Routing > Add Static Route.
[Link]
22-01-2012
UTM: How to Configure Static Routes in SonicOS (Standard and Enhanced)
Page 3 of 4
3. 4. 5. 6. 7.
Specify the Destination Network [Link] Specify the Subnet Mask [Link] Specify the Default Gateway [Link] Specify the interface as LAN (also known as X0). Click OK to update the settings.
Configuring Static Routes on SonicOS Enhanced
1. Login to the SonicWALL Management Interface 2. Select Network > Routing > click Add button.
3. Select the following Route Policy Settings: - Source = Any - Under Destination = specify Create New Address Object. Enter a name for the static route.
[Link]
22-01-2012
UTM: How to Configure Static Routes in SonicOS (Standard and Enhanced)
Page 4 of 4
Specify the Specify the Specify the Specify the Click OK.
Zone Assignment as LAN. Type as Network. IP Address [Link]. Netmask [Link]
- Service = Any - Under Gateway = specify Create New Address Object. Enter a name for the local router. Specify the Zone Assignment as LAN. Specify the Type as Host. Specify the IP Address [Link]. (i.e Route IP on X0) Click OK. - Specify the interface as LAN. - Specify the metric as 1. - Click OK.
Notes:
The destination network and mask must define a logical subnet which doesn't overlap the LAN subnet. The gateway must be local to the LAN. The router at [Link] must have a default route pointing to the firewall's LAN IP address ([Link]) for the secondary subnet to be able to access the internet through the SonicWALL's connection. You can also establish static routes for the WAN, DMZ and additional interfaces as applicable, but only if the gateway router involved is a second router, not the main WAN Gateway router, for which you will not need static routes.
Related Items
UTM: IPSpoof dropped messages in the SonicWALL Log. Archived -- UTM: Configuring Multiple WAN Subnets Using Static ARP with SonicOS Enhanced Archived -- SonicOS: The log shows "IPSpoof Messages". UTM: How to route only SMTP traffic through a specific interface (e.g. Secondary WAN)
KBID Date Modified Date Created
3559 10/29/2010 10/17/2007
[Link]
22-01-2012