Matthew Gregan wrote:
At 2004-11-12T10:30:41+1300, Andy Leach wrote:
and ping -c3 google.comping: unknown host google.com
These failures all make sense based on the error you reported earlier relating to /etc/resolv.conf.
When you're connected, can you try pinging www.google.com by one of its IP addresses, e.g.:
$ ping -c3 66.102.7.99
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
the kinternet connection has now got two plugs, however, ping www.google.com gives the same name failure problem as does ftp
However, what _really_ doesn't make sense is that you seem to be saying that, even with the modem physically disconnected from the telephone line, the dial-up and login process appears to work and you appear to receive an IP address in the 192.168.99.0/24 range. Is that correct, or have I misunderstood?
I'm saying that i get a kinternet log of
SuSE Meta pppd ( smpppd-ifcfg), Version 1.16 on linux Status is: disconnected trying to connect to smpppd connect to smpppd Status is: disconnected Status is: lurking pppd[0]: Plugin passwordfd.so loaded pppd[0]: Using interface ppp0 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
pppd[0]: starting link
Establishing connection due to activity
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
Cheers,
-mjg
