On Mon, 3 Jan 100 [EMAIL PROTECTED] wrote:
|Here is the chat script on the client:
|
|/usr/sbin/pppd -d connect '/usr/sbin/chat -v "" AT OK ATDTxxxxxxx CONNECT
|"" ogin: me ord: \
|secret $ /etc/ppp/ppplogin'
|
|Here is the chat script logging in successfully when pppd 2.2.0 is
|on the PPP server with the debug info from the PPP server:
|
|Jan 3 12:43:25 chime pppd[4871]: pppd 2.3.7 started by root, uid 0
|Jan 3 12:43:26 chime chat[4873]: send (AT^M)
|Jan 3 12:43:26 chime chat[4873]: expect (OK)
|Jan 3 12:43:26 chime chat[4873]: AT^M^M
|Jan 3 12:43:26 chime chat[4873]: OK
|Jan 3 12:43:26 chime chat[4873]: -- got it
|......
|
|Jan 3 12:43:43 chime chat[4873]: ~^?}#@!}!}!} }2}!}$
|Jan 3 12:43:43 chime chat[4873]: -- got it
|Jan 3 12:43:43 chime chat[4873]: send (/etc/ppp/ppplogin^M)
|Jan 3 12:43:44 chime pppd[4871]: Serial connection established.
|Jan 3 12:43:44 chime pppd[4871]: Using interface ppp0
|Jan 3 12:43:44 chime pppd[4871]: Connect: ppp0 <--> /dev/ttyS0
Look at what's happening here. Chime gets part of a PPP LCP message from
orbital *before* chat is finished with it's assigned task. That has to
mean that you set up orbital to launch pppd in /etc/passwd so you can't
really expect a shell prompt from orbital.
You got lucky because the 2.2.0 pppd on orbital requests an mru of 1500
which is a 4 byte option and the option length is sent in the LCP request.
At this point in the LCP negotiations all control characters are escaped
and 4 is a control character. So 4 is XOR with 20h and the result is 24h
which is the ASCII $.
That is the $ that chat on chime found, not a shell login prompt; then it
sent /etc/ppp/ppplogin and that was discarded by the already running pppd
on orbital. At that point the chime chat was finished handed control back
to the chime pppd and LCP negotiations actually finished and resulted in a
viable PPP connection.
The 2.3.7 pppd on orbital didn't request a mru at all and so had no 4 to
escape and XOR with 20h, nor did it send a straight 24h. The chime chat
waited for the $ and then timed out (the "alarm"), but orbital had already
hungup. There were no LCP negotiations since the chime pppd never got a
chance to start, and thus the PPP connection failed.
It should work for both pppd versions if you just delete the
$ /etc/ppp/ppplogin
from the chime chat script.
BTW did you notice that your mailer or your host clock has a Y2K bug?
Either that or you've time-traveled back to 100 A.D. and are using an
Interchronologicalnet.
---
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]
