<html>
<!--
Public Release 3
$Id: samp_host.html,v 1.2 1997/07/17 22:40:18 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>Sample Host Configurations</title>
</head>
<body>
<H2>Sample Host Configurations</H2>
<P>End system configuration is simple, usually containing only two
configuration statements. The configuration shown here emulates
<CODE>routed</CODE>. It runs RIP, and it only sends updates if there
is more than one interface up and IP forwarding is enabled in the
kernel.
<P><PRE>
#
rip yes ;
#
</PRE>
<P>Note: RIP will not run if UDP checksums are disabled in the
kernel.
<P>This configuration runs RIP in quiet mode; it only listens to packets,
no matter how many interfaces are configured.
<P><PRE>
#
rip yes ;
{
nobroadcast ;
} ;
#
</PRE>
<P>This configuration should work for any system that runs RIP and has only
one network interface.
<P><PRE>
#
# don't time-out the network interface
#
interface 136.66.12.2 passive ;
#
# enable rip
#
rip yes ;
#
</PRE>
<P>(SWB: Is this correct now? JC)
<P>The keyword passive prevents GateD from changing the preference of the
route to this interface if it is believed to be down due to lack of
received routing information. The purpose of the interface passive
statement is to identify a router with a guest host on an Ethernet. In
this example the route is through the directly attached network interface.
Normally when GateD thinks an interface is down, it removes it from the
routing database to prevent a gateway from announcing that it can route
data through a non-operational interface. If the host has only one
interface, it should not be removed from the routing database even if the
interface is down i.e. the statement interface 136.66.12.2 passive in this
configuration. RIP is enabled with a rip yes statement. This statement is
not required as it is the default but the explicit statement in the
gated.conf file serves to document the configuration preventing future
confusion.
<hr>
Last updated 1994/03/15 19:41:17.
<p><ADDRESS>gated@gated.cornell.edu</ADDRESS>
</body>
</html>
