On Thursday, January 09, 2003 1:50 PM [GMT+0530=IST],
[EMAIL PROTECTED] (Srinivasa Pradeep) wrote:
> --- Philip S Tellis <[EMAIL PROTECTED]>
>> Only problem that I have with wvdial is that the
>> only way to terminate
>> it is by killing the process. this kills pppd
>> immediately, as a result
>> of which, /etc/ppp/{ip-down,ip-down.local} aren't
>> executed.
>>
>> Does anyone know how to fix this? Should I kill
>> pppd instead of killing
>> wvdial?
>>
> Even I used earlier wvdial, but the problem was I have
> accounts with two different ISP, and if I use wvdial,
> I have to set the DNS in the resolv.conf everytime.
> I thought if I use pppd with usepeerdns, i don't need
> to set the DNS entries again and again.
That doesn't have anything to do with philip's question - and yes,
usepeerdns should work, as should running a local caching namserver like
dnscache (http://cr.yp.to/djbdns/dnscache.html)
Though, this is a bit unnecessary here, considering that most local ISPs
are stupid enough to allow their nameservers to serve as recursive
resolvers to the world over (that is, if someone from an unauthorized IP
block queries their nameserver, they must only return queries for
domains they are authoritative for, rather than for random domains).
So, even if you are dialed in with satyam or eth.net, you can use (say)
vsnl's dns servers exclusively.
Philip - Try killing pppd - and set wvdial not to redial (or it
auto-retries).
srs
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
linux-india-help mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/linux-india-help
