On Fri, 7 May 1999, Sergey N. Ivanov wrote:

> I use NetBSD 1.3.3 with wrstuden.ppp.setup package on Macintosh IIsi. 
> After connecting to my ISP  ping and ftp hangs and gives not any answer, while netstat tells 
> "netstat: kvm-read: Bad address".
> In /var/log/messages this connection reflected by such lines:
> 
> May  6 23:48:13  chat[326]: ATDP9715702^M^M 
> May  6 23:48:13  chat[326]: CONNECT 19200^M 
> May  6 23:48:15  chat[326]: login: -- got it 
> May  6 23:48:15  chat[326]: send (seriv ppp^M) 
> May  6 23:48:16  chat[326]: expect (word:) 
> May  6 23:48:16  chat[326]:  seriv ppp^M 
> May  6 23:48:16  chat[326]: Password: -- got it 
> May  6 23:48:16  chat[326]: send (????????^M) 
> May  6 23:48:17  pppd[308]: Serial connection established.
> May  6 23:48:18  pppd[308]: Using interface ppp0
> May  6 23:48:18  pppd[308]: Connect: ppp0 <--> /dev/tty00
> May  6 23:48:20  /netbsd: ppp0: no compressor for [15 3 29], 3
> May  6 23:48:20  /netbsd: ppp0: no compressor for [18 4 8], 4
> May  6 23:48:20  pppd[308]: local  IP address 194.154.81.36
> May  6 23:48:20  pppd[308]: remote IP address 195.218.218.102

You're connected. Can you ping anyone if you specify an ip address?
`route -n show | grep default -' should give "default 195.218.218.102
UG". If the answer to both questions is "yes", then it's only your
nameservice that's not set up correctly. You have specified a
nameserver in /etc/resolv.conf, and /etc/resolv.conf is world
readable? You could use `nslookup' to verify the ip address of the
nameserver, like so: `nslookup - 206.54.252.3', substituting the ip of
your chosen nameserver, of course. You'll get a `>', at which you can
query names, among other things (type ? for help). That's the number
of a real nameserver, BTW, but you should put your own isp's
designated nameserver in your resolv.conf.