home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!cs.utexas.edu!qt.cs.utexas.edu!yale.edu!jvnc.net!newsserver.jvnc.net!rutgers!igor.rutgers.edu!geneva.rutgers.edu!hedrick
- From: hedrick@geneva.rutgers.edu (Charles Hedrick)
- Newsgroups: comp.os.linux
- Subject: Re: A few misc questions,
- Message-ID: <Jan.11.22.01.52.1993.22678@geneva.rutgers.edu>
- Date: 12 Jan 93 03:01:52 GMT
- References: <1145.1189.uupcb@satalink.com> <1993Jan9.174500.3183@infodev.cam.ac.uk>
- Organization: Rutgers Univ., New Brunswick, N.J.
- Lines: 17
-
- tjrc1@cus.cam.ac.uk (T.J.R. Cutts) writes:
-
- >So could we have either a) some pointers to a newbie's guide to TCP/IP or b)
- >some really simpleton instructions we can follow to get a working loopback
- >system, with which we can then tinker and learn that way.
-
- There is a general introduction to TCP/IP on athos.rutgers.edu, in
- /runet/tcp-ip-intro.doc and .ps (.doc is ASCII, .ps is Postscript). A
- followon document explains how to set up TCP/IP networks. It's
- /runet/tcp-ip-admin.doc and .ps. (Note that it deal with
- architectural issues in building something like a campus network.
- It's not intended to tell you how to set up networking on a single
- system, though knowing the information in it may help you make sense
- of programs like ifconfig and route.)
-
- These documents are now a couple of years old, so there are newer
- RFC's than those described in them.
-