[EMAIL PROTECTED] wrote:
>okokok, i was intempestuous. probably frustrated with my failing to make
>diald work. still am. maybe i do not understand enough linux. is Wvdial the
>same thing or does it only replace a chatscript?
>
>fred
Apparently, wvdial is a "smart" replacement for the "chat" program and
associated chat script. From their web page, I see that wvdial figures out
modem parameters automagically. It also handles configuring pap-secrets,
ppp options and the like.
I've actually not had many problems with getting the actual modem part of a
diald setup working, at least not with modern modems. Usually, the only
initialization command I need is "AT&F" or something like that.
In addition, most of the ISPs I've seen (at least in Belgium) use terminal
servers which either directly start up ppp if you give them a ppp name and
password, or (and here's where it gets interesting) they'll respond with
login: and password: prompts if you hit return after connecting instead of
automatically negotiating pap authentication.
Thus you can check out if a chat script should work by using minicom to
manually dial the ISP's number, and hitting return a couple of times. If
you see login: then enter your ISP account name, and send your password in
response to the password: prompt. You should then see a bunch of garbage
characters on your screen as ppp starts up at the other end. This means
that the login can easily be done by chat. If not, you're SOL so search the
list archives for information about pap based logins.
Then in the diald.conf file somewhere, put the line:
device /dev/ttyS1
to choose the modem you'll be using, and:
connect "/usr/sbin/chat -vf /etc/ppp/chatfile"
To tell diald to use chat and the chat file to connect, and be verbose
about it.
My chat file looks like this:
ABORT BUSY ABORT 'NO CARRIER' ABORT 'NO DIALTONE'
'' 'AT&F2'
OK AT\dD023001111\d
CONNECT ''
ogin:--ogin: XXXXX
assword:--assword: \qYYYYYYYY
Note that the "\q" just makes the password not appear in the log files, and
"\d" introduces a slight delay before sending the following characters, in
this case so that we have time to get a dial tone.
And that's that for the actual connection. You still have to configure the
rest of diald, but you'll find some examples in the documentation, on the
list archives, and on various pages scattered throughout the Web.
Remember, local2.log is your friend. You can figure out what diald is doing
by reading that log.
Put a line like:
local2.* /var/log/local2.log
in /etc/syslog.conf and you can see what is going on by using tail -f
local2.log on that log file on another console or xterm.
Hope this helps,
John
__________________________________________________________________
John Seifarth http://www.waw.be/waw/
Words & Wires SPRL [EMAIL PROTECTED]
Computer Consulting & Language Services Voice: (+) 32-2-660-3943
1160 Brussels, Belgium Fax: (+) 32-2-675-3922
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
