Current Document and Section   Other Documents     Documentation     Howtos   User Guide DNS and Domains Gateway Services Guide Release Notes

Howtos - Managing Static Routes

Overview

This document describes how to configure a static route on a ClarkConnect system.

Configuration

Static routes on a ClarkConnect system are associated with a particular network interface. The route is then enabled/disabled when the particular network interface is enabled/disabled. Here is a simple scenario:

• A ClarkConnect LAN interface - eth1 - is configured with a 192.168.1.x network.
• A private building-to-building wireless connection is setup via a wireless router. One side of the wireless router is connected to the ClarkConnect LAN at 192.168.1.100. The other side of the wireless router is connected to a 192.168.99.x LAN.

In order for the ClarkConnect gateway to be aware of the remote 192.168.99.x LAN, a static route must be configured. In this example, /etc/sysconfig/network-scripts/route-eth1 is created with the following:

192.168.99.0/24 via 192.168.1.100

After adding this static route, the route can be activated by re-enabling the ClarkConnect LAN interface: /sbin/ifup eth1. If you are using Multi-WAN, then you also need to restart the firewall: /sbin/service firewall restart.

Additional LAN Networks

If you have other LAN networks connected behind your ClarkConnect gateway, you need to configure these on the ClarkConnect system. In version 4.1, you can add extra networks in /etc/system/network file (create the file if it does not exist). The format is similar to:

EXTRALANS="LAN1 LAN2 ... LANx"

For example:

EXTRALANS="192.168.4.0/24 192.168.5.0/24"

You may need to restart services (for example, the web proxy) after making this change.