RuggedRouter User Guide
The Network/Host and Netmask fields describe the remote network the static route
will reach. If the netmask field is not entered (or a netmask of 255.255.255 is
entered) the routing will define a host route. Any other netmask will define a
network route. If the network field is cleared the route will be deleted upon the next
save.
The Gateway field describes an address that is used as the next hop to forward traffic
to. If this field is not specified than traffic is forwarded to the Interface.
The Interface field describes the network interface this static route will use. The
interface does not need to be active or even exist, but the route will not be installed
until both are true. You do not need to provide an interface, but doing so will cause
the menu to warn you if the gateway is not owned by the interface. The menu
provides a list of currently configured interfaces for your convenience.
The Metric field specifies an integer cost metric for the route, which is used when
choosing among multiple routes in the routing table that most closely match the
destination address of a packet being forwarded. The route with the lowest metric is
chosen.
The Comment field shows the status of the static route, and provides a basic cause
when the route is not installable.
The Save button below the table will save the routes and immediately install them.
The following sanity checks will be made for static routes:
•The Net mask ca n not b e 0.0.0 .0.
•If the interfa ce is a ctive th e stat ic route will be insta lled, i f it ca n not be
install ed, it will be treate d as il legal.
•A routings Gateway address must be owned by the routings interface.
Delete routes by removing their Network/Host addresses before saving.
Manually Entered St atic Routes
This table will be shown if there are active static routes which are not in the
Configured Static Routes table. Following a routes “Save to Configured Static
Routes” link will make the route permanent.
Note: T here are s ituations where man ually ente red route s should n ot be con verted, e.g. rou tes dynami cally add ed by IPse c and GRE tunnels. Making th ese route s permanen t may caus e the dae mons that add them t o fail.
52 RuggedCom