From owner-freebsd-questions  Thu Sep 26 11:30:35 1996
Return-Path: owner-questions
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id LAA04986
          for questions-outgoing; Thu, 26 Sep 1996 11:30:35 -0700 (PDT)
Received: from agora.rdrop.com (root@agora.rdrop.com [199.2.210.241])
          by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id LAA04962
          for <freebsd-questions@FreeBSD.org>; Thu, 26 Sep 1996 11:30:32 -0700 (PDT)
Received: from pcnet1.pcnet.com by agora.rdrop.com with smtp
	(Smail3.1.29.1 #17) id m0v6LCf-00092MC; Thu, 26 Sep 96 11:30 PDT
Received: by pcnet1.pcnet.com (4.1/SMI-4.1)
	id AB24484; Thu, 26 Sep 96 14:21:48 EDT
Date: Thu, 26 Sep 96 14:21:48 EDT
From: eischen@vigrid.com (Daniel Eischen)
Message-Id: <9609261821.AB24484@pcnet1.pcnet.com>
To: freebsd-questions@FreeBSD.org
Subject: Sprints response to to wcarchive connectivity problems
Sender: owner-questions@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk


I've been having problems with connectivity to wcarchive.  It's happened
quite a few times in the past, and I've noted all the responses saying
it's Sprints problem.  I finally got tired of dealing with thesse
transient problems, so I started complaining to my ISP and his Sprint 
representative.

Here is Sprints response (in my ISPs words).  While this may be the cause
of recent problems (last week or so), is it representative of most of
the other Sprint connectivity problems?

  "cdrom.com's provider, crl.com, is connected to the internet via a
  non-approved poor router. The router is hosing causing flapping problems.
  This is also due to the fact that crl does not properly peer. In other
  words, crl and therefore crl's customer is not holding up to acceptable use
  policies. The destination is deliberately blocked when the router flaps so
  as to prevent flapping throughout the network."


Dan Eischen
eischen@pcnet.com