Ed Doolittle wrote:
>
> On Wed, 22 Mar 2000, Sean Whitney wrote:
>
> > I have been using diald successfully for the last 6 months.
> > In the last 2 days I have had connections problems. If I start
> > wvdial it will connect fine. If I use minicom I can connect fine.
>
> Post your chat script and your wvdial chat script.
>
> --
> Ed Doolittle <mailto:[EMAIL PROTECTED]>
> "Everything we do, we do for a reason." -- Peter O'Chiese
Here is the script connect from /etc/diald/
#!/bin/sh
# Copyright (c) 1996, Eric Schenk.
# Copyright (c) 1997, 1998 Philippe Troin <[EMAIL PROTECTED]> for Debian
GNU/Linux.
#
# $Id:$
#
# This script is intended to give an example of a connection script that
# uses the "message" facility of diald to communicate progress through
# the dialing process to a diald monitoring program such as dctrl or
diald-top.
# It also reports progress to the system logs. This can be useful if you
# are seeing failed attempts to connect and you want to know when and
why
# they are failing.
#
# This script requires the use of chat-1.9 or greater for full
# functionality. It should work with older versions of chat,
# but it will not be able to report the reason for a connection failure.
# Configuration parameters
# When debugging a connection, set DEBUG to -v to increase chat's
# verbosity and to report on this script's progress.
# WARNING: THIS MIGHT CAUSE YOUR PASSWORD TO SHOW UP IN THE SYSTEM LOGS
DEBUG=-v
# The initialization string for your modem
MODEM_INIT1="ATZ"
MODEM_INIT2='ATQ0V1E1S0=0&C1&D2S11=55+FCLASS=0'
# The phone number to dial
PHONE_NUMBER="8160247"
#PHONE_NUMBER="8340452"
# If the remote system calls you back, set to 1; otherwise leave to 0.
CALLBACK=0
# If you authentify using PAP or CHAP (that is let pppd handle the
# authentification, set this to 0.
AUTHENTIFY=1
# The chat sequence to recognize that the remote system
# is asking for your user 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="deleted"
# The chat sequence to recongnize that the remote system
# is asking for your password.
#PASSWD_CHAT_SEQ="word:"
PASSWD_CHAT_SEQ="assword:"
# The string to send in response to the request for your password.
PASSWORD="deleted"
# 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="annex:"
# The command to issue to start up the remote protocol
#PROTOCOL_START="ppp"
# The string to wait for to see that the protocol on the remote
# end started OK. If this is empty then no check will be performed.
START_ACK="Entering PPP"
# Pass a message on to diald and the system logs.
message () {
if [ "$DEBUG" != "" ]
then
[ "$FIFO" != "" ] && echo "message $*" >$FIFO
logger -p local2.info -t connect "$*"
fi
}
# Initialize the modem. Usually this just resets it.
message "Initializing Modem"
chat $DEBUG TIMEOUT 10 "" "$MODEM_INIT1" TIMEOUT 45 OK "$MODEM_INIT2" OK
""
if [ $? != 0 ]; then
message "Failed to initialize modem"
exit 1
fi
# Dial the remote system.
message "Dialing system"
chat $DEBUG \
TIMEOUT 45 \
ABORT "NO CARRIER" \
ABORT BUSY \
ABORT "NO DIALTONE" \
ABORT ERROR \
"" "ATDT$PHONE_NUMBER" \
CONNECT ""
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
# Return here if the script doesn't handle authentification (pppd
should).
if [ "$AUTHENTIFY" == 0 ]; then
exit 0
fi
# We're connected try to log in.
message "Logging in"
chat $DEBUG \
TIMEOUT 5 \
"$USER_CHAT_SEQ" "\\q$USER_NAME" \
TIMEOUT 45 \
"$PASSWD_CHAT_SEQ" "\\q$PASSWORD"
if [ $? != 0 ]; then
message "Failed to log in"
exit 1
fi
# Wait eventually for callback
if [ "$CALLBACK" != 0 ]; then
message "Waiting for callback"
chat $DEBUG \
TIMEOUT 20 \
RING ATA
if [ $? != 0]; then
message "Remote system did not call back"
exit 1
fi
fi
# We logged in, try to start up the protocol (provided that the
# user has specified how to do this)
if [ "$PROMPT" != "" ]; then
message "Starting Comm Protocol"
chat $DEBUG TIMEOUT 15 "$PROMPT" "$PROTOCOL_START"
if [ $? != 0 ]; then
message "Prompt not received"
exit 1
fi
fi
if [ "$START_ACK" != "" ]; then
chat $DEBUG TIMEOUT 15 "$START_ACK" ""
if [ $? != 0 ]; then
message "Failed to start Protocol"
exit 1
fi
fi
# Success!
message "Protocol started"
Here is the wvdial.conf file
-- [Dialer Defaults]
Phone = 8160247
Username = deleted
Password = deleted
New PPPD = yes
Modem = /dev/ttyS1
Baud = 115200
Init1 = ATZ
Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 S11=55 +FCLASS=0
He looked at me as if I were a side dish he hadn't ordered.
-- Ring Lardner
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
