Re: SUSE, YaST and dial-up failure

[Andy Leach]

As Chris and Matthew have asked me the same question pretty much, should 
I only respond to one to pull the thread together as I have here, or 
both? What is list etiquette for such situations?
Matthew Gregan wrote:

At 2004-11-12T11:54:53+1300, Andy Leach wrote:
 

OKAY!!! it dialed, I got a connection, I heard the modem doing its 
thing. All 3 packets went and came back safely without loss in 278ms, 
279ms and 278ms
   

Good news.
 

the kinternet connection has now got two plugs, however, ping 
www.google.com gives the same name failure problem as does ftp
   

Okay, that explains the RFC1918 address you start off with after
starting KInternet--since you're using dial-on-demand, you need some
valid and unique address for the ppp0 device.  Once traffic passes
across that connection, the dial up is triggered.
(I don't use dial-on-demand, so I haven't seen this before.)
 

I'm saying that i get a kinternet log of
   

 

SuSE Meta pppd ( smpppd-ifcfg), Version 1.16 on linux
   

[...]
 

Status is: lurking
pppd[0]:  local IP address 192.168.99.1
pppd[0]:  remote IP address 192.168.99.99
regardless of whether th modem is plugged in or not, yes. with the 
connection in place now the next lines added are
   

Right.  That makes sense given the use of dial-on-demand.
 

pppd[0]:  starting link
Establishing connection due to activity
   

If you run the following after this point, you should find that ppp0 has
a public IP address:
# ifconfig ppp0
 

it gives me
   link encap: Point-to-Point Protocol
   inet addr: 202.150.99.252    P-t-P: 192.168.251.74   Mask 
255.255.255.255
   UP POINTTOPOINT RUNNING NOARP MUTLICAST MTU: 1500 Metric: 1
   RX packets: 6 errors: 1 dropped: 0 overruns: 0 frame: 0
   TX  packets: 9 errors: 0 dropped: 2 overruns: 0 frame: 0
   collisions: 0   txqueuelen: 3
   RX bytes: 186 (180.0 b)   TX bytes: 351 (351.0 b)

ifconfig also gave me entries for eth0 and lo I assumed the details 
weren't required here.

 

it then goes on with various line of initialization, authentication
etc.  all of which seems to have been succesful - is the full log
entry required here?
   

 

hopefully this gives a new pointer to what exactly i did here...
thanks
   

Well, we've come somewhat full circle.  Can you tell us where you're
seeing the "/etc/resolv.conf does not exist" error you mentioned in your
first post about this problem?  

bugger, I don't remember where it was - can I re-'touch' the file to 
bring the error back?

That file is supposed to contain details
of your ISPs DNS servers; without those details, domain name lookups
(e.g. trying to find out the IP address of www.google.com) will fail.
For a standard pppd(8), specifying 'usepeerdns' in your /etc/ppp/options
file is the usual way to get pppd(8) to store the ISP-supplied DNS
details into /etc/resolv.conf.  There should be an easier way to ensure
this happens via SuSE's graphical configuration utilities, though.  I'm
not familiar with SuSE dial-up stuff, so perhaps Volker can fill in the
details.
Cheers,
-mjg