Sat, 17 Jul 2004 14:36:03 -0400 tarihinde, Cat dedi ki:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On Fri, 16 Jul 2004 20:17:03 +0300, Abdullah Ramazanoglu wrote:
>
>> --8<--
>>> Also the nameservers appear to be set for kppp and not for wvdial.
>>
>> Bingo!
>>
>> --8<--
>>
>> Your problem is that you don't get DNS addresses.
> Unfortuately it aint that simple.
>
> ping -n 216.109.127.30
>
> doesn't work with wvdial but does with kppp with identical routing tables.
> I have the nameserver entries in my /etc/resolv.conf
>
> search telstra.net
> nameserver 139.130.4.4
> nameserver 203.50.2.71

When I saw no DNS negotiation in the wvdial logs, I think I plunged into
that prematurely. Well, then could it be a defaultroute issue? From the
logs it is clear that both sides negotiate successfully and your pppd gets
remote and local IP addresses. There is a "defaultroute" parameter to
pppd, which can be given in /etc/ppp/options or wvdial.conf file.

Another common problem regarding defaultroute is when your machine has an
ethernet card an already assigned a default route (to eth0) before pppd
started. Then pppd sometimes adds a defaultroute (to ISP) without deleting
the already established defaultroute (to eth0) first. I guess kppp might
be a bit smarter to detect this situation and delete eth0 defaultroute
itself. I don't remember whether wvdial had such an option somewhere. But
even if it doesn't, you could still handle such an issue by not assigning
a default route to eth0 in the first place. (either/both in the
/etc/sysconfig/network and /etc/sysconfig/network-scripts/ifcfg-eth0)

If it isn't a defaultroute issue, then I can't think of another culprit,
currently.

--
Abdullah | aramazan@ |
Ramazanoglu | myrealbox |
________________| D O T cöm |