Subject: Re: ppp struggles! please help!
To: Krypto <cyberdog@sunworks.com>
From: Bill Studenmund <wrstuden@loki.stanford.edu>
List: port-mac68k
Date: 04/06/1997 22:29:45
> 
> Hey folks, I am having major problems getting on the internet from netbsd.
> I've tried pppsetup.tgz... and i spend 2 soild days trying to get it to
> work... is there any other software package I can use??

Rather than give up, why not get us to try and help you get it running?

Those scripts are basically the ones I am using right now. They do
work. Though they are more sophisticated than other working scripts,
they should be just as easy (or hard) to configure as the part you
have to configure is the same in each one.

I'm going to get soap-boxy as a number of folks are having problems.

You have to provide two things: the modem intialization string, and
how to get into your ISP. Both of these things will go into
the chat script.

The chat script is a set of see-say pairs. chat looks for the first
thing, then says the next thing. If it looks for a "" item, it
just goes ahead and says the next thing.

If your ISP supports ppp under MacOS, STEAL ITS CONFIGURATION!!!!!!!!
The ATXXX string in ppp.setup.tgz was stolen right out of my copy of MacSLIP.
Your modem will probably want something else.

My ISP (Stanford) has a fairly simple setup. You dial in, enter your
login name, then your password. Then you type ppp, and away you go.

I do not know what your ISP wants. But the chat script needs to do what
they want, not what Stanford wants.

If you have ppp up under MacOS, look at that chat script. No, copy it.
Chat scripts are chat scripts.

If you are having chat script problems, I've pulled Paul Goyette's debug
helpter out of the demand-dial ppp kit, and put it in ftp://ftp.macbsd.com/
pub/NetBSD/contrib/ppp-setup and it's the ppp-debug file. There's a
readme. Run it, then try ppp. All the stuff chat sends and sees will
go to the console. Or you can change the /dev/console phrase in the 11th
line (echo "local2.*   /dev/console") to some file, say /var/log/info.
Then everything will go to that file (you might have to "touch /var/log/info"
first, though).

Now you should be able to see what's going wrong. Assuming it's the
chat script.

Take care,

Bill