On Fri, May 14, 1999 at 09:37:43AM -0500, Michael Chi Dang wrote:
> May 14 03:37:06 localhost pppd[761]: pppd 2.3.7 started by root, uid 0
> May 14 03:37:06 localhost ifup-ppp: pppd started for ppp0 on /dev/modem at 115200
> May 14 03:37:07 localhost chat[763]: abort on (BUSY)
> May 14 03:37:07 localhost chat[763]: abort on (ERROR)
[ snip a bunch of stuff ]
> May 14 03:37:32 localhost chat[763]: Entering PPP mode.^M
> May 14 03:37:32 localhost chat[763]: Async interface address is unnumbered
>(Ethernet0)^M
> May 14 03:37:32 localhost chat[763]: Your IP address is 128.83.254.167. MTU is 1500
>bytes^M
> May 14 03:37:32 localhost chat[763]: Header compression will match your system.^M
> May 14 03:37:32 localhost chat[763]: ^M
> May 14 03:37:35 localhost chat[763]: ~~^?}#@!}!}+} }4}"}&} }*} } }%}&
> May 14 03:37:37 localhost chat[763]: 'q3}'}"}(}"-g~~^?}#@!}!},} }4}"}&} }*} } }%}&
> May 14 03:37:39 localhost chat[763]: 'q3}'}"}(}"a}'~~^?}#@!}!}-} }4}"}&} }*} } }%}&
> May 14 03:38:00 localhost pppd[761]: Exit.
It's been a while, but at the point where you see all that
garbage printing out near the bottom, chat should have started
pppd to run the binary ppp protocol. But the log entries
indicate that chat is still trying to run instead of doing so.
1. Make sure your chat script (or whatever you're using) knows to
terminate and start pppd when you receive a string like 'Your
IP address is'.
2. Make sure that the option "silent" does _not_ appear in your
pppd options config file (on my Debian system, it's
/etc/ppp/options).
3. My chat script is actually much simpler than yours, because I
use pap authentication. The chat script just looks like this:
ABORT BUSY
ABORT "NO CARRIER"
ABORT VOICE
ABORT "NO DIALTONE"
ABORT "NO ANSWER"
REPORT "CARRIER"
REPORT "CONNECT"
"" ATZ
OK ATDT4759996
CONNECT \d\c
chat doesn't do the login. It just starts pppd as soon as the
modem connection is made. Then, in your pap-secrets file
(/etc/ppp/pap-secrets on Debian) you just need one line at the
bottom to have pppd do the authentication (i.e., login) for
you. It looks like this:
yourUsername * yourPassword
And finally, in your peers config file (/etc/ppp/peers/telesys
on my machine), you need a line like:
user yourUsername
I'm not completely positive it works the same in RedHat as it
does on my Debian system, but I'd bet it does. I call pppd
like this:
pppd call telesys
where the last arg is the name of the config file in
/etc/ppp/peers/. It looks like this on my machine:
noauth
connect "/usr/sbin/chat -v -r /var/log/ppp.log -f /etc/chatscripts/telesys"
/dev/ttyS1
57600
defaultroute
noipdefault
user rkilgore
Anyway, pap authentication is more reliable (at least here at
UT) and probably slightly more secure, so I'd recommend using
it if it's not too much of a bother to do so.
Hope this helps.
later,
- rick
--
Richard Kilgore | [EMAIL PROTECTED]
Electrical & Computer Engineering | http://lore.ece.utexas.edu/~rkilgore/
The University of Texas at Austin | (512) 471-8011
---------------------------------------------------------------------------
Send administrative requests to [EMAIL PROTECTED]
