[comp.protocols.tcp-ip.ibmpc] Can't use KA9Q with 9.6Kbps Telebit, but can use 9.6K hard

ron@vsedev.VSE.COM (Ron Flax) (01/26/88)

The subject pretty much sums things up.. I can connect two machines at
9600 baud over a hardwired connection just fine, but when I put two
Telebit Trailblazer modems in between I am unable to establish a
session of any kind.  The modems are set up in PEP mode, but ALL
asynchronous protocols have been disabled.  I have tried setting data
compression on/off, but there is no difference.  I can however use the
modems with tip/cu to dial each computer and work interactively at
9600 baud, but I cannot get a SLIP connection to work.

--
ron@vsedev.vse.com	(Ron Flax)
uucp:	..!uunet!vsedev!ron
inet:	vsedev!ron@uunet.uu.net

jbvb@ftp.UUCP (James Van Bokkelen) (01/27/88)

I tried to reply to your first message directly, but somebody didn't know
the back-path.

The SLIP we were using (ours) with the Trailblazers implements CTS modem
control (optionally), and the Telebits needed it to work at 19.2.  Aside
from being a little jumpy due to a bit of a mis-match between the underlying
half-duplex packet size the Telebits were using, and uncompressed SLIP
datagrams, it all worked fine.

James VanBokkelen
FTP Sotware Inc.

karn@thumper.bellcore.com (Phil R. Karn) (02/05/88)

I simply assert RTS and DTR in my asynch driver and leave them on; I do
not do any form of RTS/CTS flow control. I just don't think it should be
necessary, because TCP does its own end-to-end flow control.  If a
pseudo-full-duplex modem can't spare enough memory to buffer even one
typical TCP window, then that's the modem's problem.

I use V.32 modems (true 9600 bps full duplex) and they work great!

Phil Karn, KA9Q