From owner-freebsd-hackers  Wed Sep  4 11:38:41 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id LAA26143
          for hackers-outgoing; Wed, 4 Sep 1996 11:38:41 -0700 (PDT)
Received: from brasil.moneng.mei.com (brasil.moneng.mei.com [151.186.109.160])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA26133
          for <hackers@FreeBSD.org>; Wed, 4 Sep 1996 11:38:38 -0700 (PDT)
Received: (from jgreco@localhost) by brasil.moneng.mei.com (8.7.Beta.1/8.7.Beta.1) id NAA13520; Wed, 4 Sep 1996 13:37:00 -0500
From: Joe Greco <jgreco@brasil.moneng.mei.com>
Message-Id: <199609041837.NAA13520@brasil.moneng.mei.com>
Subject: Re: can't get to freefall.FreeBSD.org
To: jlemon@americantv.com (Jonathan Lemon)
Date: Wed, 4 Sep 1996 13:37:00 -0500 (CDT)
Cc: sprice@hiwaay.net, hackers@FreeBSD.org
In-Reply-To: <199609041432.JAA05229@right.PCS> from "Jonathan Lemon" at Sep 4, 96 09:32:51 am
X-Mailer: ELM [version 2.4 PL24]
Content-Type: text
Sender: owner-hackers@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

> Sprintlink is basically your problem.  Sprintlink appears to have their 
> collective thumbs up you know where, and can't figure out how to
> reliably keep their routers working.   I have the misfortune to be linked
> with them to freefall, and have variously seen the following routes
> over the last few months:
> 
>   chicago1 -> chicago2 -> chicago1 -> chicago2  	(chicago loop?)

Yes :-)  Your packet in a holding pattern...  it's the ONLY fast transit
around the Loop  ;-)

>   chicago -> philadelphia -> chicago -> philadelphia

Hey don't whine, you got out of Chicago for a bit...

>   chicago -> philadelphia -> chicago -> st louis -> dc

Wow!

Usually I see Chi-Chi-Chi-Chi-Chi problems.  :-(  I've rarely seen it
route anywhere else when it gets broken...  you are lucky indeed.

... JG