Return to BSD News archive
Newsgroups: comp.os.386bsd.questions Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!elroy.jpl.nasa.gov!swrinde!gatech!howland.reston.ans.net!vixen.cso.uiuc.edu!moe.ksu.ksu.edu!crcnis1.unl.edu!news.unomaha.edu!cwis!ekennedy From: ekennedy@cwis.unomaha.edu (Eric Kennedy) Subject: Re: FreeBSD incoming SLIP line configuration? Message-ID: <ekennedy.754240437@cwis> Keywords: SLIP FreeBSD Sender: news@news.unomaha.edu (UNO Network News Server) Organization: University of Nebraska at Omaha References: <ekennedy.754064115@cwis> Date: Thu, 25 Nov 1993 15:13:57 GMT Lines: 44 ekennedy@cwis.unomaha.edu (Eric Kennedy) writes: >I am trying to configure a incoming SLIP line for FreeBSD. My configuration >is PC running FreeBSD 1.0 with a DOS PC connected to it with a null modem >cable. I have tried CSLIPPER, UMSLIP, and SLIP8250 as SLIP drivers on the PC. >I am able to login to the FreeBSD machine and use the line as a terminal with >no difficulty. When I login with an ID that runs sliplogin as it's shell I >get a message that the slip connection has started. I have tried NCSA Telnet, >WATTCP apps, and QVTNET. I am unable to connect with the server (however >they do start up okay, in other words they are finding the packet driver). If >I load a comm package and ping the PC from the FreeBSD machine I can see >that information is infact being sent to the PC. It appears as though the >information is not recognized by the TCP/IP packages. Any suggestions? Is there >a special setup for the tty port to support incoming SLIP? I've spent serveral >hours trying to figure this out and am kind of at a loss as to what to try >next. (BTW, I have looked at all of the FAQ's). >Thanks, Eric Kennedy (ek@cwis.unomaha.edu) I was able to fix this problem by setting up a special gettytab entry for this port that specified no parity "np". I can now connect to the machine using FTP software's PC/TCP SLIP drivers. I now am having difficulty getting the routing to work properly. I have one segment on an ethernet cable (network 129.1.3.0) and the other one on the SLIP line (network 129.1.2.0). The ethernet card in the FreeBSD box is 129.1.3.2 and the SLIP connection is 129.1.2.5. A PC on the ethernet is 129.1.3.3. The PC on the end of the SLIP connection is 129.1.2.4. The netmask is 255.255.255.0. I can ping both PC's from the FreeBSD box. I can ping both 129.1.3.2 and 129.1.2.5 from the PC on the end of the SLIP line, but I cannot ping 129.1.3.3. Likewise I can ping 129.1.3.2 and 129.1.2.5 from the PC on the ethernet, but I cannot ping 129.1.2.4. I have tried to set up routes on the FreeBSD box as follows: route add -interface -net 129.1.3.0 129.1.3.2 route add -interface -net 129.1.2.0 129.1.2.5 I have experimented using the -g flag on routed but nothing seems to work. Is there something special that I need to do to enable routing on the machine? Also I have not gotten the SLIPPER packet driver to work yet. I thought I would try to get the whole setup working with the FTP package before trying to figure that out. Any help with the routing problem would be greatly appreciated. Thanks, Eric Kennedy (ekennedy@cwis.unomaha.edu)