You should start by replacing the  CONNECT ''  with  CONNECT '\d\c'  or
CONNECT \d\c  according as the chat script is on the chat command line or
in a separate file using the chat -f option.

The chat script seems to be flawed in other respects too.  In-line comments
below. 

On Tue, 15 Jun 1999, Miles D. Oliver wrote:

|Having trouble diagnosing a PPP connection betweeh a Linux box and
|a Solaris 7 x86 server, both running ppp 2.3.8
|
|I have the chat scripts working properly and can get PPP started but 
|there is a problem with the negotiation.  I cannot seem to find the info I
|need from a debug sequence.  
|
|The connection seems to timeout and drop after a few sections.
|
|Here is a copy of the PPP log on the Linux box.
|
|Jun 15 13:59:39 linux pppd[6659]: pppd 2.3.8 started by root, uid 0
|Jun 15 13:59:40 linux chat[6660]: send (ATD19373822139^M)
|Jun 15 13:59:40 linux chat[6660]: expect (CONNECT)
|Jun 15 13:59:58 linux chat[6660]: ATDxxxxxxxxxxxxx^M^M
|Jun 15 13:59:58 linux chat[6660]: CONNECT
|Jun 15 13:59:58 linux chat[6660]:  -- got it 
|Jun 15 13:59:58 linux chat[6660]: send (^M)

Here the carriage return that results from the chat script expect/send
CONNECT ''  is sent.

|Jun 15 13:59:58 linux chat[6660]: expect (ogin:)
|Jun 15 13:59:58 linux chat[6660]:  26400/ARQ^M
|Jun 15 13:59:58 linux chat[6660]: ^M^M
|Jun 15 13:59:58 linux chat[6660]: login:
|Jun 15 13:59:58 linux chat[6660]:  -- got it 

Here a login: prompt appears.

|Jun 15 13:59:58 linux chat[6660]: send (name^M)

You send "name^M" (?) for the login name.  That seems odd.

|Jun 15 13:59:58 linux chat[6660]: expect (assword:)
|Jun 15 13:59:58 linux chat[6660]:  ^M

Here's the carriage return from the chat script expect/send   CONNECT ''
arriving - 

|Jun 15 13:59:59 linux chat[6660]: login: root^M

- here's a second login: prompt that is immediately followed by "root^M"
which the chat script appears to have sent ??  What happened to "name^M"?

|Jun 15 13:59:59 linux chat[6660]: Password:
|Jun 15 13:59:59 linux chat[6660]:  -- got it 

The password prompt, but at this point I'm lost.  I can't really tell
what's arrived where or when, or what's real and what's not.

|Jun 15 13:59:59 linux chat[6660]: send (password^M)

But I think this password is as lost as I am since one second later -

|Jun 15 13:59:59 linux pppd[6659]: Serial connection established.
|Jun 15 13:59:59 linux pppd[6659]: Using interface ppp0
|Jun 15 13:59:59 linux pppd[6659]: Connect: ppp0 <--> /dev/ttyS1
|Jun 15 14:00:00 linux pppd[6659]: sent [LCP ConfReq id=0x1 <asyncmap 0x0> 
<magic 0xdedb7aad> <pcomp> <accomp>]
|Jun 15 14:00:00 linux pppd[6659]: rcvd [LCP ConfReq id=0x1 <asyncmap 0x0>
<magic 0xdedb7aad> <pcomp> <accomp>]

- pppd is talking to itself.  The sent message is identical to the rcvd
message, right down to the magic number - just as they are are all the
subsequent message pairs.

---
Clifford Kite                                               Not a guru. (tm)
[EMAIL PROTECTED]                                           Not even close.


-
To unsubscribe from this list: send the line "unsubscribe linux-ppp" in
the body of a message to [EMAIL PROTECTED]

Reply via email to