From owner-freebsd-announce  Fri May 26 04:58:33 1995
Return-Path: announce-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id EAA23709
          for announce-outgoing; Fri, 26 May 1995 04:58:33 -0700
Received: from asstdc.scgt.oz.au (root@asstdc.scgt.oz.au [202.14.234.65])
          by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id EAA23663
          ; Fri, 26 May 1995 04:55:17 -0700
Received: (from imb@localhost)
	by asstdc.scgt.oz.au (8.6.12/BSD4.4)
	id VAA07277; Fri, 26 May 1995 21:52:33 +1000
From: michael butler <imb@scgt.oz.au>
Message-Id: <199505261152.VAA07277@asstdc.scgt.oz.au>
Subject: Re: Drivers for FORE systems cards under FreeBSD
To: hasty@netcom.com (Amancio Hasty Jr)
Date: Fri, 26 May 1995 21:52:32 +1000 (EST)
Cc: julian@ref.tfs.com, pss@fore.com, announce@FreeBSD.org,
        hackers@FreeBSD.org, phk@ref.tfs.com, rv@fore.com
In-Reply-To: <199505252220.PAA24375@netcom14.netcom.com> from "Amancio Hasty Jr" at May 25, 95 03:20:28 pm
Reply-To: imb@scgt.oz.au
X-Mailer: ELM [version 2.4 PL24beta]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Length: 1256      
Sender: announce-owner@FreeBSD.org
Precedence: bulk

Amancio Hasty Jr writes:

> No promises over here but I am going to try to remedy the ATM situation.
> Nor I am going to state who am I going to be dealing with .

Much as I hate generalisations .. I would warn that ATM and IP apparently do
not mix well in cases where good interactive response is critical, at least
in my limited experience. I get better response over my own overworked 14k4
modem connection to the net than over a (university based) 2 megabit ATM
link.

Taking simple icmp echo (ping) as a guide to find out why, on my modem link
I get round-trip times of ~600mS to the US .. over ATM, they start at 7
seconds and take some time before dropping to a more acceptable 160mS. When
typing in a telnet session, this equates to .. leave the keyboard alone for
any period greater than one or two seconds and you're back to that 7 second
latency.

It's unusable as currently implemented for anything but bulk-haulage of
video and news. I don't know the unlying technical details but, based on
this experience, I'm not entirely sure I want to.

However, if this is an implementation specific problem, I would be very glad
to hear how it might be resolved .. it's near impossible for me to do
assignments by telecommuting these days :-(

	michael