Received: from SOUTH-STATION-ANNEX.MIT.EDU by po7.MIT.EDU (5.61/4.7) id AA16291; Sat, 24 Feb 96 19:59:57 EST
Received: from pain.lcs.mit.edu by MIT.EDU with SMTP
	id AA22849; Sat, 24 Feb 96 19:59:26 EST
Received: (from daemon@localhost) by pain.lcs.mit.edu (8.6.12/8.6.12) id QAA08363; Sat, 24 Feb 1996 16:13:39 -0500
Received: from boogers.sf.ca.us by pain.lcs.mit.edu (8.6.12/8.6.12) with ESMTP id PAA08085; Sat, 24 Feb 1996 15:55:30 -0500
Received: (from riz@localhost) by boogers.sf.ca.us (8.7.3/8.6.12) id MAA01769; Sat, 24 Feb 1996 12:40:51 -0800 (PST)
From: the Riz <riz@boogers.sf.ca.us>
Message-Id: <199602242040.MAA01769@boogers.sf.ca.us>
Subject: Re: Please read this. (Re: SUP and FTP errors)
To: hvozda@netcom.com (Eric S. Hvozda)
Date: Sat, 24 Feb 1996 12:40:50 -0800 (PST)
Cc: scottr@plexus.com, current-users@NetBSD.ORG, netbsd-help@NetBSD.ORG,
        jules@mailbox.co.uk
In-Reply-To: <9602232124.AA30586@lexington.liris.loral.com> from "Eric S. Hvozda" at Feb 23, 96 04:24:31 pm
X-Mailer: ELM [version 2.4 PL24]
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-netbsd-help@NetBSD.ORG
Precedence: list
X-Loop: netbsd-help@NetBSD.ORG

You wrote:

> On Fri, 23 Feb 1996 11:13:52 -0600 (CST)  scottr@plexus.com wrote:
> > It was determined some time ago problems with a certain router between
> > many hosts on the West Coast of the US and the rest of the world.  If you
> > happen to be fortunate enough to have your traffic go through this router,
> > it will eventually choke on a "magic bit pattern" that _will_ get
> > corrupted.  (This problem affects Netcom, as well, by the way... a site
> > that undoubtably gets far more traffic.)

> Ah, but people expect this kind of lossage from Netcom.  Well at least I have
> as a subscriber.  It's sad that this problem persists and yet the people
> who own the hardware haven't corrected it yet :-(

Hey!  As pointed out in another mail, the problem appears to exist in a
NetEdge at another ISP.  The *really* bad problems which we were
experiencing before was the result of data corruption on mae-west which
affected a *lot* more than just NetBSD.org and NETCOM.  Plus, I believe
(I'm not certain of this) that Best had a problem with their NetEdge as
well.

Disclaimer:   in my other life, I work for NETCOM.

-- 
Jeff Rizzo                                         http://boogers.sf.ca.us/~riz
riz@boogers.sf.ca.us
