Greetings, Hoping somebody can help with my diald problem. It was suggested I turn on debug and look at the log. Added debug option to /etc/ppp/options and /etc/diald.conf I also removed proxyarp. Here is the output from /var/log/debug Dec 13 21:05:58 mycomputer diald[653]: Starting diald version 0.16.5 Dec 13 21:05:58 mycomputer diald[653]: Proxy device established on interface sl0 Dec 13 21:05:58 mycomputer diald[653]: running '/sbin/ifconfig sl0 local.IP.address pointopoint 95.box.IP.address mtu 1500 up' Dec 13 21:06:00 mycomputer diald[653]: SIGCHLD[1]: pid 654 system, status 0 Dec 13 21:06:00 mycomputer diald[653]: Setting pointopoint route for sl0 Dec 13 21:06:00 mycomputer diald[653]: running '/sbin/route add 95.box.IP.address metric 1 dev sl0' Dec 13 21:06:00 mycomputer diald[653]: SIGCHLD[2]: pid 660 system, status 0 Dec 13 21:06:00 mycomputer diald[653]: Establishing routes for sl0 Dec 13 21:06:00 mycomputer diald[653]: running '/sbin/route add default metric 1 netmask 0.0.0.0 dev sl0' Dec 13 21:06:00 mycomputer diald[653]: SIGCHLD[3]: pid 661 system, status 0 Dec 13 21:06:00 mycomputer diald[653]: Changed snoop device to sl0 Dec 13 21:06:00 mycomputer diald[653]: Diald initial setup completed. Dec 13 21:06:02 mycomputer diald[653]: new state CONNECT action 0x804ee14 timeout 60 Dec 13 21:06:03 mycomputer diald[653]: Running connect (pid = 663). Dec 13 21:06:03 mycomputer chat[663]: report (CONNECT) Dec 13 21:06:03 mycomputer chat[663]: abort on (BUSY) Dec 13 21:06:03 mycomputer chat[663]: abort on (ERROR) Dec 13 21:06:03 mycomputer chat[663]: abort on (NO CARRIER) Dec 13 21:06:03 mycomputer chat[663]: abort on (NO DIALTONE) Dec 13 21:06:03 mycomputer chat[663]: abort on (NO ANSWER) Dec 13 21:06:03 mycomputer chat[663]: send (ATZ^M) Dec 13 21:06:03 mycomputer diald[653]: SIGCHLD[4]: pid 663 dial, status 1024 Dec 13 21:06:03 mycomputer diald[653]: Connect script failed. Dec 13 21:06:03 mycomputer diald[653]: new state CLOSE action 0x804f4a0 timeout -1 Dec 13 21:06:03 mycomputer diald[653]: Closing modem line. Dec 13 21:06:03 mycomputer chat[663]: expect (OK) Dec 13 21:06:03 mycomputer chat[663]: report (CONNECT) Dec 13 21:06:03 mycomputer chat[663]: abort on (BUSY Dec 13 21:06:03 mycomputer chat[663]: -- failed Dec 13 21:06:03 mycomputer chat[663]: Failed (BUSY) Dec 13 21:06:04 mycomputer diald[653]: Delaying 30 seconds before clear to dial. doesn't do anything for me but I'm hoping someone else finds it meaningful. Rod Pike wrote: > Any information that can help solve my problem would be greatly > appreciated. > > Here are the details > > redhat ver 5.1 > diald ver 0.16.5 > ppp ver 2.3.3 > > here are my files with user specific information changed to protect the > niave:) > > /etc/ppp/chatscript > > REPORT CONNECT > ABORT BUSY > ABORT ERROR > ABORT "NO CARRIER" > ABORT "NO DIALTONE" > ABORT "NO ANSWER" > '' ATZ > OK IPphoneNumber > 'ipname :' myuserid > Password: mypassword > > /etc/diald.conf > > mode ppp > connect '/usr/sbin/chat -v -s -f /etc/ppp/chatscript' > device /dev/cua1 > speed 115200 > modem > lock > crtscts > local localIPaddress > remote remoteIPaddress > dynamic > defaultroute > proxyarp > include /usr/lib/diald/standard.filter > retry-count 2 > redial-timeout 30 > > I start up ppp with the following script > > /root/startppp > > #!/bin/sh > /usr/sbin/pppd /dev/cua1 115200 connect 'chat -v -s -f > /etc/ppp/chatscript' defaultroute crtscts proxyarp lock > > When I try diald it fails initializing the modem and aborts the chat > script. I'm using the exact same chatscript for ppp and diald > > here is what the /var/log/message looks like for a successful ppp > > Dec 13 20:32:26 mycomputer pppd[508]: pppd 2.3.3 started by root, uid 0 > Dec 13 20:32:27 mycomputer chat[509]: report (CONNECT) > Dec 13 20:32:28 mycomputer chat[509]: abort on (BUSY) > Dec 13 20:32:28 mycomputer chat[509]: abort on (ERROR) > Dec 13 20:32:28 mycomputer chat[509]: abort on (NO CARRIER) > Dec 13 20:32:28 mycomputer chat[509]: abort on (NO DIALTONE) > Dec 13 20:32:28 mycomputer chat[509]: abort on (NO ANSWER) > Dec 13 20:32:28 mycomputer chat[509]: send (ATZ^M) > Dec 13 20:32:28 mycomputer chat[509]: expect (OK) > Dec 13 20:32:28 mycomputer chat[509]: ATZ^M^M > Dec 13 20:32:28 mycomputer chat[509]: OK > Dec 13 20:32:28 mycomputer chat[509]: -- got it > Dec 13 20:32:28 mycomputer chat[509]: send (ATDT5551212^M) > Dec 13 20:32:28 mycomputer chat[509]: expect (myIPname :) > Dec 13 20:32:28 mycomputer chat[509]: ^M > Dec 13 20:32:43 mycomputer chat[509]: ATDT5551212^M^M > Dec 13 20:32:43 mycomputer chat[509]: CONNECT > 33600/ARQ/V34/LAPM/V42BIS^M > Dec 13 20:32:44 mycomputer chat[509]: ^M^M > Dec 13 20:32:44 mycomputer chat[509]: myIPname : > Dec 13 20:32:44 mycomputer chat[509]: -- got it > Dec 13 20:32:44 mycomputer chat[509]: send (myuserid^M) > Dec 13 20:32:44 mycomputer chat[509]: expect (Password:) > Dec 13 20:32:44 mycomputer chat[509]: mypassword^M > Dec 13 20:32:44 mycomputer chat[509]: Password: > Dec 13 20:32:44 mycomputer chat[509]: -- got it > Dec 13 20:32:44 mycomputer chat[509]: send (mypasswrod^M) > Dec 13 20:32:44 mycomputer pppd[508]: Serial connection established. > Dec 13 20:32:45 mycomputer pppd[508]: Using interface ppp0 > Dec 13 20:32:45 mycomputer pppd[508]: Connect: ppp0 <--> /dev/cua1 > > and the failed diald log > > Dec 13 20:09:15 mycomputer diald[2207]: found interface eth0 for proxy > arp > Dec 13 20:09:25 mycomputer diald[2207]: Running connect (pid = 2220). > Dec 13 20:09:26 mycomputer chat[2220]: report (CONNECT) > Dec 13 20:09:26 mycomputer chat[2220]: abort on (BUSY) > Dec 13 20:09:26 mycomputer chat[2220]: abort on (ERROR) > Dec 13 20:09:26 mycomputer chat[2220]: abort on (NO CARRIER) > Dec 13 20:09:26 mycomputer chat[2220]: abort on (NO DIALTONE) > Dec 13 20:09:26 mycomputer chat[2220]: abort on (NO ANSWER) > Dec 13 20:09:26 mycomputer chat[2220]: send (ATZ^M) > Dec 13 20:09:26 mycomputer diald[2207]: Connect script failed. > Dec 13 20:09:26 mycomputer chat[2220]: expect (OK) > Dec 13 20:09:26 mycomputer chat[2220]: report (CONNECT) > Dec 13 20:09:26 mycomputer chat[2220]: abort on (BUSY > Dec 13 20:09:26 mycomputer chat[2220]: -- failed > Dec 13 20:09:26 mycomputer chat[2220]: Failed (BUSY) > Dec 13 20:09:27 mycomputer diald[2207]: Delaying 30 seconds before clear > to dial. > > Any ideas??? > > Thanks in advance > > Cheers, > > Rod > > [EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe linux-diald" in the body of a message to [EMAIL PROTECTED]
