In article <3ts0c2$...@ionews.io.org> ste...@io.org (Steven Singer) writes:
>I am trying to get UUCP working over TCP/IP. Has anyone done this before?
>(could I possibly see the applicable lines from the Systems,Devices,Dialers?
>files.) I've tried a number of diffrent configurations with no luck. Also is
>there anything special I have to do to get the machine to accept UUCP
>connections over TCP/IP besides uncomment a line from /etc/inetd.conf?
How to configure UUCP over TCP/IP with the TCP socket interface.
KEYWORDS: tcpip uucp configure socket interface file transfer 540 port server client bsd tli listen v4
RELEASE: SCO UNIX System V/386 Release 3.2 Operating System Version 4.0
SCO Open Desktop Release 2.0
SCO TCP/IP Generic
PROBLEM: How do I configure UUCP over TCP/IP with the TCP socket interface?
SOLUTION: The rest of this document assumes knowledge of both UUCP
and SCO TCP/IP.
There are several reasons you may wish to configure the (U)nix
to (U)nix (C)o(P)y system, UUCP, over TCP/IP. Some sites do
not provide ftpd or rshd servers, and/or their respective
clients, ftp and rcp. Thus transferring files across a
TCP/IP network is not an option with these systems.
Additionally, some versions of TCP/IP do not provide the
(S)imple (M)ail (T)ransfer (P)rotocol, SMTP, for mail transfer.
In both of these cases, setting up UUCP to use TCP/IP may be an
option to allow both file transfer and exchange of mail
between such systems.
In the following paragraphs, the word "client" refers
to a system which executes the uucp(C) or uux(C) command,
while the term "server" or "listener" refers to a system
that responds to a request from a client system.
There are two approaches to configuring UUCP over TCP/IP.
They are as follows:
1. The TCP socket interface:
The server system uses the inetd superserver to listen
for incoming uucp requests on TCP port 540. When
receiving a request from a client uucico process, the
server system forks the daemon called uucpd, which logs
in a user whose "shell" is uucico. The two uucico
processes can now transfer information similar to the
way they would in a standard serial line configuration.
Graphically, if machine bomb20 initiates a uucp connection
to the machine terrapin we have the following representa-
uucp or uux
2. The TLI (Transport Layer Interface) method:
The server system uses a process called "listen" to wait
for requests from a predefined TCP port and then when
receiving a request, forks a uucico process directly,
bypassing the standard UUCP login sequence. Graphically,
if machine bomb20 initiates a uucp request to machine
terrapin, we have the following representation:
uucp or uux
SCO UNIX System V/386 Release 3.2 Version 4.0 has a uucico(ADM)
program which supports both of the above methods using the "e"
protocol. In the case where two SCO UNIX System V/386 Release 3.2
Version 4.0 systems are involved, the SCO Support Department strongly
recommends use of the first method, although both will work. In the
case where you want to configure an SCO UNIX System V/386 Release 3.2
Version 4.0 system to talk to another vendor's UUCP package over
TCP/IP, you will have to determine which method listed above the other
vendor's UUCP package supports. The SCO Support Department strongly
recommends use of the TCP socket implementation with the "e" protocol
whenever possible, as it is easier to configure and maintain.
Note that the uucico(ADM) program supplied with SCO UNIX System V/386
Release 3.2 Version 4.0 supports the "e", "f", "x", and "g" protocols.
The "e" protocol is for use with TCP/IP. Other protocols may not work
across TCP/IP. See the default /usr/lib/uucp/Systems file for an
explanation of which protocol to use over a particular network.
The remainder of this document describes configuration of UUCP over
TCP/IP with the TCP socket interface. For information on
configuring UUCP to use the (T)ransport (L)ayer (I)nterface,
(TLI), see the database item entitled:
"How do I set up UUCP over TCP/IP with the Transport Layer Interface"
Configuring UUCP over TCP/IP with the TCP socket Interface
The following steps demonstrate how to configure UUCP over TCP/IP
using the TCP socket interface between the systems bomb20 and
terrapin. This explanation assumes that both systems are running
SCO UNIX System V/386 Version 4.0, along with SCO TCP/IP.
Before proceeding, verify that SCO TCP/IP is installed and
1. On both systems, verify that the file /etc/inetd.conf has the
following line, and that it is uncommented, with no "#"
character at the beginning of the line:
uucp stream tcp nowait NOLUID /etc/uucpd uucpd
In the special case of an SCO UNIX 3.2v4 system running
SCO TCP/IP Release 1.1.3, the following line should be
used instead ("NOLUID" is replaced with "root"):
uucp stream tcp nowait root /etc/uucpd uucpd
Should the program /etc/uucpd not exist, execute the following
commands as root:
ln /usr/lib/uucp/uucpd /etc/uucpd
chmod 755 /etc/uucpd
2. Verify that both systems have the following line in the
uucp 540/tcp uucpd # uucp daemon
3. Verify the configuration of the "nuucp" user on each machine.
Make sure that the "shell" of the "nuucp" user is
/usr/lib/uucp/uucico, and that the "nuucp" user has a password
on both machines. You will probably have to set a password
for the nuucp user. The "shell" of the user can be checked
by using the System Administrator's Shell and choosing
the Account-->User-->Examine menu options.
4. Add the following line to the file /usr/lib/uucp/Systems on
terrapin Any TCP,e Any - ogin: nuucp word: <Password>
<Password> is the password of the nuucp user on terrapin.
5. Add the following line to the file /usr/lib/uucp/Systems on
bomb20 Any TCP,e Any - ogin: nuucp word: <Password>
<Password> is the password of the nuucp user on bomb20.
6. Verify that the /usr/lib/uucp/Permissions file on bomb20 has
the following entry:
MACHINE=terrapin LOGNAME=nuucp \
7. Verify that the /usr/lib/uucp/Permissions file on terrapin has
the following entry:
MACHINE=bomb20 LOGNAME=nuucp \
8. Add the following line to /usr/lib/uucp/Devices on both machines:
TCP TCP,e - Any TCP 540
9. Verify that both bomb20 and terrapin are in each other's /etc/hosts
file, or resolvable by a nameserver.
10. If you needed to change anything in step 1, shutdown and reboot
the systems on which the changes were made. UUCP should then work
as expected between the two systems. Both bomb20 and terrapin
should be able to issue uucp requests for the opposite system.
Note that steps 3 through 7 are similar to the steps used in
configuring UUCP between systems over a serial line. Also,
the user names and sample Permissions files shown here are
only examples and may be changed to suite the security needs
of a particular site.
For general UUCP configuration information, see the database item
entitled "How to configure UUCP for SCO UNIX System V/386."
Also, see Chapter 18 of SCO UNIX System V/386 Release 3.2 Version 4.0
Administrator's Guide "Building a Remote Network with UUCP", or
Chapter 13 of SCO Open Desktop System Administrator's Guide, also
titled: "Building a Remote Network with UUCP".
This information is provided "AS IS" without warranty and may be posted
to public networks individually in response to specific questions as a
public service but no other reproduction, transmittal or storage, in any
form, is permitted without prior written permission from the copyright
owner. Copyright infringement is a serious matter under the United
States and foreign Copyright Laws.
Information in this document is subject to change without notice and
does not represent a commitment on the part of The Santa Cruz
Copyright (C) 1986-1994 The Santa Cruz Operation, Inc.
All Rights Reserved
read more »