Date: Fri, 27 Sep 1996 07:55:30 -0400 (EDT) From: "Jason T. Nelson" <jason@purcell.jlc.net> To: eischen@vigrid.com (Daniel Eischen) Cc: freebsd-questions@FreeBSD.org Subject: Re: Sprints response to to wcarchive connectivity problems Message-ID: <199609271155.HAA17969@purcell.jlc.net> In-Reply-To: <9609261821.AB24484@pcnet1.pcnet.com> from Daniel Eischen at "Sep 26, 96 02:21:48 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
> 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." That's mostly crap on your ISP's part (or maybe Sprint, I'm more inclined to think that). There is no such thing as a non-approved router; it probably means that CRL is not using the same piece of crap Cisco's Sprint uses (and good for them for bucking the trend). As for holding up to acceptable use policies, this is utter nonsense as well, but if you were to try to make sense of what they are saying, Sprint may be the WORST offender with some of their practices. -- Jason T Nelson <jason@jlc.net>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199609271155.HAA17969>