Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 alpha 4/15/85; site ucbvax.ARPA
Path: utzoo!watmath!clyde!burl!ulysses!ucbvax!tcp-ip
From: tcp-ip@ucbvax.ARPA
Newsgroups: fa.tcp-ip
Subject: Gateway re-directs.
Message-ID: <8581@ucbvax.ARPA>
Date: Fri, 28-Jun-85 09:29:02 EDT
Article-I.D.: ucbvax.8581
Posted: Fri Jun 28 09:29:02 1985
Date-Received: Sat, 29-Jun-85 03:14:26 EDT
Sender: daemon@ucbvax.ARPA
Organization: University of California at Berkeley
Lines: 23

From: hsw@TYCHO.ARPA    (Howard Weiss)

I have recently seen some strange behavior from the core gateways that
I cannot understand or resolve.

While receiving mail from BRL-TGR (and acking that mail), my host (TYCHO -
26.0.0.57) did not have the BRL gateway defined in its table.  This meant
that all packets for BRL-TGR were sent, by default, to the "smart" gateway
otherwise known as the MIL-ARPA mail bridge gateway (26.0.0.106).
Immediately, MIL-ARPA sent redirects back.  One would normally think that
the gateway would redirect to the BRL gateway (26.3.0.29), since that is the
shortest path, but, that is NOT what happened.

Instead, the MIL-ARPA gateway sent redirects to the MINET gateway
(26.1.0.40).  The MINET gateway, in turn, then sent back redirects to the
BRL gateway.

Does anyone have any good words or reasonings for this behavior?  It would
seem to me that MIL-ARPA should have redirected to the BRL gateway
immediately.

Howard Weiss
-------