Article View: can.usrgroup
Article #717UUCP/TCP/IP[/TLI] for BNU 1 or better
From: Sean Doran
Date: Mon, 13 Apr 1992 06:21
Date: Mon, 13 Apr 1992 06:21
61 lines
2811 bytes
2811 bytes
The other day at the UNIX Unanimous meeting in Toronto, I offered to
post some information about how to do UUCP over TCP using HDB UUCP.
If you want to accept incoming connections, you will generally need
either a uucpd (porting the 4.3-reno uucpd is generally not too
difficult, although for SVR4 machines one has to watch the shadow
password and utmp junk) or a uucico that understands the t protocol.
1. Figure out whether your HDB supports SysV streams or BSD sockets.
Generally if you have a SYSV derived UNIX you have streams, and
want to use the TLI/TPYR method, and if you have a BSD derived
system you should be able to use the TCP/gethostbyname one.
2. Set up your Devices file
for Streams:
TPYR,et tcp - - TLI \D
for sockets:
TCP,et - - Any TLI -
The ,et specifies the choice of protocols to use; e does no error
checking and is appropriate for use with TCP or any other
kernel-to-kernel error-free character stream, while t is useful when
talking to a telnetd rather than a uucpd.
2. The Systems file
(for TLI)
uunet.ca Any TPYR,e - \x0002021c8e4d0101 in:--in: what word: fooblat
This says to connect to uunet.ca with the TPYR device, using a tcp
stream to remote port 512 (0x021c), IP interface 142.77.1.1
(0x8e4d0101), and to use the e protocol. There is no reason why
one couldn't use another port, provided that it can handle a simple
negotiation and one of the standard protocols (like 't').
UUCPD will offer login: as one would expect.
(for TCP)
lsuc Any TCP,e - news.lsuc.on.ca in:--in: FOOBAR ord:--ord: barfoo
Resolve news.lsuc.on.ca using gethostbyname(3N), and connect to the
"uucp" port (resolved by getservbyname(3N)), which is where uucpd
lives. Use "e" protocol.
It is possible to get the TCP driver to connect to another port by
replacing the "-" with another name that getservbyname can use.
3. Test things out with heavy use of -x9. The obvious problems are
mainly on the remote end (does the daemon pass the right
environment to HDB, and does it generate a reasonable utmp entry, or
has the v2 UUCP been set up to accept calls from your hostname),
although there are strange things I've seen with AT&T SYSVr3
involving SO_KEEPALIVE.
Sean.
Technical Details
Message-ID:
<1992Apr13.062117.10967@uunet.ca>Path:
arc1-ca.pugleaf.net!sparky!uunet!uunet.ca!smdShow Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 1149bd,8c29dcdcd47596db,start X-Google-Attributes: gid1149bd,public X-Google-ArrivalTime: 1992-04-12 23:21:17 PST Newsgroups: can.usrgroup Path: arc1-ca.pugleaf.net!sparky!uunet!uunet.ca!smd From: smd@uunet.ca (Sean Doran) Subject: UUCP/TCP/IP[/TLI] for BNU 1 or better Organization: UUNET Canada Date: Mon, 13 Apr 1992 06:21:17 GMT Message-ID: <1992Apr13.062117.10967@uunet.ca> Distribution: can Lines: 61