Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!ucsd!ucbvax!BBN.COM!satlas
From: satlas@BBN.COM
Newsgroups: comp.protocols.tcp-ip
Subject: Re: [Alan Larson: routing - very strange stuff]
Message-ID: <8909061704.AA10826@ucbvax.Berkeley.EDU>
Date: 6 Sep 89 15:28:12 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 31

Alan,

 Can you tell me why SRI-GW.ARPA is forwarding the echo requests to
three different Mailbridges within a very short period of time?  Is
SRI-GW.ARPA running some form of loadsharing?  The Mailbridges do not
control the choice of the next hop for SRI-GW.ARPA, but can just offer
reachability information via EGP.  From the traceroute information it
appears that the Mailbridges are receiving the ICMP packets and
forwarding them to the proper destination.

Regards,
Stephen

Unrelated note:  From the traceroute information Alan forwarded the 
round trips from the west coast to the east coast appear very good.

             Truncated version of previous message.
-----------------------------------------------------------------

>  IP routing has become more and more of a concern to many of us,
>as routes become stranger and stranger.  Earlier this morning, we
>were unable to find any routes to milnet.  Just now, I tried again,
>and found that the route is, to say the least, a bit strange.


>traceroute to NIC.DDN.MIL (26.0.0.73), 30 hops max, 38 byte packet
> 1: 128.18.10.254 (128.18.10.254)  10 ms  10 ms  0 ms
> 2: SRI-GW.ARPA (128.18.1.1)  10 ms  10 ms  10 ms
> 3: RESTON-DCEC-MB.DDN.MIL (10.6.0.20)  150 ms MARINA-DEL-REY-MB.DDN.MIL
>    (10.6.0.22)  130 ms MCLEAN-MB.DDN.MIL (10.3.0.111)  310 ms
> 4: NIC.DDN.MIL (26.0.0.73)  260 ms  440 ms  250 ms