[SLE] Wvdial and Diald
i've been configuring diald to work with wvdial for a while now and i still can't get it to work. the problem is that i get disconnected after 20 seconds. basically, my wvdial works - i run it on the command line and i can go online - no problem. however, if i use it with diald, it times out after 20 seconds. the following is my wvdial.conf file: [Dialer Defaults] Username = xxxxxxx Modem = /dev/ttyS0 Password = xxxxxxxxx Init1 = ATZ Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 S11=55 +FCLASS=0 Tonline = 0 Compuserve = 0 Dial Command = ATDT Phone = ispnumber Baud = 115200 Auto DNS = 1 Stupid Mode = 1 New PPPD = 1 my diald.conf file is as follows: mode ppp connect wvdial device /dev/modem speed 115200 modem lock crtscts local 192.168.0.1 remote 128.135.4.2 dynamic defaultroute include /usr/lib/diald/standard.filter /var/log/messages gives me: Jan 12 10:37:34 alpha pppd[1949]: sent [IPCP ConfReq id=0x2 <addr 128.135.231.199> <compress VJ 0f 01> <ms-dns1 128.135.12.73> <ms-dns3 128.135.4.2>] Jan 12 10:37:35 alpha pppd[1949]: rcvd [IPCP ConfAck id=0x2 <addr 128.135.231.199> <compress VJ 0f 01> <ms-dns1 128.135.12.73> <ms-dns3 128.135.4.2>] Jan 12 10:37:35 alpha pppd[1949]: local IP address 128.135.231.199 Jan 12 10:37:35 alpha pppd[1949]: remote IP address 128.135.231.1 Jan 12 10:37:35 alpha pppd[1949]: primary DNS address 128.135.12.73 Jan 12 10:37:35 alpha pppd[1949]: secondary DNS address 128.135.4.2 Jan 12 10:37:35 alpha pppd[1949]: Script /etc/ppp/ip-up started (pid 1950) Jan 12 10:37:35 alpha ip-up: Modified /etc/resolv.conf for DNS at ppp1 Jan 12 10:37:35 alpha pppd[1949]: Script /etc/ppp/ip-up finished (pid 1950), status = 0x0 Jan 12 10:37:55 alpha diald[1925]: Connect script timed out. Killing script. Jan 12 10:37:55 alpha diald[1925]: Sending SIGINT to (dis)connect process 1948 Jan 12 10:37:55 alpha pppd[1949]: Terminating on signal 15. Jan 12 10:37:55 alpha pppd[1949]: Script /etc/ppp/ip-down started (pid 1959) Jan 12 10:37:55 alpha pppd[1949]: sent [LCP TermReq id=0x2 "User request"] Jan 12 10:37:55 alpha pppd[1949]: rcvd [LCP TermAck id=0x2] Jan 12 10:37:55 alpha pppd[1949]: Connection terminated. Jan 12 10:37:55 alpha pppd[1949]: Connect time 0.6 minutes. Jan 12 10:37:55 alpha pppd[1949]: Sent 440 bytes, received 302 bytes. Jan 12 10:37:55 alpha pppd[1949]: Waiting for 1 child processes... Jan 12 10:37:55 alpha pppd[1949]: script /etc/ppp/ip-down, pid 1959 Jan 12 10:37:55 alpha ip-down: Restored original /etc/resolv.conf Jan 12 10:37:55 alpha pppd[1949]: Script /etc/ppp/ip-down finished (pid 1959), status = 0x0 Jan 12 10:37:55 alpha pppd[1949]: Exit. Jan 12 10:37:55 alpha diald[1925]: connector: --> Disconnecting at Wed Jan 12 10:37:55 2000 Jan 12 10:37:56 alpha diald[1925]: Delaying 30 seconds before clear to dial. SLIP with keepealive and linefill (not used) is compiled in the kernel for diald, thus the message at boot.msg: <6>TCP compression code copyright 1989 Regents of the University of California <6>PPP line discipline registered. <6>SLIP: version 0.8.4-NET3.019-NEWTTY (dynamic channels, max=256) (6 bit encapsulation enabled). <6>SLIP linefill/keepalive option. however, when i run diald on the command line, i get (from/var/log/messages): Jan 12 10:58:15 alpha modprobe: modprobe: Can't locate module tap0 Jan 12 10:58:15 alpha modprobe: modprobe: Can't locate module tap1 Jan 12 10:58:15 alpha modprobe: modprobe: Can't locate module tap2 Jan 12 10:58:15 alpha modprobe: modprobe: Can't locate module tap3 Jan 12 10:58:15 alpha modprobe: modprobe: Can't locate module tap4 Jan 12 10:58:15 alpha modprobe: modprobe: Can't locate module tap5 Jan 12 10:58:16 alpha modprobe: modprobe: Can't locate module tap6 Jan 12 10:58:16 alpha modprobe: modprobe: Can't locate module tap7 Jan 12 10:58:16 alpha modprobe: modprobe: Can't locate module tap8 Jan 12 10:58:16 alpha modprobe: modprobe: Can't locate module tap9 Jan 12 10:58:16 alpha modprobe: modprobe: Can't locate module tap10 Jan 12 10:58:16 alpha modprobe: modprobe: Can't locate module tap11 Jan 12 10:58:17 alpha modprobe: modprobe: Can't locate module tap12 Jan 12 10:58:17 alpha modprobe: modprobe: Can't locate module tap13 Jan 12 10:58:17 alpha modprobe: modprobe: Can't locate module tap14 Jan 12 10:58:17 alpha modprobe: modprobe: Can't locate module tap15 Jan 12 10:58:17 alpha diald[2122]: start sl0: SIOCSIFMETRIC: Operation not supported any thoughts? PS: i have tried wvdial.dod but i get a failure in the connect script using wvdial. mac -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
On Wed, 12 Jan 2000, Mac Q. Flores IV wrote:
i've been configuring diald to work with wvdial for a while now and i still can't get it to work. the problem is that i get disconnected after 20 seconds.
Don't use diald, they don't get along. Look here: http://sdb.suse.de/sdb/en/html/hoe_wv_dod_start.html -- -=|JP|=- Jon Pennington | Atipa Linux Solutions -o) jpennington@atipa.com | http://www.atipa.com /\\ Kansas City, MO, USA | 816-241-2641 _\_V -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
Jon Pennington wrote:
On Wed, 12 Jan 2000, Mac Q. Flores IV wrote:
i've been configuring diald to work with wvdial for a while now and i still can't get it to work. the problem is that i get disconnected after 20 seconds.
Don't use diald, they don't get along. Look here:
Oh but they do get along. Mac used diald to invoke wvdial by itself. Wvdial makes the connection and starts pppd _but_does_not_quit_. Diald sees this as an error, as it should, and kills wvdial. Wvdial than disconnects like it should do. The trick is (with the latest wvdial) to let it be invoked by diald with the switch --chat . Now diald should pipe i/o from wvdial to your serial device. Wvdial makes the connection and quits without dropping the line. At that point diald invokes pppd and all is well. The one thing that didn't make this work for me in the first run was that diald did not pipe the i/o properly (or I did something wrong somewhere I am unaware of / not knowledgable about). So I put in my diald.something the following: connect "wvdial --chat >/dev/modem </dev/modem" This should also make other dialing scripstworking like chat etc. Hope this helps. BB, Arjen -- Sell what you use, use what you sell. -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
At 11:46 AM 01/12/2000 -0600, you wrote:
Don't use diald, they don't get along. Look here:
Howdy Jon, just tried that script and SuSE's directions - it doesn't seem to work. :-( Open question to everyone: Has anyone got wvdial.dod working properly yet? After I get this fixed, I'll have to figure out why Marc Heuse's Firewals 2.0 script is fighting so vehemently with wvdial's ability to change the route. I have to do an "/sbin/init.d/firewall restart" each time I make a connection manually with wvdial. *sigh* -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
On Sun, 20 Feb 2000, Argentium G. Tiger wrote:
At 11:46 AM 01/12/2000 -0600, you wrote:
Don't use diald, they don't get along. Look here:
Howdy Jon, just tried that script and SuSE's directions - it doesn't seem to work. :-(
Open question to everyone: Has anyone got wvdial.dod working properly yet?
I am using wvdial.dod quite happily. After trying the script on the SuSE US web page without success, I located the one on the German page. You have to be careful about line breaks. The other problem I ran into was extraneous characters at the end of each line. However, that may have come from using a Windows text editor to start with. I would be happy to email my version of the wvdial.dod script if you would like to look at it. Harry -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
participants (5)
-
agtiger@grapevine.net
-
arjen@technologist.com
-
bc550@scn.org
-
jpennington@atipa.com
-
mflores@uchicago.edu