On Fri, 25 Feb 2000, Juan Pablo Sales wrote:
|Feb 25 21:11:25 localhost pppd[613]: pppd 2.3.7 started by root, uid 0
|Feb 25 21:11:26 localhost chat[614]: timeout set to 3 seconds
|Feb 25 21:11:26 localhost chat[614]: abort on (\nBUSY\r)
|Feb 25 21:11:26 localhost chat[614]: abort on (\nNO ANSWER\r)
|Feb 25 21:11:26 localhost chat[614]: abort on\nRINGING\r\n\r\nRINGING\r)
|Feb 25 21:11:26 localhost chat[614]: send (rAT^M)
|Feb 25 21:11:26 localhost chat[614]: expect (OK)
|Feb 25 21:11:27 localhost chat[614]: rAT^M^M
|Feb 25 21:11:27 localhost chat[614]: OK
|Feb 25 21:11:27 localhost chat[614]: -- got it
|Feb 25 21:11:27 localhost chat[614]: send (ATH0^M)
|Feb 25 21:11:27 localhost chat[614]: timeout set to 30 seconds
|Feb 25 21:11:27 localhost chat[614]: expect (OK)
|Feb 25 21:11:27 localhost chat[614]: ^M
|Feb 25 21:11:27 localhost chat[614]: ATH0^M^M
|Feb 25 21:11:27 localhost chat[614]: OK
|Feb 25 21:11:27 localhost chat[614]: -- got it
|Feb 25 21:11:27 localhost chat[614]: send (ATDT4602000^M)
|Feb 25 21:11:27 localhost chat[614]: expect (CONNECT)
|Feb 25 21:11:27 localhost chat[614]: ^M
|Feb 25 21:11:51 localhost chat[614]: ATDT4602000^M^M
|Feb 25 21:11:51 localhost chat[614]: CONNECT
|Feb 25 21:11:51 localhost chat[614]: -- got it
|Feb 25 21:11:51 localhost chat[614]: send (^M)
Here the modem has connected with the ISP DCE and you've sent a carriage
return (^M). Nothing wrong yet.
|Feb 25 21:11:51 localhost chat[614]: expect (ogin:)
|Feb 25 21:11:51 localhost chat[614]: 9600^M
|Feb 25 21:11:58 localhost chat[614]: Bem-Vindo^M
|Feb 25 21:11:58 localhost chat[614]: ^M
|Feb 25 21:11:58 localhost chat[614]: ^M
|Feb 25 21:12:21 localhost chat[614]: alarm
|Feb 25 21:12:21 localhost chat[614]: send (^M)
Here your chat script expects a "ogin:" prompt from the ISP but it never
comes. There is another carriage return sent.
|Feb 25 21:12:21 localhost chat[614]: expect (ogin:)
|Feb 25 21:12:21 localhost chat[614]: ^M
|Feb 25 21:12:51 localhost pppd[613]: Connect script failed
|Feb 25 21:12:51 localhost chat[614]: alarm
|Feb 25 21:12:52 localhost pppd[613]: Exit.
|Feb 25 21:12:51 localhost chat[614]: Failed
The script is written to try again to expect "ogin:" from the ISP which
again does come. The chat script times out and pppd exits.
The chat script is not doing what is necessary to get past whatever the ISP
is doing instead of presenting the expected "login:" prompt. This is a
different problem that what you described in your earlier post. It might
be as simple as using CONNECT '\d\c' instead of CONNECT '' in the chat
script (eliminating the carriage return from '' which sometimes confuses an
ISP) but it could easily be something else.
You should try to find out what the ISP wants to start PPP, a
login/password only, a login/password plus something extra that will start
PPP at the ISP, or maybe even no login/password with authentication done
using either the PPP PAP or CHAP protocol.
You *might* get some idea of what the ISP is looking for by using minicom
to call the ISP to see what, if any, prompts it presents. It also might be
worthwhile to configure pppd to do PAP or CHAP authentication and see what
happens that way with no chat login/password expect-sends after the
CONNECT '\d\c'.
---
Clifford Kite Not a guru. (tm)
-
To unsubscribe from this list: send the line "unsubscribe linux-ppp" in
the body of a message to [EMAIL PROTECTED]
