Return to BSD News archive
Newsgroups: comp.unix.bsd Path: sserve!manuel!munnari.oz.au!uunet!decwrl!csus.edu!netcom.com!alm From: alm@netcom.com (Andrew Moore) Subject: SLIP set up, but how to connect? Message-ID: <r0rn0hj.alm@netcom.com> Date: Wed, 09 Sep 92 02:10:25 GMT Organization: Netcom - Online Communication Services (408 241-9760 guest) Lines: 45 I am using "Unix System Administration" by Nemeth, Synder, Seebass as a reference, which is very helpful, but it doesn't seem to cover SLIP... On one system SLIP autologin is set up as per the sliplogin man page (sliplogin linked to /etc/, passwd entry added with vipw, etc). On the second system, only the 386bsd distribution installation disk is installed (and a patched kernel from the first system). I can use the second system as a serial terminal (connecting with tip) on the first. But how to I get a SLIP connection? Following the 386bsd installation instructions for loading 386bsd via SLIP, I do: # slattach /dev/com2 9600 # ifconfig sl0 192.100.92.2 192.100.92.1 (192.100.92.1 and .2 are the arbitrary IP addresses that I have assigned to the first and second system, respectively. They appear in the first system's /etc/hosts file). Is the route command necessary now? If so, do I use the first system's IP address as the <local gate number>? In the mean time, I try: # ftp 192.100.92.1 No complaint, but no connection either. So I try: # route add default 192.100.92.1 adds default OK. Again: # ftp 192.100.92.1 nothing. So then I try tip, but that doesn't work now. Other variations I have tried: login via tip before slattach to the first system using SLIP login name (Sworm). autolgoin fails in slip.login. connect via tip and at the "login: " prompt ^Z back to local system. Do slattach, fg back to tip - the diagnostic appears: "write not support by device" etc. What am I doing wrong? -Andrew Moore <alm@netcom.com>