On Sun 11 Mar 01, 8:40 PM, Larry Snyder said:
> Pete,
>
> Here are the pieces of the various outputs and files you asked for
> (if they don't screw up wrapping between here and there). As you can see
> the inet addr in the ifconfig output is the same as in the
> /var/log/messages file. But the resolv.conf is just empty comments:
>
> #
> # /etc/resolv.conf
> #
hmmm. this looks like a problem to me. it's been awhile since i've
worried about modems, but i'm pretty sure you need nameservers here.
the really odd thing is that you say that root has nameserving. my guess is
that kppp sets up some kind of nameserving. it's prolly not 'working' for
your user accounts.
this file should have the form:
search mysearch.edu
nameserver 123.45.67.89
nameserver 123.45.67.80
where mysearch.edu is a kind of default search (not required). the
nameserver fields are your DNS servers. you had to enter this into kppp
when you set it up.
> ppp0 Link encap:Point-to-Point Protocol
> inet addr:168.150.192.101 P-t-P:168.150.253.19 Mask:255.255.255.255
looks good.
> lds@linux:/sbin > route -n
> Kernel IP routing table
> Destination Gateway Genmask Flags Metric Ref Use Iface
> 168.150.253.19 0.0.0.0 255.255.255.255 UH 0 0 0 ppp0
> 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
> 0.0.0.0 168.150.253.19 0.0.0.0 UG 0 0 0 ppp0
> lds@linux:/sbin >
looks ok.
> lds@linux:~ > ls -l /usr/sbin/pppd
> -rwsr-sr-- 1 root dialout 176288 Jan 19 09:41 /usr/sbin/pppd
ok, i just wanted to make sure it was suid.
> >From /var/log/messages:
>
> Mar 11 19:37:08 linux pppd[744]: local IP address 168.150.192.101
> Mar 11 19:37:08 linux pppd[744]: remote IP address 168.150.253.19
i think we narrowed it down to a nameserving problem. fix resolv.conf and
see if that helps things.
pete
