ji@close.columbia.edu (John Ioannidis) (05/02/90)
In article <70400005@m.cs.uiuc.edu> carroll@m.cs.uiuc.edu writes: > >I would like to have a local UUCP net running between my two machines over >ethernet. I have 3Com cards in the machines, and the normal network stuff >(rlogin, rcp, NFS, etc.) all work fine. What I need to know is how to tell >UUCP about it. The main sticking points have been It doesn't really make sense to run UUCP over ethernet. Why not use ftp or rcp (or just NFS) to transfer files, and sendmail for mail? >1) the device name (/dev ip, tcp, ni ?) >2) the network "address" (A.B.C.D, full host name, subnet id ?) irrelevant. The IP namespace has nothing to do with the filesystem namespace >3) What is NLS (Network Listener Service)? Should I specify it? I thought it was National Language Support! >Any information or manual pointers would be great. I've looked through the >SysAdmin guide, and the TCP/IP guide without much luck. Thanks! Of course not! You are not supposed to do uucp that way. ANyway, if you insist, the easiest way to do it is write a small program that opens a tty/pty pair and 'attaches' the master end to a telnet to the target machine. Your local uucp can then access the slave part of the tty/pty pair (/dev/ttyp?) and use it as if it were a normal tty. if all goes well, when you connect your local uucp process to the pseudo tty, it will see the login: prompt of the remote machine. It can then proceed to log on as uucp etc. I'm still not sure why you want to do that. Trying to exploit uucp security holes again? :-) :-) :-) /ji In-Real-Life: John "Heldenprogrammer" Ioannidis E-Mail-To: ji@cs.columbia.edu V-Mail-To: +1 212 854 5510 P-Mail-To: 450 Computer Science \n Columbia University \n New York, NY 10027
dag@fciva.FRANKLIN.COM (Daniel A. Graifer) (05/02/90)
In article <1990May2.044758.22817@cs.columbia.edu> ji@close.UUCP (John Ioannidis) writes: >In article <70400005@m.cs.uiuc.edu> carroll@m.cs.uiuc.edu writes: >> >>I would like to have a local UUCP net running between my two machines over >>ethernet. [...] >It doesn't really make sense to run UUCP over ethernet. Why not use >ftp or rcp (or just NFS) to transfer files, and sendmail for mail? >[...] >In-Real-Life: John "Heldenprogrammer" Ioannidis Don't knock this so quickly. System V uucp has hooks in it to do this easily for a reason. I've been meaning to set this up myself. Suppose you have a file on machine a to copied to and processed on machine b. It is important that it get done eventually, but not that it happen immediately. Mail solves this with a whole hierarchy of daemons to maintain the sendmail queues. It would be nice to use the uucp and uux queueing mechanisms to accomplish this for other tasks, rather than writing software to manage my own delayed remote execution queues. My Devconfig file contains comments describing how to get uucico/cu to push streams modules onto a network interface. My Devices file contains comments on how to connect thru an NLS (Network Listener Service) thru an NSU (Network Service Utility) as described in the comments in my Dialers file. All of this assumes that your ethernet conforms to the AT&T STREAMS transport interface. If carroll@m.cs.uiuc.edu doesn't have these comments in the D* files supplied with his/her uucp, and would like me to extract them from mine, please send me E-mail. Dan -- Daniel A. Graifer Franklin Mortgage Capital Corporation uunet!dag@fmccva.franklin.com 7900 Westpark Drive, Suite A130 (703)448-3300 McLean, VA 22102
ebersman@uunet.UU.NET (Paul Ebersman) (05/02/90)
In <1990May2.044758.22817@cs.columbia.edu> ji@close.columbia.edu (John Ioannidis) writes: >In article <70400005@m.cs.uiuc.edu> carroll@m.cs.uiuc.edu writes: >> >>I would like to have a local UUCP net running between my two machines over >>ethernet. I have 3Com cards in the machines, and the normal network stuff >>(rlogin, rcp, NFS, etc.) all work fine. What I need to know is how to tell >>UUCP about it. The main sticking points have been >It doesn't really make sense to run UUCP over ethernet. Why not use >ftp or rcp (or just NFS) to transfer files, and sendmail for mail? >>Any information or manual pointers would be great. I've looked through the >>SysAdmin guide, and the TCP/IP guide without much luck. Thanks! >Of course not! You are not supposed to do uucp that way. ANyway, if you Yes, you can do uupc over TCP, if your uucp supports this. That is what the uucpd daemon is for. You will need to have a login for the site with uucico as the shell and an entry in your L.sys similar to the following: site Polled TCP uucp site.internet-name One reason to do uucp over tcp is for rnews without using NNTP. You can also use it to avoid using sendmail's domain rewriting :-) -- Paul A. Ebersman @ UUNET Communications uunet!ebersman or ebersman@uunet.uu.net The difference between theory and practice in practice is greater than the difference between theory and practive in theory.
davidsen@sixhub.UUCP (Wm E. Davidsen Jr) (05/03/90)
In article <1990May2.044758.22817@cs.columbia.edu> ji@close.UUCP (John Ioannidis) writes: | It doesn't really make sense to run UUCP over ethernet. Why not use | ftp or rcp (or just NFS) to transfer files, and sendmail for mail? Not true in mant cases. uucp and uux are store and forward protocols, which do not require that both machines be up at the instant you enter the command. NFS, rcp, rsh all fail if the other system is down. Both techniques have their good points, and there is no "wrong way" other than to assume that either way will be best for all cases. | Of course not! You are not supposed to do uucp that way. ANyway, if you | insist, the easiest way to do it is write a small program that opens | a tty/pty pair and 'attaches' the master end to a telnet to the | target machine. Your local uucp can then access the slave part of the | tty/pty pair (/dev/ttyp?) and use it as if it were a normal tty. if all goes | well, when you connect your local uucp process to the pseudo tty, it will | see the login: prompt of the remote machine. It can then proceed to log | on as uucp etc. Exactly so. And many versions of uucp provide a way to do this for you, although there may still be a need to write your own. Pretty good explanation of how to do it from someone who doesn't see why you do it at all ;-) | | I'm still not sure why you want to do that. Trying to exploit uucp | security holes again? :-) :-) :-) I think the reasons listed above are sufficient, particularly the uux example, since for something which doesn't just use stdin/stdout you need to ftp the input files, run on the remote machine, and ftp the results back (deleting the files of course). uux does all this for you. -- bill davidsen - davidsen@sixhub.uucp (uunet!crdgw1!sixhub!davidsen) sysop *IX BBS and Public Access UNIX moderator of comp.binaries.ibm.pc and 80386 mailing list "Stupidity, like virtue, is its own reward" -me
guy@auspex.auspex.com (Guy Harris) (05/04/90)
>Yes, you can do uupc over TCP, if your uucp supports this. That is what >the uucpd daemon is for. Time to point this out again: "UUCP over TCP" doesn't necessarily refer to one particular thing. One UUCP-over-TCP was, to a large degree, done by your president (or whatever the hell is Rick's official title) at Computer Consoles; that mechanism is the one you're discussing, and is in the 4.3BSD UUCP, as well as patches to Honey Danber source that Peter Honeyman put out (and which were folded into the SunOS 4.1 HDB-based UUCP). Another is the UUCP-over-TLI stuff supported by the HDB that comes with System V Release 3.x; this is UUCP-over-TCP if you have a TLI-based TCP implementation, which I assume a number of S5R3 systems have. As far as I know, the two aren't compatible; for one thing, Rick's UUCP-over-TCP uses the "t" encapsulation that he devised, while the S5R3 UUCP has only the "e" encapsulation.
vjs@calcite.UUCP (Vernon Schryver) (05/04/90)
In article <899@sixhub.UUCP>, davidsen@sixhub.UUCP (Wm E. Davidsen Jr) writes: > > Not true in mant cases. uucp and uux are store and forward protocols, > which do not require that both machines be up at the instant you enter > the command. NFS, rcp, rsh all fail if the other system is down. There is a fair chunk of news shuffled among a some large sites in the San Francisco Bay Area using rcp/rsh/TCP/IP/leased-lines. That is, a trivial protocol using news batch files and rcp act as a "store and forward protocol," doing the correct things when one end or the other is down. My introduction to the idea was indirectly from Brian Reed of DEC. It is very easy to implement. I much prefer the scheme to NNTP/TCP as a transport mechanism because NNTP uses an incredible ihave/sendme, one article at a piddling, context switching, tiny packet time. I confess that I have not actually measured the relative CPU costs or network costs. Looking for facts when you have a perfectly good theory would be against the spirit of usenet. It must be noted that there is some pressure to replace the rcp scripts with "normal" UUCP/TCP from someone at one of the sites who would rather reduce the number of mechanisms he has to maintain. Vernon Schryver vjs@calcite.uucp
clay@haapi.uci.mn.org (Clayton Haapala) (06/01/90)
In article <1990May21.034847.21653@fts1.uucp> michael@fts1.uucp (Michael Richardson) writes: > > [Followups to comp.mail.uucp, since I think this applies to more >than just 386/ix.] > >In article <186@touch.touch.com> john@touch.uucp (John Weald) writes: >>This is how to set up UUCP to use Ethernet (actually TLI). The example >>is for OSI, however you can change the OSI addresses to TCP/IP. >> >>It works on 386/ix 2.0.2. > > First - thanks! I'm going to read it over again later... I'd like to read it the first time :-) -- I musta missed it. I have been unable to get uucp over TCP/IP to work under 386/ix HOST-BASED TCP/IP. We do not have an NP600 card, rather two NI5210's and a WD8003. I think it has to do with the listener. (RFS doesn't work either, and maybe for the same reason, but that is for another news group.) The listener won't bind to its address, and won't 'listen' to connections at the '00000000' address that it doesn't complain about. This is 386/ix 2.0.2 with TCP/IP 1.2 installed. -- Clay Haapala This signature brought to you by DAM: clay@haapi.uci.mn.org, Mothers Against Dyslexia ...!{bungia,jhereg}!uci!haapi!clay