Newsgroups: comp.os.minix
Subject: slip and 2.0.2
Organization: Syracuse University, Syracuse
From: mcconnel@hydra.syr.edu (Terry R. McConnell)
NNTP-Posting-Host: hydra.syr.edu
Message-ID: <36c44f1d.0@news.syr.edu>
Date: 12 Feb 1999 10:56:13 -0500
X-Trace: 12 Feb 1999 10:56:13 -0500, hydra.syr.edu
Lines: 52
Path: news.adfa.oz.au!clarion.carno.net.au!news0.optus.net.au!news1.optus.net.au!optus!intgwpad.nntp.telstra.net!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!news.syr.edu!hydra.syr.edu!mcconnel

I'm having a hard time getting slip to work with 2.0.2, and am hoping someone
can offer some words of advice.

I've finally managed to get chat to log me in in reliably on the remote machine.
From there I start a program called slirp which emulates a slip connection
via a shell account. The details don't matter --  you can think of slirp as
providing a slip service that is indistinguishable from any other. I know
that end is not a problem because I've been using slirp quite reliably 
from Windows 95 and Linux for years now.

The problem is what to do after having made a dialup connection with some
form of slip running on the far end. I've run netdefault psip2 previously,
so then I do

ifconfig -h <my assigned ip address> -n 255.255.255.0

(I've tried many other possibilities for the net mask here.)

Minix's ifconfig doesn't seem to allow you to specify an interface. Is that
because there can be only 1 (setup using netdefault ?)

Then I do

/usr/bin/slip /dev/psip2 </dev/tty00 >/dev/tty00

but this command always seems to hang, i.e., I never get the prompt back.
Is it supposed to work like that ? Running it in the background doesn't
help because then slip is detached from it's stdin and complains that it
immediately reads EOF. 

If I go to another console and continue in what seems to be a reasonable
way, by attempting to add a default route,

add_route -g <ip address of the remote slip host> 

I get a complaint that the device doesn't support an ioctl. (Which device?)
I tried adding -i with /dev/all-sorts-of-things, and always got complaints
about an ioctl, or that the device is not a typewriter (????), although I
did get it to hang once by using /dev/tcp2. (specifying -d 0.0.0.0 etc
doesn't help.)  

I've read the man pages for all these commands as well as serial-ip, ip, and 
slip. As far as I can tell from this material, I'm doing things the right
way. (More, or less.)

Of course, trying to do anything after the above (e.g., telnet) just produces
a network unreachable message. What am I missing?
-- 
************************************************************************
Terry R. McConnell   Mathematics/304B Carnegie/Syracuse, N.Y. 13244-1150
trmcconn@syr.edu                            http://barnyard.syr.edu/~tmc 
************************************************************************
