*BSD News Article 34349


Return to BSD News archive

Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!bunyip.cc.uq.oz.au!munnari.oz.au!news.Hawaii.Edu!ames!hookup!swrinde!gatech!udel!news.sprintlink.net!sundog.tiac.net!sundog.tiac.net!rick
From: rick@vox.trystero.com (Richard E. Nickle)
Newsgroups: comp.os.386bsd.questions
Subject: Re: Getting SLIP Going
Date: 08 Aug 1994 16:01:10 GMT
Organization: The Internet Access Company
Lines: 116
Distribution: world
Message-ID: <RICK.94Aug8120110@vox.trystero.com>
References: <940807181232683@busilink.com>
NNTP-Posting-Host: vox.trystero.com
In-reply-to: michael.scantlen@busilink.com's message of Sun,  7 Aug 1994 18:08:05 GMT

In article <940807181232683@busilink.com> michael.scantlen@busilink.com (Michael Scantlen) writes:

>   Path: sundog.tiac.net!europa.eng.gtefsd.com!library.ucla.edu!agate!iat.holonet.net!shpbbs!michael.scantlen
>   From: michael.scantlen@busilink.com (Michael Scantlen)
>   Newsgroups: comp.os.386bsd.questions
>   Date: Sun,  7 Aug 1994 18:08:05 GMT
>   Organization: BUSILINK
>   Distribution: world
>   Lines: 13   
>
>   I've read thru the FAQ's at freebsd.cdrom.com and being a first time
>   install/use of SLIP - I'm in the foggy stage.  I was hoping to locate
>   a step-by-step FAQ for getting SLIP going from a fresh FreeBSD install.
>   I have a SLIP provider, IP address, Domain Name, & NameServer.  I have
>   taken pieces of the various FAQ's and probably created a
>   Franken-FreeBSD. 8)
>
>   Has anyone got a pointer to a FAQ or equivalent that someone may have
>   written down the steps [ all the conf files, host files, 'etc' ] that
>   are needed to be performed?  Is cu, tip, or kermit the preferred method
>   for dialup to the slip provider?
>
>	    Thanks for any new pointers... Michael

Here's about what I arrived at:

-	If you have more than one machine on your local net,
	make sure that the machine doing SLIP/PPP has a kernel
	built with GATEWAY enabled.

-	To run slip by hand, do something like the following:

	[ first, find out how to turn off 'drop carrier on dtr transition'
	  on your modem.  i have a switch setting on my USR Sportster to
	  do this.  set it not to drop CD on DTR transition ]

	[ in this example, '199.199.199.199' is your IP address,
	  and '200.200.200.200' is the remote IP address ]

	bash# cu -l /dev/tty00 -s 57600
	[connected -- beep]
	atdt 5557777
	CONNECT 14400[blahblahblah]
	
	Welcome to RandomSLIP!

	Login: yourlogin
	Password: yourpassword

	BEGINNING SLIP SESSION FOR 199.199.199.199 to 200.200.200.200....
	xslkfdjlsdf8

	~[yourmachine].
	[disconnected]
	bash# slattach -a -c -h -s 57600 /dev/tty00
	bash# ifconfig sl0 199.199.199.199 200.200.200.200
	bash# route add default 200.200.200.200
	bash# pine 200.200.200.200
	
	It's that simple, really.  I dunno about tip or anything, but
	that's how I handled it for weeks, with no real trouble, except
	that it wouldn't redial on CD drop.

-	Now, here's my new improved method, thanks to a little advice
	from Wilhelm Kloke:

	[ \ characters are continuation characters, naturally ]

	bash# slattach -a -c -h -z -r 'chat "" ATZ OK ATDT 5557777 login: \
		yourlogin word: yourpassword </dev/tty00 1>/dev/tty00' \
		-s 57600 /dev/tty00
	bash# ifconfig sl0 199.199.199.199 200.200.200.200
	bash# route add default 200.200.200.200

	This works SO WELL, that I put it into rc.local (screw the
	security concerns!), and it works at boot just fine.  Every
	time the carrier on the line drops, it chokes, sputters, and
	redials.

Is that good enough for an FAQ?  I didn't actually explain anything, it's
just a practical demonstration.

KEY POINTS:

-	If you have a local net, enable GATEWAY in the kernel.

-	One thing that trips a lot of people is entering in the
		'hopcount' in the ifconfig, where they enter in
		
		ifconfig sl0 myip remoteip 1

	For a hop-count value of '1' on that interface.  FreeBSD's
	slattach chokes on this, and tries to parse that extra digit
	as another IP address.  That's probably a bug, but if you don't
	do it, you have no problems.

-	Put in the 'route add default remoteip' if you want things
	like telnet and ftp to remote sites to work okay.

I won't even begin to try to talk about nameservers or stuff like that.
It's all black magic!