🚀 go-pugleaf

In article <CE15yG.4z8@qsss08.gs.com> bk@qsss01.gs.com writes:
>I'd like to know what the diff between PPP and SLIP are.  I'm trying to connect
>to the internet via jvncnet and they told me they use PPP, actually they
>use MorningStar PPP.  Depending on who I talk to I get different responses about
>what each of the protocols are.  First I'm told they are not compatible.
>Then I hear that PPP is just a negotiator of whether to use slip or cslip (compressed
>slip).  This person also tells me that MorningStar PPP runs all 3, ppp, slip and cslip.

I've been battling this for a couple of months, and finally resolved it
last night.  While everyone I've spoken with at JVNC is nothing if not
polite and willing, I really began to wonder where I had sent my check when
they would say "SCO? What's SCO?".

While they recommend Morningstar PPP, and while they may know all about
setting up Morningstar PPP, you are quite right, they don't seem to know
much beyond parroting stock phrases.
It took six weeks until one of the them said to me, "hey, you don't want to
run PPP to talk to the terminal server; you want to run compressed slip."

The light went on: what they knew about was setting up the Morningstar PPP
package to run compressed slip.

[I have never seen or touched Morningstar's package, and I have never heard
anything but praise for Morningstar; but I'd paid a pretty penny for my SCO
software, and right in front of me are man pages for slip, ppp, pppd...]

The other side of my problem concerned SCO ODT 3.0 (Unix 3.2v4.2). I could
connect to the JVNC terminal server, but not ping a thing there, or connect
to rest of the world in any way, until I knocked out all the ppp chains I
had, and the other slip chain as well. When you ask SCO Unix to add a route,
it doesn't seem to let you tell it to which chain this pertains, and the
route would get associated with everything except my slip line to jvnc.net.

Finally I deleted all the ppp and slip chains, and left only kernel driver
code for slip.
I commented out the slattach line in /etc/tcp, since SCO slattach doesn't
know how to do any dialing, and only deals with a specific tty line, so I
didn't want such a command to be launched at boot time.

Now, after tcp starts, I launch my connection with this sequence:
I call xcfront, a shell script which calls xc until xc finds an unused
modem line, then xc runs a script which calls the terminal server, logs in,
launches slattach on whichever modem port it dialed out on, and then sets
up the default route through that server.

I was doing telnet and ftp all over the world last night, from this SCO
machine, via the JVNC NYC POP, over a WB at v.32bis/v.42bis.

My remaining problem is to write a daemon to kill the slattach when JVNC
has dropped the connection due to inactivity; otherwise, the xc is still
running and the modem is still off-hook and unavailable.


-----
	# @(#).slip script for xc -- must be run by root
	# @(#)Francois Vrana, Jean-Pierre Radley 93/09/29

	set proto 8n
	set cis off		# otherwise ^E triggers B+ protocol
	# debug "on"		# turn on verbose script reporting
	# tty "off"		# don't echo received characters to screen

	transmit "atS41=0^M"	# turn off inactivity timer on WBlazer
	dial "555-5555"		# number of JVNC's POP

	while ! waitfor "CONNECT" 40 ; do; redial ; done

	waitfor  "name:"	;transmit "MeAndI^M"
	waitfor  "word:"	;transmit "GiantSecret^M"
	waitfor  ">"		;transmit "terminal download^M"
	waitfor  ">"		;transmit "terminal telnet-transparent^M"
	waitfor  ">"		;transmit "slip /compress^M"
	waitfor	 ":"		;transmit "MeAndI^M"
	waitfor  ":"		;transmit "GiantSecret^M"
	waitfor  "compress."

	# add route *after* slattach with sleep
	shell "(/bin/sleep 5;/etc/route add default 11.22.33.1 1) &"

	# $MODEM is in the environment, it's the port we're dialing on
	shell "/bin/stty intr '' quit '' kill '';/etc/slattach +e +m 1500 $MODEM 11.22.33.55 11.22.33.1 38400"

	# if we get here, the slattach got killed & we are done...
	hangup
	beep
	shell "/etc/route delete default 11.22.33.1"
	echo "SLIP CONNECTION TERMINATED"
-----

-- 
Jean-Pierre Radley   Unix in NYC   XC custodian   jpr@jpr.com   CIS: 72160.1341