From owner-freebsd-hackers  Wed Sep  4 07:38:49 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id HAA14333
          for hackers-outgoing; Wed, 4 Sep 1996 07:38:49 -0700 (PDT)
Received: from fullfeed.msn.fullfeed.com (fullfeed.msn.fullfeed.com [199.184.182.42])
          by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id HAA14304
          for <hackers@freebsd.org>; Wed, 4 Sep 1996 07:38:30 -0700 (PDT)
Received: from sumatra.americantv.com by fullfeed.msn.fullfeed.com (8.6.9/FF-1.1)
	id JAA05160; Wed, 4 Sep 1996 09:38:13 -0500
Received: (from uucp@localhost) by sumatra.americantv.com (8.6.12/8.6.12) with UUCP id JAA21890; Wed, 4 Sep 1996 09:11:44 -0500
Received: (jlemon@localhost) by right.PCS (8.6.12/8.6.4) id JAA05229; Wed, 4 Sep 1996 09:32:52 -0500
From: Jonathan Lemon <jlemon@americantv.com>
Message-Id: <199609041432.JAA05229@right.PCS>
Subject: Re: can't get to freefall.FreeBSD.org
To: sprice@hiwaay.net (Steve Price)
Date: Wed, 4 Sep 1996 09:32:51 -0500 (CDT)
Cc: hackers@freebsd.org
In-Reply-To: <322D0578.6201DD56@hiwaay.net> from "Steve Price" at Sep 3, 96 11:28:40 pm
X-Mailer: ELM [version 2.4 PL21]
Content-Type: text
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> I know this is not freefall's fault nor does it have anything to
> do with FreeBSD except this blooming router is the reason why I
> can't get to freefall.  I was just wondering if anybody knew of
> anybody that has anything to do with it.  Of course, this message
> will take forever to get posted since this same router has to be
> used and it can't figure out how to route packets to anything
> other than itself right now. :(
> 
> Name:    sl-fw-8-S2/7-T1.sprintlink.net
> Address:  144.228.38.65

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?)
  chicago -> philadelphia -> chicago -> philadelphia
  chicago -> philadelphia -> chicago -> st louis -> dc

I assume that Sprintlink knows about this, as I've bugged my ISP to 
bother them, but it doesn't seem to do much good.
--
Jonathan