Path: utzoo!attcan!uunet!wuarchive!zaphod.mps.ohio-state.edu!swrinde!ucsd!celit!billd
From: billd@fps.com (Bill Davidson)
Newsgroups: comp.dcom.modems
Subject: Re: uucp over telnet connection
Message-ID: <12063@celit.fps.com>
Date: 27 Oct 90 21:32:59 GMT
References: <1990Oct24.115921.22397@nstar.uucp> <35219@cup.portal.com>
Distribution: na
Organization: FPS Computing Inc., San Diego, CA
Lines: 21

In article <35219@cup.portal.com> cec@cup.portal.com (Cerafin E Castillo) writes:
[explanation of problems with telnet vs. uucp and using the 't' protocol]
>I hear that some of this is not true when telneting from a
>TCP/IP Terminal Server device (ie Xylogics Annex II/IIe).

I have a IIe on evaluation right now.  Xylogics provides a program
called "rtelnet" (reverse telnet) which is normally run at boot time.
It takes control of a pseudo tty, and puts itself in the background.
Any reads or writes to that pseudo-tty go through rtelnet to the Annex
IIe to a port specified when you invoked rtelnet.  It works great with
binary kermit transfers.  I'm having a little trouble with uucp so far
though (lot's of alarms and timeouts at 19200).  They sent me the wrong
cables so I don't have RTS/CTS flow control.  They are supposed to be
sending me the right ones soon so it may work fine when I get those and
use flow control (They are a bit hard to make since they go from a
50-pin connector to 8 DB25's).  Also, at least on my systems, if you
reset a port which has rtelent running on it, it panics the machine
which is running the rtelnet in the kernel pty driver.  I haven't had a
lot of time to explore this yet.  Has anyone else come across this?

--Bill Davidson