Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!bloom-beacon!apple!vsi1!frame!bugeater.UUCP!tvb
From: tvb@bugeater.UUCP (Terry Bush)
Newsgroups: comp.sys.apollo
Subject: Re: routed -h: why?
Message-ID: <3372@frame.UUCP>
Date: 25 Apr 89 19:27:03 GMT
References: <8904250204.AA24093@umix.cc.umich.edu>
Sender: news@frame.UUCP
Organization: Frame Technology, 2911 Zanker Rd., San Jose, CA 95134-9908
Lines: 20
Phone.......: (408) 954-3900 (Office) "tvb@frame.com (email)"


>    1)  Run /etc/routed (no options) on all systems.  On gateways, routed
>        advertises itself as a gateway;  on non-gateways, routed listens
>        for these messages and updates the routing table accordingly.  When a
>        gateway ceases broadcasting its availability, routed on non-gateways
>        deletes it from the table and adds another route (if it exists)
>        automatically.  This is how we use routed on our Unix systems, and at
>        TCP 3.1 it proved to work on our Apollos as well.


Rick,
  I have come to nearly the same conclusion that you have concerning
  TCP routing.  One exception is that I run routed with the '-q' option
  on all non-gateway nodes.  This assures me (falsely maybe) that those
  hosts do not add to our already loaded network traffic.


	Peace,
	Terry V. Bush
	The Veritable Bugeater