<html>
<!--
Public Release 3
$Id: static_stmt.html,v 1.2 1997/07/17 22:40:24 chopps Exp $
------------------------------------------------------------------------
Copyright (c) 1996, 1997 The Regents of the University of Michigan
All Rights Reserved
Royalty-free licenses to redistribute GateD Release
3 in whole or in part may be obtained by writing to:
Merit GateDaemon Project
4251 Plymouth Road, Suite C
Ann Arbor, MI 48105
THIS SOFTWARE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER
EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE REGENTS OF THE
UNIVERSITY OF MICHIGAN AND MERIT DO NOT WARRANT THAT THE
FUNCTIONS CONTAINED IN THE SOFTWARE WILL MEET LICENSEE'S REQUIREMENTS OR
THAT OPERATION WILL BE UNINTERRUPTED OR ERROR FREE. The Regents of the
University of Michigan and Merit shall not be liable for
any special, indirect, incidental or consequential damages with respect
to any claim by Licensee or any third party arising from use of the
software. GateDaemon was originated and developed through release 3.0
by Cornell University and its collaborators.
Please forward bug fixes, enhancements and questions to the
gated mailing list: gated-people@gated.merit.edu.
------------------------------------------------------------------------
Copyright (c) 1990,1991,1992,1993,1994,1995 by Cornell University.
All rights reserved.
THIS SOFTWARE IS PROVIDED "AS IS" AND WITHOUT ANY
EXPRESS OR IMPLIED WARRANTIES, INCLUDING, WITHOUT
LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTABILITY
AND FITNESS FOR A PARTICULAR PURPOSE.
GateD is based on Kirton's EGP, UC Berkeley's routing
daemon (routed), and DCN's HELLO routing Protocol.
Development of GateD has been supported in part by the
National Science Foundation.
------------------------------------------------------------------------
Portions of this software may fall under the following
copyrights:
Copyright (c) 1988 Regents of the University of California.
All rights reserved.
Redistribution and use in source and binary forms are
permitted provided that the above copyright notice and
this paragraph are duplicated in all such forms and that
any documentation, advertising materials, and other
materials related to such distribution and use
acknowledge that the software was developed by the
University of California, Berkeley. The name of the
University may not be used to endorse or promote
products derived from this software without specific
prior written permission. THIS SOFTWARE IS PROVIDED
``AS IS'' AND WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES,
INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
-->
<head>
<TITLE>GateD Configuration Guide - Static Statement</TITLE>
</head>
<body>
<H1>Static Statements</H1>
<code>Static</code> statements define the static routes used by GateD.
A single <CODE>static</CODE> statement can specify any number routes.
The <CODE>static</CODE> statements occur after protocol statements and
before control statements in the gated.conf file. Any number of
<CODE>static</CODE> statements may be specified, each containing any
number of static route definitions. These routes can be overridden by
routes with better preference values.
<pre>
<strong>static</strong> <strong>{</strong>
( <strong>host</strong> <var>host</var> ) | <strong>default</strong> |
( <var>network</var> [ ( <strong>mask</strong> <var>mask</var> ) | ( <strong>masklen</strong> <var>number</var> ) ] )
<strong>gateway</strong> <var>gateway_list</var>
[ <strong>interface</strong> <var><a href="intfcs.html#interface list">interface_list</a></var> ]
[ <strong>preference</strong> <var><a href="pref.html">preference</a></var> ]
[ <strong>retain</strong> ]
[ <strong>reject</strong> ]
[ <strong>blackhole</strong> ]
[ <strong>noinstall</strong> ] <strong>;</strong>
( <var>network</var> [ ( <strong>mask</strong> <var>mask</var> ) | ( <strong>masklen</strong> <var>number</var> ) ] )
<strong>interface</strong> <var>interface</var>
[ <strong>preference</strong> <var><a href="pref.html">preference</a></var> ]
[ <strong>retain</strong> ]
[ <strong>reject</strong> ]
[ <strong>blackhole</strong> ]
[ <strong>noinstall</strong> ] <strong>;</strong>
<strong>}</strong> <strong>;</strong>
</pre>
<dl>
<dt> <strong>host</strong> <var>host</var> <strong>gateway</strong> <var>gateway_list</var>
<dt> ( <var>network</var> [ ( <strong>mask</strong> <var>mask</var> ) | ( <strong>masklen</strong> <var>number</var> ) ] )
<dt> <strong>default</strong> <strong>gateway</strong> <var>gateway_list</var>
<dd> This is the most general form of the static statement. It
defines a static route through one or more gateways. Static
routes are installed when one or more of the <code>gateways</code>
listed are available on directly attached interfaces. If more
than one elligible gateways are available, they are limited by
the number of multipath destinations supported (this compile time
parameter is currently almost always one on Unix).
<p>
Parameters for static routes are:
<dl>
<dt> <strong>interface</strong> <var><a href="intfcs.html#interface list">interface_list</a></var>
<dd> When this paramter is specified, gateways are only
considered valid when they are on one of these
interfaces.See the section on <a
href="intfcs.html#interface list">inteface list</a>
specification for the description of the
<var>interface_list</var>.
<dt> <strong>preference</strong> <var><a href="pref.html">preference</a></var>
<dd> This option selects the preference of this static route.
The preference controls how this route competes with routes
from other protocols. The default preference is 60.
<dt> <strong>retain</strong>
<dd> Normally gated removes all routes except interface routes
from the kernel forwarding table during a graceful shutdown.
The <code>retain</code> option may be used to prevent
specific static routes from being removed. This is useful
to insure that some routing is available when gated is not
running.
<dt> <strong>reject</strong>
<dd> Instead of forwarding a packet like a normal route,
<code>reject</code> routes cause packets to be dropped and
<code>unreachable</code> messages to be sent to the packet
originators. Specifying this option causes this route to be
installed as a reject route. Not all kernel forwarding
engines support reject routes.
<dt> <strong>blackhole</strong>
<dd> A <code>blackhole</code> route is the same as a
<code>reject</code> route except that
<code>unreachable</code> messages are not supported.
<dt> <strong>noinstall</strong>
<dd> Normally the route with the lowest preference is installed
in the kernel forwarding table and is the route exported to
other protocols. When <code>noinstall</code> is specified
on a route, it will not be installed in the kernel
forwarding table when it is active, but it will still be
elligible to be exported to other protocols.
</dl>
<dt> ( <var>network</var> [ ( <strong>mask</strong> <var>mask</var> ) | ( <strong>masklen</strong> <var>number</var> ) ] ) <strong>interface</strong> <var>interface</var>
<dd> This form defines a static interface route which is used for
primitive support of multiple network addresses on one interface.
The <code>preference</code>, <code>retain</code>,
<code>reject</code>, <code>blackhole</code> and
<code>noinstall</code> options are the same as described above.
</dl>
<hr>
Last updated 1995/04/19 18:42:17.
<p><address>gated@gated.cornell.edu</address>
</body>
</html>
