#
# Public Release 3
#
# $Id: rip.slip,v 1.2 1997/07/17 22:39:34 chopps Exp $
#

I use these to configuration files for the slip link to my house.  The
first runs on the server and generates a static route to my network at
home (192.107.121).  The `interface du slip' parameters on the static
route for 192.107.121 require that the static route only exist when
the route to 132.236.200.19 is via an du* or slip* interface.  Since
132.236.200.19 is within the address range of the local ethernet
(132.236.200/255.255.255) this prevents the route from being generated
when the SLIP link is not up.

I keep a little bit of logging around, but limit it to 200k (100k in 2
files).

Jeff


#

tracefile "/var/tmp/gated.log" replace size 100k files 2;
traceoptions general route kernel update icmp ;

interfaces {
	interface all passive ;
} ;

snmp yes ;

rip yes {
#	broadcast ;
	interface all version 2 broadcast ;
	interface le1 metricin 2 ;
	trustedgateways 132.236.200.1 132.236.200.200 132.236.199.1 132.236.199.200 132.236.200.19;
} ;

static {
	default gateway 132.236.199.1 preference 150 retain ;
#	default gateway 128.253.205.2 retain ;
	192.107.121 gateway 132.236.200.19 interface du slip ;
} ;

export proto rip {
	proto static {
		192.107.121 metric 2 ;
	} ;
} ;


At home I just install a static default route to the SLIP server.  I
take advantage of the fact that static routes will only be installed
to gateways on interfaces that are up to make sure the static default
route gets install to the gateway I'm actually using.  This is
actually not necessary in my case as my SLIP software automatically
installs a defaur me.


rip no {
	nobroadcast ;
	interface du noripout ;
} ;

static {
	default gateway 132.236.200.25 132.236.200.38 preference 100 retain ;
} ;

