Message-ID: <3A2DDFD0.63339DB1@gte.net> Date: Tue, 05 Dec 2000 22:42:24 -0800 From: emanon <charles.randle@gte.net> Subject: Re: [SLE] Wvdial quirk phoenix- odd- the first time i tried your suggestion (wvdialconf > dev null) i clicked new messages in netscape's email and dial-on-demand found my modem and dialed it correctly. that was the last and only time it worked... i'm using suse v6.4 which from my reading seems to have problems with dial-on-demand. i'm stumped. any ideas? thanks- larry phoenix wrote:
emanon wrote:
phoenix-
thanks for the suggestion. i have been trying to get dial-on-demand working for several days without any luck. <wvdialconf >dev null> worked! as far as i can tell it wrote the modem configuration to dev null. i didn't see anything referring to this in the documentation, suse database or the achieves of this list.
thanks-
larry
Larry,
Your'e welcome. It was actually part of the documentation. That's how I found out about it in the first place. (I'm not sure where though. I think it may have been in the "wvdialconf -h" or "info wvdialconf" something like that ! :)
Have fun
From: Jonathan Drews <j.e.drews@worldnet.att.net> Date: Wed, 6 Dec 2000 00:53:34 -0600 Message-Id: <00120600575600.02868@linux> Subject: Re: [SLE] Wvdial quirk You might want to look at this URL in the suse data base: http://sdb.suse.de/sdb/en/html/hoe_wvdod64.html Here is a synopsis: ------------------------------------------------------ After using the automatic modem detection the dial on demand for modems and ISDN-terminaladapters with wvdial.dod doesn't work. In the file /var/log/messages you can find lines like this Apr 12 17:36:39 Erde /usr/sbin/rcwvdial.dod[4334]: starting pppd 192.168.99.1:192.168.99.99 /dev/ttyS4 Analog Modem 115200 modem crtscts defaultroute -detach user suse ipcp-accept-local ipcp-accept-remote usepeerdns call wvdial demand idle 180 connect "/usr/bin/wvdial^I--chat "... PID=4368 Launching the command ps ax | grep pppd shows that the pppd daemon is not running. Cause: The file /etc/wvdial.conf can contain more than one entry for the keyword Modem. This cannot be resolved correctly by the wvdial.dod script. ----------------------------------------------- <p> There are other tips for wvdial in the Support Data base. I had Wvdial working in SuSE 6.4 and it was grand. I can't remember which article from the support data base I used but the solution is there. Hope this helps Jonathan
Message-ID: <3A2DE496.7374B560@gte.net> Date: Tue, 05 Dec 2000 23:02:46 -0800 From: emanon <charles.randle@gte.net> Subject: Re: [SLE] Wvdial quirk jonathon- thanks for the suggestion. that's the first thing i tried several days ago. on my v6.3 toaster that died a few weeks ago in a severe wind storm, i used kppp. when i switched the dial-up services over to my 6.4 box which was functioning just as a file server, i tried to implement wvdial and dod. i've researched the suse db but nothing so far has worked. i'm beginning to suspect my modem, a 56kb/call-waiting type of dubious pedigree. it did actually work once and only once as described below. thanks- larry <p><p>Jonathan Drews wrote:
You might want to look at this URL in the suse data base:
http://sdb.suse.de/sdb/en/html/hoe_wvdod64.html
Here is a synopsis:
------------------------------------------------------ After using the automatic modem detection the dial on demand for modems and ISDN-terminaladapters with wvdial.dod doesn't work.
In the file /var/log/messages you can find lines like this Apr 12 17:36:39 Erde /usr/sbin/rcwvdial.dod[4334]: starting pppd 192.168.99.1:192.168.99.99 /dev/ttyS4 Analog Modem 115200 modem crtscts defaultroute -detach user suse ipcp-accept-local
ipcp-accept-remote usepeerdns
call wvdial demand idle 180 connect "/usr/bin/wvdial^I--chat "... PID=4368
Launching the command ps ax | grep pppd shows that the pppd daemon is not running.
Cause:
The file /etc/wvdial.conf can contain more than one entry for the keyword Modem. This cannot be resolved correctly by the wvdial.dod script. -----------------------------------------------
There are other tips for wvdial in the Support Data base. I had Wvdial working in SuSE 6.4 and it was grand. I can't remember which article from the support data base I used but the solution is there.
Hope this helps
Jonathan
participants (2)
-
charles.randle＠gte.net -
j.e.drews＠worldnet.att.net