Path: utzoo!attcan!uunet!bywater!scifi!njs
From: njs@scifi.UUCP (Nicholas J. Simicich)
Newsgroups: comp.dcom.modems
Subject: Re: uucp over telnet connection
Message-ID: <1813@scifi.UUCP>
Date: 29 Oct 90 02:57:49 GMT
References: <1990Oct24.115921.22397@nstar.uucp> <35219@cup.portal.com>
Distribution: na
Organization: Nick Simicich, Peekskill, NY
Lines: 46

In article <35219@cup.portal.com> cec@cup.portal.com (Cerafin E Castillo) writes:

>		UUCP over TCP/IP is in need of UUCP protocol 't'.
>	I am not certain of the specifics on the 't' protocol, but
>	when using a psuedo tty via telnet to do uucp sessions,
>	the IP datagrams and delays do get in the way.

Actually, my measurements have found those delays to be fairly
insignificant.  I frequently uucp from my home machine to a machine at
work by calling an Annex II terminal server, and then using a fairly
complex chat script where I turn off all of the telnet options which
would get in the way.  I also telnet to port 540 on the work machine,
which is the port listened to by the uucp daemon at that end.  Modems
are Telebit T2500's, no flow control is used, and everything works
fine.   The newer releases of the Annex II software are capable of
making a binary character-by-character path using telnet to data
ports. 

I don't think that IP gets in the way, I think it is the "telnet"
protocol, which has a character escape, might convert cr to cr-nl, and
so forth.  

The uucp protocol I can use, g or t, is selected during negotiation.
You don't have to use t, and I don't.

>
>		Someone else in this group may know more and wish
>	to comment.  I have seen some write-ups on uucp protocol
>	't' in the AT&T SysVR3.2.2 manuals.  Good Luck!
>
>	P.S.
>
>	I hear that some of this is not true when telneting from a
>	TCP/IP Terminal Server device (ie Xylogics Annex II/IIe).

When we were using an RT as a terminal server, I did the same thing,
but I used a simple program which connected to uucpd on the remote
machine via tcp/ip.   All that was required was that the program send
the characters it reads from the modem to the remote end, and that the
characters read from the socket be sent to the terminal, without
changing them in any way.


-- 
Nick Simicich - uunet!bywater!scifi!njs - njs@ibm.com
SSI #AOWI 3958, HSA 318