On Fri, 30 Apr 1999, Alan E. Derhaag wrote:
|Clifford Kite <[EMAIL PROTECTED]> writes:
|
|> Just what is the problem? If you configure noccp then pppd can't negotiate
|> CCP so ProtRej is correct. If you allow CCP negotiation and neither pppd
|> or the peer can provide a compression algorithm that the other requests
|> then ConfRej is correct for the ones that are requested.
|>
|> No CCP compression isn't a great loss anymore since most ISPs and their
|> clients now use compression implemented in hardware to send compressed
|> data over the wire.
|>
|
|I don't know.. I'm grasping at straws now. I saw the reference to a
|possible solution but that was with authorization not compression. I
|had no feed back on other postings of the problem but that was to the
|newsgroup (comp.protocols.ppp) not the maillist so here goes.. The
|following listing is from the logging with debug and kdebug 27 (even
|though the kdebug doesn't seem to work in connection with pptp). I'm
|trying to find the indication of why the TermReq in the following listing:
Yes, I saw the post and wasn't able to speculate as to what caused the
problem. The ppp link negotiations go great until just one Ack away from
success and wham! it gets a LCP TermReq which is fatal. I also have no
experience with pptp and don't know how PPP and PPTP relate.
Maybe with more information something will suggest itself to me or someone
else. But first get rid of "kdebug 27" - it's a RH red herring. The
acceptable kdebug values are the integers 0 through 7, or put another way,
each kdebug value is a three bit bitmask, each bit turning on or off a
different layer of debug. Read about it in "man pppd."
Some things to check on:
The timestamps for "chat -v" messages (/var/log/messages ?), are there any
modem initialization expect/sends and if so is the time between sending the
command and receiving the modem's OK longer than one second.
Does the modem connect with a reasonable speed? The modem connection speed
is usually found in a chat message with proper modem configuration.
The UART setting for the modem device file, is it correct? Is the serial
port UART appropriate for the speed of the modem, if the modem is external.
"setserial /dev/ttySx" shows these for the device file /dev/ttySx.
Are the internal modem settings reasonable? Minicom and AT&V will show
these.
Are the pppd options suitable? Is crtscts present? Have you tried the
option "asyncmap 0" rather than "asyncmap a0000" ?
Is the modem known to work correctly with another program or OS or kernel?
A recent Zoom modem apparently caused some folks trouble until they
downloaded and applied a firmware upgrade.
If you use a 2.0.x kernel does "stty /dev/ttySx" show a speed of 38400 or
115200, or whatever you asked for in the pppd speed option? This will need
to be done in the period of time that PPP negotiations are taking place,
or you'll need to reboot and do it before using pppd.
Is it possible that the peer can be configured to require MS-PPC which is
proprietary and pppd must -and does- reject?
|Connect: ppp0 <--> /dev/ttya0
Hmm.. ttya0 is new to me. The rest of the log looks good until the very
end.
---
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]
