Received: from SOUTH-STATION-ANNEX.MIT.EDU by po7.MIT.EDU (5.61/4.7) id AA09558; Fri, 29 Sep 95 22:32:46 EDT
Received: from SUN-LAMP.PC.CS.CMU.EDU by MIT.EDU with SMTP
	id AA20442; Fri, 29 Sep 95 22:32:18 EDT
Received: from pain.lcs.mit.edu (pain.lcs.mit.edu [128.52.46.239]) by sun-lamp.pc.cs.cmu.edu (8.6.11/8.6.10) with ESMTP id WAA00777; Fri, 29 Sep 1995 22:32:21 -0400
Received: (from daemon@localhost) by pain.lcs.mit.edu (8.6.9/8.6.9) id KAA06406; Fri, 29 Sep 1995 10:07:05 -0400
Received: from bart.datastorm.com by pain.lcs.mit.edu (8.6.9/8.6.9) with ESMTP id KAA05984 for <netbsd-help@NetBSD.ORG>; Fri, 29 Sep 1995 10:01:32 -0400
Received: from ms-mail.datastorm.com (dsusmail.dsus.datastorm.com) by bart.datastorm.com with SMTP
	(1.37.109.16/16.2) id AA258883909; Fri, 29 Sep 1995 09:11:49 -0500
Received: by ms-mail.datastorm.com with Microsoft Mail
	id <306C189B@ms-mail.datastorm.com>; Fri, 29 Sep 95 09:02:35 PDT
From: John Maier <JohnAM@datastorm.com>
To: "'netbsd-help'" <netbsd-help@NetBSD.ORG>
Subject: Why is SLIP so slow on a dial up, but fast on a direct connect?
Date: Fri, 29 Sep 95 09:07:00 PDT
Message-Id: <306C189B@ms-mail.datastorm.com>
Encoding: 35 TEXT
X-Mailer: Microsoft Mail V3.0
Sender: owner-netbsd-help@NetBSD.ORG
Precedence: list
X-Loop: netbsd-help@NetBSD.ORG


I've a external Supera 28.8 off of my server (486DX2-66, 8megs, 16550   
UART) with the port set to 38400. I am connecting to the server with   
another Supera 28.8.

I have noticed a strange thing, if I directly connect to the server with   
a serial line, I can get outstanding transfer rates.  When I replace the   
line with the modem and dial up (from a PC running Trumpet, or anything   
else), the rates are terrible (lots of pauses from the server).

I tried turning off compression, and error corrections, but this didn't   
really help.

Some the things I notice are, if the link is left idle for a moment and   
then a FTP xfer is started, initially the rate is fairly quick (2800   
bytes/sec) and begins quickly to drop to 400 bytes/sec.  Telnet exhibits   
the same problems.

What's up?  Has anyone else seen this.  BTW this is the second machine   
I've setup that exhibits these problems.

jam

**************************************************************************  
*
*       John A. Maier          * Research and Development   
                *
* E-mail: johnam@datastorm.com * Datastorm Technologies Inc.   
             *
*                              * Procomm Plus for Windows and DOS   
        *
*                              * (314) 443-3283   
                          *
**************************************************************************  
*
