davec@shared.uucp (Dave Close) (01/26/91)
My Intel SysV R4 box is connected to the world only via Ethernet. Another
box on the net has the modem and runs uucp. So, to transfer to/from external
systems using uucp, I must relay through the other system.
AT&T's manual says you can run uucp over TCP/IP. The files look like this:
Devices: networkx,eg devicex - - TLIS \D
Systems: systemx Any networkx - addressx [chat...]
systemx = The other guy's system name, seems easy.
networkx = The network name, in this case "tcp".
devicex = The network device, /dev/tcp, entered as "tcp".
addressx = The address of the other guy on the network. The System
Administrator's Guild says (pg 7-45) that "this is usually
just the system name".
Try as I can, I can't find a value for addressx which works. Just entering
the system name, Uutry returns "invalid address format". Entering the IP
address or socket number, or any combination, or anything containing a period
or a comma, causes Uutry to say "address family not supported by protocol
family". Of course, all the examples in the manual are for StarLan.
Can anyone say if this should work? If so, what am I doing wrong?
--
Dave Close, Shared Financial Systems, Dallas
davec@shared.com vmail +1 214 458 3850
uunet!shared!davec fax +1 214 458 3876
My comments are my opinions and may not be shared by Shared.bobp@cbnewsl.att.com (robert.phillips) (01/28/91)
In article <1991Jan26.012029.36153@shared.uucp> davec@shared.uucp (Dave Close) writes: >My Intel SysV R4 box is connected to the world only via Ethernet. Another >box on the net has the modem and runs uucp. So, to transfer to/from external >systems using uucp, I must relay through the other system. > .... > >Try as I can, I can't find a value for addressx which works. Just entering >the system name, Uutry returns "invalid address format". Entering the IP >address or socket number, or any combination, or anything containing a period >or a comma, causes Uutry to say "address family not supported by protocol >family". Of course, all the examples in the manual are for StarLan. > >Can anyone say if this should work? If so, what am I doing wrong? >-- > Dave Close, Shared Financial Systems, Dallas > davec@shared.com vmail +1 214 458 3850 > uunet!shared!davec fax +1 214 458 3876 >My comments are my opinions and may not be shared by Shared. Well, UUCP over TCP/IP works, but not in the way that you are trying it. At the risk of annoying someone in the Company, it is pretty silly to give examples for Starlan, when few people outside of AT&T or its spin-offs have ever used it, heard of it, or cared one whit about it. Try something like this (Entries from my own System V R4 386--known to WORK-- with names and addresses changed to protect the innocent) /etc/uucp/Systems: bart Any TcpCico10 - \x00020401c10c6d61 /etc/uucp/Devices: TcpCico10,eg tcp - - TLI \D listencico10 /etc/uucp/Dialers listencico10 "" "" NLPS:000:001:10\N\c /etc/saf/tcp/_pmtab 10::listen:reserved:reserved:reserved:::c::/usr/lib/uucp/uucico -r 0 -i TLI -u uucp And don't forget that your nlps server must be properly configured in /etc/saf/tcp/_pmtab, as well. That entry should look something like 0::root:reserved:reserved:reserved:\x00020ACEC10C6D610000000000000000::c::/usr/lib/saf/nlps_server Good luck Rob Disclaimer: The typing presented here does not reflect the typing that AT&T, any of its subsidiaries, or any entity even remotely connected to it would type if given the opportunity. The information presented is as correct as I could make it, barring typographical errors, brain seizures, and random acts of stupidity. -- Rob Phillips AT&T BL 190 River Rd. Summit, NJ 07901