*BSD News Article 52618


Return to BSD News archive

Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!simtel!news.sprintlink.net!psgrain!iafrica.com!ticsa.com!cstatd.cstat.co.za!ee.und.ac.za!nntp.und.ac.za!kestrel.ugrd.und.ac.za!chops
From: chops@kestrel.ugrd.und.ac.za (Ewan McPhail)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Hassles with Slip (well described, not a newbie)
Date: 6 Oct 1995 07:21:57 GMT
Organization: University of Natal (Durban), South Africa
Lines: 77
Message-ID: <452lel$pjn@owl.und.ac.za>
NNTP-Posting-Host: kestrel.ugrd.und.ac.za
Summary: Can't go outside the slip host
Keywords: slip sliplogin
X-Newsreader: TIN [version 1.2 PL2]

Okay, I've been reading this group for some time looking at all the 
"help me with Slip" messages, and in particular the "help me I can't
get out of my slip host" ones. I have exactly this hassle - and a few
other questions.

I'd _really_ appreciate it if anyone who could shed some light on the 
situation...

I'm dialling in using Trumpet Winsock for Win3.1. I can connect to the
FreeBSD machine below's modem, and start slip using "sliplogin <myname>" - 
I can then telnet/ftp to the FreeBSD machine, but NOWHERE ELSE.

Here are the bit's and pieces I use (FreeBSD 2.0-Release) :
The FreeBSD machine's Ip is 146.230.224.19
The Ip address we have had reserved for slip is 146.230.224.9

                    /etc/netstart (in this order)
route add default 146.230.224.1   #the router on this subnet.
ifconfig sl0 inet 146.230.224.19 146.230.224.9 netmask 0xffffff00
sysctl -w net.inet.ip.forwarding=1

                    /etc/sliphome/slip.hosts
<username> 146.230.224.19 146.230.224.9 0xffffff00 autocomp

"ifconfig sl0" reports the following :
sl0: flags=d010<POINTOPOINT,LINK0,LINK2,MULTICAST> mtu 552
	inet 146.230.224.19 -> 146.230.224.9 netmask 0xffffff00 (all ok there?)

"sysctl net.inet.ip.forwarding" returns "net.inet.ip.forwarding = 1". (ok too?)

I know that "146.230.224.1" is the correct router on this net, since
that's the first place shown by every traceroute from FreeBSD box.

/etc/host.conf has "bind" before "hosts", and i've tried reversing the order..

I am logging all the parameters passed to /etc/sliphome/slip.login, and
get the following from a login :
  <username> attached @ 19200 via sl0, 146.230.224.19 -> 146.230.224.9, 
  mask 0xffffff00

Do I need to have anything specific in /etc/networks? /etc/resolv.conf?

When i've connected and turned on IP packet tracing on the Windows machine,
I see packets going to the nameserver 146.230.128.7, but no reply reaches
the windows box (146.230.224.9 -> 146.230.128.7, size=x just repeats).
The same happens if i specify the ip address of any remote site, no reply 
from the remote site (so either I'm not sending anything, or I'm not getting 
anything)         [ttyd0 is the serial line, if that helps anything]

Trumpet Winsock claims I don't need to enter the default gateway and
netmask for slip connections, but I have anyway to be sure. 
(btw, what should the default gateway's addr be, the FreeBSD box, or 
gateway on the subnet?)

                       Now for the second part :
I'm presuming ALL I need to exec is /sbin/sliplogin <username>, I don't
need any daemons running? Any kernel options needed?
As far as I can see, "startslip" dials up a remote slip server and connects
(another unix box) - not what I want. And I don't need to run "slattach"
either, do I? (it has a redial option, and I want to dial IN, not out).
(i've tried running "slattach", no go either :(

The man page for "sliplogin" notes that "only the superuser may attach a
network interface" - I'm presuming this is why "sliplogin" is setuid root.

You'll really make my month if you can help me out here!
Thanks in advance!

	-Ewan

---
 _______  
|  _____|wan McPhail - Computer Science undergrad at UND, South Africa.
| |___     mcphail@beastie.cs.und.ac.za (SysAdmin and WebMaster)
|  ___|            <URL:http://kestrel.ugrd.und.ac.za/~chops/>
| |_____     Try my experimental, homebrewed mailserver! 
|_______|    Mail mcphail@beastie with the subject line "request-help".