Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!decvax!decwrl!pyramid!pesnta!hplabs!hp-sdd!ncr-sd!sdcsvax!ucbvax!SRI-SPAM.ARPA!gds
From: gds@SRI-SPAM.ARPA.UUCP
Newsgroups: mod.protocols.tcp-ip
Subject: Re: The Big Bug?
Message-ID: <8605231710.AA22915@sri-spam.arpa>
Date: Fri, 23-May-86 13:10:34 EDT
Article-I.D.: sri-spam.8605231710.AA22915
Posted: Fri May 23 13:10:34 1986
Date-Received: Sat, 24-May-86 19:30:04 EDT
References: <8605230539.AA00758@ucbvax.Berkeley.EDU>
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 15
Approved: tcp-ip@sri-nic.arpa

> What do hosts do when they are redirected via a "gateway" that is not
> on their directly-connected net?

4.2 hosts running BBN TCP/IP ignore redirects from gateways which are
not on their directly attached net.  In addition, there is a notion of
the "connected set of gateways" which are allowed to send redirects to
the host.  It starts with the "default" gateway, installed by the system
manager.  The default gateway may redirect the host to another gateway
if there is a better route, and any other gateways put in the routing
tables from similar redirects may do likewise.  A gateway which has not
been "installed" from previous redirects cannot redirect the host -- in
fact the code is commented "Who are you, and why are you talking to us,
and how do we know the IP source is not a lie?"

--gregbo