Subject: Re: Connecting using pppd ...
To: William Gallafent <William.Gallafent@comlab.ox.ac.uk>
From: Chris Gilbert <cg110@york.ac.uk>
List: port-arm32
Date: 05/06/1998 17:59:50
On Tue, 5 May 1998, William Gallafent wrote:

> 
> I hope that this is a case of 'so near, but yet so far'.
> 
> In my quest to banish type 5 errors and singletasking from my machine, I
> am trying to configure netbsd to dialup and connect using pppd to
> compulink. I used various sources of information to add appropriate
> nameservers to resolv.conf, and create a chat script etc.

hmm, try the man pppd pages, that's were I got a lot of my stuff from.
 
> When I initiate the connection, 'pppd call compulink', The chat script
> logs me in OK, and pppd regains control, and states (looking at the debug
> output) 'local IP 197.153.7.54' on one line, followed by 'remote IP
> 194.153.0.x' where x varies from call to call. This all seems sensible. 
> There is a 'defaultroute and a '197.153.7.54:' in
> /etc/ppp/peers/compulink, by the way. The problem is that nothing happens
> next.

check ifconfig -a, does ppp0 show a link on it?

Chris