From owner-freebsd-isp  Mon Jan 27 07:30:14 1997
Return-Path: <owner-isp>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id HAA10129
          for isp-outgoing; Mon, 27 Jan 1997 07:30:14 -0800 (PST)
Received: from irvine.americasnet.com (ricardo@irvine.americasnet.com [208.145.128.2])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA10123
          for <freebsd-isp@freebsd.org>; Mon, 27 Jan 1997 07:30:08 -0800 (PST)
Received: from localhost (ricardo@localhost) by irvine.americasnet.com (8.8.3/8.7.3) with SMTP id HAA21397; Mon, 27 Jan 1997 07:31:05 -0800
Date: Mon, 27 Jan 1997 07:31:05 -0800 (PST)
From: Ricardo Kleemann <ricardo@americasnet.com>
To: Steve Khoo <steve@gordian.com>
cc: freebsd-isp@freebsd.org
Subject: Re: Comment on CRL Network Services please.
In-Reply-To: <unu3o6af6i.fsf@ares.gordian.com>
Message-ID: <Pine.LNX.3.95.970127072900.21211B-100000@irvine.americasnet.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-isp@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

I don't use CRL directly, but I do have a secondary connection, with
Ironlight Digital, which utilizes CRL.

My experience has NOT been very good. However this is a Fram Relay
connection I'm talking about; maybe their pt-to-pt network is better.
However, I've experienced a LOT of routing problems and packet loss in the
past... It's definitely been annoying. :(



On 24 Jan 1997, Steve Khoo wrote:

> We are contemplating switching over to CRL for T1 access.  If
> you have any dealings with them please comment.  How about that CRL's
> LAP service?
> 
> Thanks!
> 
> SEK
>