Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!bunyip.cc.uq.oz.au!munnari.oz.au!spool.mu.edu!sdd.hp.com!saimiri.primate.wisc.edu!news.doit.wisc.edu!fozzie!porter From: porter@fozzie (Ron Porter) Newsgroups: comp.os.386bsd.questions Subject: help a newbie with SLIP and UNIX Date: 19 Aug 1994 20:23:17 GMT Organization: Division of Information Technology Lines: 108 Message-ID: <3334bl$nel@news.doit.wisc.edu> NNTP-Posting-Host: fozzie.chem.wisc.edu X-Newsreader: TIN [version 1.2 PL0] Hello, The following is an exerpt from the #7 FAQ(communictions), with many questions from me added in. These questions are both specific to SLIP and general UNIX questions. I hope that i Don't offend anyone by posting this but i'm confused about how to set up a SLIP server on my FreeBSD1.1.5.1 machine and the FAQ's that i have read only bring up more questions. So if you would rather not wast your time helping out a beginner, read no further. Please don't mistake this for lazyness i've been reading UNIX books trying to find answers for these questions and although i've learned many other things there are still many questions :(. If you have suggestions for good UNIX books this is welcomed also. ANY help is appreciated! Thanks, Ron Porter >Section 7. (System Communication and Network Information) >7.1 SLIP/CSLIP > > Serial Line I/P is supported in all versions of PC BSDs. > > Brian <brian@awfulhak.demon.co.uk> provides us with a rather > good explanation of some of the hurdles that must be overcome >for a working slip interface. > > The idea is (overview) that you make a serial line connection to > the host, set the line discipline, and tell your router to use > this interface as your gateway. You also should set the gateway > up as a nameserver. > > You will need the information in 7.4.1 below to make sense to > you before you proceed much further. I suggest you read that > now. ******************************************************* > 7.4.1 TIP/CU > > First thing you need to do is... > > vi /etc/remote > > Then remove the two lines at the bottom of the file that mention > com1, and com2. Now add the following lines: > > com0:dv=/dev/com0:br#9600: > com1:dv=/dev/com1:br#9600: I don't have any com0 or com1 in the /dev directory. Should it be there? Can they be added? Can a tty** device be used instead. Also is there differances between the tty**'s( for instance is tty0 somehow fundementaly differant from ttyp0 or ttyd0 etc...). I assume that once a tty** device is used it can't be used again, at least at the same time, if so, how do you know which devices are already allocated? > That tells tip/cu where to find your com ports. Are tip and cu used by SLIP, or is this just to verify that the devices are working >Next you need to be logged in as root and do a: > > chown uucp.dialer /dev/com0 > chown uucp.dialer /dev/com1 > touch /var/log/aculog > chown uucp.dialer /var/log/aculog Why do the devices have to be owened by uucp and in the group dialer? > Make sure that, if you are running newsyslog, you change the > owner.group entry in the newsyslog.conf file so that the file > ownership is maintained correctly. > > Then you should be all set, remember "DOS Com1" = com0, and > "DOS Com2" = com1. So, if your modem is at 0x2F8/IRQ=3 and you > access it as the COM2: port from DOS, you would do.. > tip com1 "access it"?? what does this mean, will it just check to see if the port is there ********************************************************** > Sounds easy ? - well it is if you've done it before. No! > The _usual_ way of doing this is as follows: > > Both server and client must know eachothers inet addresses. Set > these up in /etc/hosts with lines saying > 11.22.33.44 host.my.domain.name host > 11.22.33.55 client.my.domain.name client Do i really need to tell the server its own IP number in the hosts file? > ** traditional method ** > - Log on to the server. This is usually done via kermit or > some such program. I'm under the impression that kermit is a file transfer protocol, so this make's no sence to me. Can you use just a Comm progrm like Procomm? I assume what i would do is start Procomm and hit return until i see the same "hello" message and login prompt as when i sit down to the machine itself, yes??? > - Exit the program (or background it if your line wants to > drop once the device is closed). > - Run `slattach /dev/comport` for whatever "comport" is. On most > BSD derived systems, this may be either com0, or cua01, or > whatever the correct name is for your site. > - Run `ifconfig sl0 net clientname servername netmask 0xffffff00` > - Run `route add default servername`. Exit what program, Kermit(or procomm)?? Is the effect of the Slattach, ifconfig and route add saved somewhere? Or do i need to add this to a login type file so it runs everytime a user logs in? -- *********************************************************** *Ron Porter porter@chem.wisc.edu * *Univ. Of Wisconsin Chemistry Dept * *1101 University Ave. Madison Wi 53706 * ***********************************************************