Xref: utzoo comp.sys.next:19185 comp.dcom.modems:10419
Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!stanford.edu!agate!spool.mu.edu!caen!zaphod.mps.ohio-state.edu!mstar!mstar.morningstar.com!bob
From: bob@MorningStar.Com (Bob Sutterfield)
Newsgroups: comp.sys.next,comp.dcom.modems
Subject: Re: Tuning slip on a T2500/NextStation
Message-ID: <BOB.91Jun17133028@volitans.MorningStar.Com>
Date: 17 Jun 91 17:30:36 GMT
References: <456@nic.cerf.net>
Sender: usenet@MorningStar.COM (USENET Administrator)
Reply-To: bob@MorningStar.Com (Bob Sutterfield)
Organization: Morning Star Technologies
Lines: 11
In-Reply-To: benseb@grumpy.sdsc.edu's message of 16 Jun 91 17:49:27 GMT

In article <456@nic.cerf.net> benseb@grumpy.sdsc.edu (Booker Bense) writes:
   ...The connection is t2500 to t2500 and I generally run it in pep
   mode... This is running regular slip ( I know I shoud be using
   cslip or PPP but it's not an option at this point. )

Without TCP header compression (whether SLIP or PPP), you can expect
pathologically slow IP throughput over PEP.  Try using the T2500s in
V.32/V.42/V.42bis mode, if they're able to maintain the carrier.  If
your line is really grungy, you may need to compare whether you lose
more throughput to V.32's frequent and unpredictable retrains, or to
PEP's turnarounds.  My choice?  implement RFC-1144...