Re: diald -- help or source!
In the message log I see that it attempts to open the connection, and immediately reports that the connection script failed. It doesn't seem to access the modem or anything. Please post the script, the log, and /etc/diald/diald.options. I can't get chat to run a simple connect script either. What do you mean by that? I'm not afraid to get into it with a debugger and really screw things up No need for that. I'm sure you just have a configuration error. -- John HaslerThis posting is in the public domain. [EMAIL PROTECTED]Do with it what you will. Dancing Horse Hill Make money from it if you can; I don't mind. Elmwood, Wisconsin Do not send email advertisements to this address.
Re: diald -- help or source!
From: John Hasler [EMAIL PROTECTED] To: Tracy Nelson [EMAIL PROTECTED] Cc: debian-user@lists.debian.org debian-user@lists.debian.org Date: Monday, June 21, 1999 20:41 Subject: Re: diald -- help or source! In the message log I see that it attempts to open the connection, and immediately reports that the connection script failed. It doesn't seem to access the modem or anything. Please post the script, the log, and /etc/diald/diald.options. My connection script is simple editing of the original to whit: +++ MODEM_INIT=ATZC1D2%C0 connect 130 lines, 3693 characters # The phone number to dial # PHONE_NUMBER=5551212 PHONE_NUMBER=6109433278 # The chat sequence to recognize that the remote system # is asking for your user name. # USER_CHAT_SEQ=name:--name:--name:--name:--name:--name:--name: USER_CHAT_SEQ=ogin:--ogin:--ogin:--ogin:--ogin:--ogin:--ogin: # The string to send in response to the request for your user name. USER_NAME=tnelson # The chat sequence to recongnize that the remote system # is asking for your password. PASSWD_CHAT_SEQ=word: # The string to send in response to the request for your password. PASSWORD=*elided* # The prompt the remote system will give once you are logged in # If you do not define this then the script will assume that # there is no command to be issued to start up the remote protocol. PROMPT=tion } # Initialize the modem. Usually this just resets it. message Initializing Modem chat $DEBUG TIMEOUT 5 $MODEM_INIT TIMEOUT 5 OK if [ $? != 0 ]; then message Failed to initialize modem exit 1 fi # Dial the remote system. message Dialing system chat $DECONNECT HONE_NUMBER \ case $? in 0) message Connected;; 1) message Chat Error; exit 1;; 2) message Chat Script Error; exit 1;; 3) message Chat Timeout; exit 1;; 4) message No Carrier; exit 1;; 5) message Busy; exit 1;; 6) message No DialTone; exit 1;; 7) message Modem Error; exit 1;; *) esac exit 1 fi fi if [ $START_ACK != ]; then chat $DEBUG TIMEOUT 15 $START_ACK if [exit 1e Failed to start Protocol fi fi # Success! message Protocol started === The log file is pretty simple, just: +++ Jun 21 09:12:48 spicerack diald[24824]: Running connect (pid = 24973). Jun 21 09:12:48 spicerack diald[24824]: Connect script failed. Jun 21 09:12:49 spicerack diald[24824]: Delaying 30 seconds before clear to dial . === My options file looks like this: +++ mode ppp connect /etc/diald/connect device /dev/ttyS0 speed 115200 modem lock crtscts local 10.0.0.3 remote 192.168.0.2 dynamic defaultroute include /etc/diald/standard.filter === I can't get chat to run a simple connect script either. What do you mean by that? Whenever I try something simple like chat -V 'ATZ' I get no response for several seconds (I suspect a timeout) and if I ^C during this time I get an I/O operation incomplete error (or something like that). Thanks very much for any clues anyone can drop in my general direction! Cheers! -- Tracy
Re: diald -- help or source!
Tracy Nelson writes: My connection script is simple editing of the original to whit: +++ MODEM_INIT=ATZC1D2%C0 connect 130 lines, 3693 characters # The phone number to dial ... Is this the exact complete script? If so, you have two problems: a) The first and third lines are extraneous garbage. b) The first line must be #!/bin/sh . I prefer to change the 'connect' line in /etc/diald/diald.options to read connect chat -v -f /etc/chatscripts/provider and use the chatscript generated by pppconfig. -- John HaslerThis posting is in the public domain. [EMAIL PROTECTED]Do with it what you will. Dancing Horse Hill Make money from it if you can; I don't mind. Elmwood, Wisconsin Do not send email advertisements to this address.
diald -- help or source!
diald is dying when trying to run the connect script. In the message log I see that it attempts to open the connection, and immediately reports that the connection script failed. It doesn't seem to access the modem or anything. pppd works just fine, but I can't get chat to run a simple connect script either. Can someone tell me what to look for? Or, alternately, tell me where I might find the source for diald? I'm not afraid to get into it with a debugger and really screw things up... ;) Cheers! -- Tracy
diald help!
Hi. I have a working diald setup on a Debian2.0 box but there are a couple of messages in the log that I can't seem to find a solution to. The items are logged when the link comes down. These are the lines with my comments added: : Closing down idle link;no problem here : Terminating on signal 2 ;can't find a reference ;for this. : Connection terminated ;no problem here either : Failed;what failed? : disconnect script failed ;can't seem to get any ;disconnect script to work. ;Any suggestions? : Exit. ;OK. : Delaying 10 seconds before clear to dial. I changed a parameter to make it 10 seconds between redials, but why does diald end it's session with this line, which makes you wait 10 seconds before dialing a new connection? Diald has been working for about two weeks with no problems, but these messages seem to indicate that something is not right. Any suggestions? thanks, -- tony mollica [EMAIL PROTECTED]
Re: diald help!
On Tue, Jan 19, 1999 at 06:52:37AM +, tony mollica wrote: Hi. I have a working diald setup on a Debian2.0 box but there are a couple of messages in the log that I can't seem to find a solution to. The items are logged when the link comes down. These are the lines with my comments added: : Closing down idle link;no problem here : Terminating on signal 2 ;can't find a reference ;for this. This is fine, it means that diald considers your link to be idle (according to /etc/diald/standard.filter) and wants to close it, so sends a SIGINT to pppd, the second line is from that. : Connection terminated ;no problem here either : Failed;what failed? : disconnect script failed ;can't seem to get any ;disconnect script to work. ;Any suggestions? You don't need a disconnect script since your modem most likely support hardware resets. If it does not, just make a script that looks like this: -- #!/bin/sh echo +++ /dev/modem echo ath /dev/modem echo atz /dev/modem -- only if simply not having a disconnect line in diald.options does not work. : Exit. ;OK. : Delaying 10 seconds before clear to dial. I changed a parameter to make it 10 seconds between redials, but why does diald end it's session with this line, which makes you wait 10 seconds before dialing a new connection? Not sure, maybe because it thinks disconnect failed? -- Rafael Kitover [EMAIL PROTECTED] pgpOfNAyWHSRR.pgp Description: PGP signature
