[comp.protocols.tcp-ip] Beginner Questions

wrd3156@fedeva.UUCP (Bill Daniels) (01/22/89)

I am new to the world of high-speed networking with Ethernet/tcp-ip and have a
few questions.  Most of my concerns are due to an inability to reconcile the
high speed local area net with remote internet connections.  I am planning
one network for our development work and yet another net for production
work.  I would also like to be able to finally make use of the multitude of
postings offering access to various archive sites through anonymous ftp.

(1) From my brief encounters with the Ultrix Networking manuals, I have a 
pretty good understanding of how a local network is set up and have actually
connected two uVaxen by means of an ethernet.  How does one establish
themselves as an internet node, electrically/mechanically that is? (I have
already asked for an internet address.)

(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?

I am sure that responses to these questions will generate even more questions
from me.  I do appreciate any help you might be able to give me.

-- 
bill daniels
federal express, memphis, tn
{hplabs!csun,gatech!emcard,mit-eddie!premise}!fedeva!wrd3156

csn1717@UX.ACSS.UMN.EDU (01/24/89)

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