On Sun, 23 Jan 2000, Evan Alter wrote:
|I have confirmed and reconfirmed my user id and password.
|Interestingly, when using either Seyon or MS Hyperterm, my ISP rejected
|my attempts to login manually. The live, on-line tech support was
|friendly, but limited.
|
|I confirmed that my ISP is using PAP, set up /etc/ppp/pap-secrets,
|amended my chat script so that the last two lines read:
|
|TIMEOUT 75
|CONNECT \d\c
|
|and now, the end of my kernel message is:
|
|Jan 22 16:30:54 openG chat[1089]: CONNECT
|Jan 22 16:30:54 openG chat[1089]: -- got it
|Jan 22 16:30:54 openG chat[1089]: send (\d)
|Jan 22 16:30:55 openG pppd[1088]: Serial connection established.
|Jan 22 16:30:56 openG pppd[1088]: Using interface ppp0
|Jan 22 16:30:56 openG pppd[1088]: Connect: ppp0 <--> /dev/modem
|Jan 22 16:31:27 openG pppd[1088]: LCP: timeout sending Config-Requests
|Jan 22 16:37:42 openG pppd[1088]: Hangup (SIGHUP)
|Jan 22 16:37:42 openG pppd[1088]: Modem hangup
|Jan 22 16:37:42 openG pppd[1088]: Connection terminated.
|Jan 22 16:37:43 openG pppd[1088]: Exit.
Darn! That usually works. The large delay is still there too, which
may well mean that the ISP does expect something else from the chat
script. But the prompt I saw in one of your earlier mails showed a
"login:", and if you saw just the login/password prompts when you
tried to login via a terminal program then I'm at a lost to say what
the ISP wants.
The \d\c is the right thing most of the time but occasionally the ISP
won't like the extra second of delay. It won't hurt to try dropping
it and using just CONNECT \c instead, although it's really a rare
occurance. BTW you can read about the \d and \c in man chat.
I suppose that the ISP could want a login/password in addition to
PAP authentication. But then you would have seen it start sending LCP
negotiation messages, which would appear as "garbage" characters, after
entering your login name and password using the terminal program.
|I'm wondering, what does this mean: "LCP: timeout sending
|Config-Requests"
Here it means that pppd attempts to start PPP by sending Link Control
Protocol (LCP) messages to the peer and that the peer isn't answering.
In most cases it is almost certainly presenting a prompt or menu.
|Does it have something to do with modem settings, like init strings or
|baud rates?
It's highly unlikely. It's remotely possible that it could be caused by
an incorrect UART setting in the device file configuration. Check this
with "setserial /dev/ttyS2", the most common UART for PCs is a 16550A
and that's what you should see in the output of this command.
Your second post showed the pppd option "debug" so the detailed PPP link
negotiation messages should appear in one of the logs in /var/log, but it
depends on how /etc/syslog.conf is set up. If you can't find any then add
daemon.*;local2.* /var/log/ppp-log
to syslog.conf, create the file with "touch /var/log/ppp-log, and then do
" kill -HUP `pidof syslogd` " to restart syslogd. I'm not at all sure
that the detailed negotiation messages will help here, but nothing else
comes to mind.
---
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]
