Xref: utzoo comp.unix.questions:11626 comp.mail.uucp:2752 comp.protocols.tcp-ip:6194
Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!sharkey!emv
From: emv@a.cc.umich.edu (Ed Vielmetti)
Newsgroups: comp.unix.questions,comp.mail.uucp,comp.protocols.tcp-ip
Subject: Re: uucp via IP ?
Message-ID: <8995@mailgw.cc.umich.edu>
Date: 10 Feb 89 20:12:10 GMT
References: <522@cvman.UUCP> <8778@orstcs.CS.ORST.EDU>
Reply-To: emv@mailgw.cc.umich.edu (Ed Vielmetti)
Followup-To: comp.mail.uucp
Organization: University of Michigan Computing Center, Ann Arbor
Lines: 19

In article <522@cvman.UUCP> gdelong@cvman.UUCP (Gary Delong) writes:
>How does one establish a uucp connection via an existing network
>connection such as TCP/IP where rlogin is available.

Two reasonably easy ways.

1.  If your uucp supports 't' protocol (4.3, recent HoneyDanber)
    then you're all set.  L.sys lines look like this for 4.3:

2.  If you have an Annex terminal server it can be configured to
    pass all 8 bits with the magic string 'stty parity none bchar 8'.
    Then run 'g' protocol over the line and use 'rlogin' to sign on.
    Similar magic for ciscos is probably available.

One gotcha is embedding the space character into the expect-send string
for the 'rlogin foo.umich.edu' command, check your documentation on that one.
--
Edward Vielmetti, U of Michigan Computing Center mail group
Support dial-up tcp/ip -- help wipe out uucp.