Static Route Example - NETGEAR ProSafe FVG318 Reference Manual

Reference Manual for the ProSafe Wireless 802.11g VPN Firewall Model FVG318
2. Type a route name for this static route in the Route Name box.
(This is for identification purpose only.)
3. Select Private if you want to limit access to the LAN only. The static route will not be reported
in RIP.
4. Select Active to make this route effective.
5. Type the Destination IP Address of the final destination.
6. Type the IP Subnet Mask for this destination.
If the destination is a single host, type 255.255.255.255.
7. Type the Gateway IP Address, which must be a firewall on the same LAN segment as the
firewall.
8. Type a number between 1 and 15 as the Metric value.
This represents the number of firewalls between your network and the destination. Usually, a
setting of 2 or 3 works, but if this is a direct connection, set it to 1.
9. Click Apply to have the static route entered into the table.

Static Route Example

As an example of when a static route is needed, consider the following case:
• Your primary Internet access is through a cable modem to an ISP.
• You have an ISDN firewall on your home network for connecting to the company where
you are employed. This firewall's address on your LAN is 192.168.1.100.
• Your company's network is 134.177.0.0.
When you first configured your firewall, two implicit static routes were created. A default route
was created with your ISP as the gateway, and a second static route was created to your local
network for all 192.168.0.x addresses. With this configuration, if you attempt to access a device on
the 134.177.0.0 network, your firewall will forward your request to the ISP. The ISP forwards your
request to the company where you are employed, and the request will likely be denied by the
company's firewall.
In this case you must define a static route, telling your firewall that 134.177.0.0 should be accessed
through the ISDN firewall at 192.168.1.100. The static route would look like
9-6.
In this example:
• The Destination IP Address and IP Subnet Mask fields specify that this static route applies to
all 134.177.x.x addresses.
Advanced Configuration
v1.0, October 2005
Figure 9-3 on page
9-7