Path: utzoo!attcan!uunet!lll-winken!ncis.llnl.gov!helios.ee.lbl.gov!pasteur!agate!ucbvax!UX.ACSS.UMN.EDU!csn1717 From: csn1717@UX.ACSS.UMN.EDU Newsgroups: comp.protocols.tcp-ip Subject: Re: Beginner Questions Message-ID: <8901240243.AA13010@ucbvax.Berkeley.EDU> Date: 24 Jan 89 02:50:03 GMT Sender: daemon@ucbvax.BERKELEY.EDU Lines: 44 In article <437@fedeva.UUCP>, wrd3156@fedeva.UUCP (Bill Daniels) writes: | How does one establish | themselves as an internet node, electrically/mechanically that is? | | (2) Since ftp works locally over an ethernet using tcp-ip, how does an | anonymous ftp connect to a remote site (analogous to uucp dialups)? | Does it tcp-ip over dial-ups? | | (3) How does one rlogin or telnet to a host on a remote network? What | advantage does this have over tip/cu? Given that "ftp works locally using tcp-ip" (thus probably telnet/rlogin), your site is quite ready for Internet connectivity. However, before you can ftp/telnet/rlogin to a remote site, you'll need to find a site which is already connected to the Internet, and is willing to forward packets for you. (By Internet, here I mean some network that is connected, directly or indirectly, to the Nsfnet or Arpanet backbone, and by packet switching --- which would exclude the present Bitnet and UUCP, and to a certain extent, CSnet.) Note that connecting your site to the Internet is more of an administrational than a technical matter... Technically, connection to your peer (the host which is already on the Internet) are usually by means of a leased phone line, though in essence any suitable transmission media of "any" data rate should work. (well, actually, 9600bps is merely acceptable as far as performance is concerned.) Since tcp/ip is just a software subsystem, surely it can be implemented over switched (dial-up) lines --- you just need a driver to get the packets off the line. (There is a package called "slip", implementing the serial line internet protocol. I haven't had experience with it, so I don't know whether it would work over dialups... I'd like to know though, so could someone please enlighten?!) Advantage over tip/cu? well, too many, too many!! With tip/cu, you only connect to one machine; with telnet/rlogin, you can possibly connect to hundreds of thousands, when given the right permissions and right routes... And more importantly, file transfers work a lot better! Have Fun! ;-) Aaron Y. T. Cheung University of Minnesota