Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!tut.cis.ohio-state.edu!ucbvax!VAX.FTP.COM!jbvb
From: jbvb@VAX.FTP.COM (James Van Bokkelen)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: Default routes in PC/TCP
Message-ID: <9002161940.AA27317@vax.ftp.com>
Date: 16 Feb 90 19:40:04 GMT
References: <9002161739.AA20965@alw.nih.gov>
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 22


   From: Roger Fajman <RAF@cu.nih.gov>
   Date:     Fri, 16 Feb 90  12:41:35 EST

   .... The upcoming Gateway Discovery protocol should
   be the ultimate solution to this, but in the meantime it would be
   helpful if PC/TCP were able to listen to RIP broadcasts for a default
   route only.  Configuring multiple default routes would also be useful,
   but requires changing everyone's configuration if you add another
   router.

When the group working on the Host Requirements RFC discussed
eavesdropping routing protocols, I was on the side that said "SHOULD
NOT".  I am keeping track of the GW Discovery effort, and given the
most recent draft of the proposal, it should be simple to add.
Multiple routers in the configuration should be in the next major
release of PC/TCP in any case, and in the present version you can use
BOOTP (via the RFC 1048 extensions) to set the single default router
we presently support.

James B. VanBokkelen		26 Princess St., Wakefield, MA  01880
FTP Software Inc.		voice: (617) 246-0900  fax: (617) 246-0901