Subject: Re: UUCP over TCPIP on 3B2? Q: Can the Wollongong package do uucp over a tcpip connection? A: YES, and here is a way to do it: INSTALLATION PROCEDURE The procedure below explains the steps for installing uucp on your TCP/IP WIN/3B network. These installation procedures will do the following: initalize TCP/IP listener files, create and edit files in /usr/lib/uucp directory, and start the listener process for the TCP/IP network. 1. Create and initalize the files needed by network listener process by entering the following: nlsadmin -i tcp If you have already initalized these files, you will see the following message: NLSADMIN net_spec already initalized 2. Add the uucp(uucico) service to the listener's database file for the network by entering the following: nlsadmin -a 101 -c "/usr/lib/uucp/uucico \ -r 0 -i TLI -u nuucp" -y "comment" tcp If you have already added this service, you will see the following message: nlsadmin: service code 101 already exists \ in /usr/net/nls/tcp/dbf nlsadmin: could not add service 3. Create the TCP/IP listener address file, using this command: /usr/etc/rfsaddr -h `/bin/uname -n` \ >/usr/net/nls/tcp/addr If you are using the /etc/hosts file and this host's internet address has changed, correct the entry in hosts and repeat this step. 4. Create the file /usr/lib/uucp/Dialers.tcp, and add the following line: tcp "" "" NLPS:000:001:101\N\c 5. Create the file /usr/lib/uucp/Devices.tcp, and add the following line: TCP,eg tcp - - TLI \D tcp 6. Edit the file /usr/lib/uucp/Sysfiles, and add the following lines: service=uucico systems=Systems.tcp:Systems \ devices=Devices.tcp:Devices \ dialers=Dialers.tcp:Dialers 7. Create the /usr/lib/uucp/Systems.tcp file, adding an entry for each TCP/IP host system you want to reach via uucp. Each entry must have the form: Any TCP -
In your entry, replace with the name of the remote system as it appears in the /etc/hosts file, or as it is known to the nameserver named. Replace
with the line printed by the command /usr/etc/rfsaddr -h , substituting the host name for for above. The address string is composed of the characters "\x," followed by 32 hexadecimal digits. (see note at bottom) You do not need to create an entry for the local host. Only remote hosts need entries. If a remote host's name or internet address has changed, modify the entry for it in the Systems.tcp file and in the /etc/hosts file or the nameserver database files if the nameserver is being used. See Chapter 4, "Domain Name service." It is essential that host names and addresses be correct in the Systems.tcp file. NOTE: This procedure must be completed on the remote host, as well as on the local host, in order to communicate with the remote host via uucp. 8. Change the ownership of the new tcp files to uucp, using the following command: chown uucp *tcp 9. Start the listener process for the TCP/IP network with the following command: nlsadmin -s tcp SUMMARY The procedure above provides a means of executing batch file transfers between 3B2 Computers running TCP/IP WIN/3B. Note that setting up uucico service in this way can compromise system security, since users will be allowed to connect directly to a remote machine without going through login verification. Therefore, uucp should only be installed over TCP/IP if all network machines can be trusted. -------------------------------------------------------------- A little more information on the
needed in the Systems.tcp file. The address is a hexidecimal representation of a code that includes your IP address. The address has the following format: \xFmlyPortInternetReserved Fmly, This is a four digit field that represents the family address (AF_INET). This field is always set to 0002. Port, This is a four digit field that represents the port number of the listener. The UNIX Systen V Release 4.0 listener uses port number 0ACE. The pre-UNIX System V Release 4.0 uses 0401. Internet, This is the host IP address in hexidecimal notation. This field is always 8 digits, with each octet of the host IP address represented by 2 hexidecimal digits. Reserved, This is a reserved 16 hexidecimal digit field. It is always set to 16 zeros (0000000000000000). Example, a UNIX System V Release 3.x machine with the IP address of 192.9.200.1 would have a listener address of: \x00020401c009c8010000000000000000 ---------------------------------------------------------------- There, wasn't that simple? This worked for me, I have a 3B2/400, a /500, and 2 System V/386 machines all doing some of their UUCP work via TCP/IP. YMMV. -Bob Martel (bob@cua2.csuohio.edu)