On Sat, 22 Jan 2000, Mithun Bhattacharya wrote:
|Oh well I will take Cliff's word for granted on the PMTU issue but I would
|still like to know why is ppp throwing away all the compression on my
|connection. As noted by few other users ppp 2.3.10 seems to be facing a
The peer and pppd have no common CCP algorithms. That's very common
since usually the ISP implements STAC Electronics LZS compression or
Microsoft PPC (MS-PPC), both of which require a license from STAC.
These are not implemented in pppd because of the licensing requirement.
Your ISP was willing to do predictor1 but it appears that the PPP
kernel support code doesn't support that. I don't know why, perhaps
Paul Mackerras could enlighten us both.
|LCP timeout problems too. Even debug mode doesn't tell us anything - just
|shows that we are sending out LCP's and not hearing anything in return.
This is a common problem. It's usually because the chat script
has not allowed the ISP to start PPP at it's end of the connection.
The reason for the failure varies but the chat -v log messages are
usually enough to suggest what might be happening and what might be
done to correct it. Since the ISPs support Microsoft, exclusively
for the most part, the Winxx users don't have this problem.
|Other than that I am seeing a lot of unknown protocol/ protocol rejected.
Anything that pppd doesn't implement is rejected. Most things that
aren't implemented are not implemented due to a software patent or a
licensing requirement, or both. In your case the peer offered both
STAC CCP and MS-PPC which pppd rejected without identifying them.
|Has something been happening in the windows version of PPP that the Linux
|community is not aware of - most probably it is all patented and locked
Microsoft is a barracuda but, no, it's very unlikely they've done
anything to cause problems with PPP that the Linux community hasn't
identified. There have been a couple of posts recently where MS-PPC
had a Microsoft encryption (MPPE) option turned on and *required*
that the client be able to use it, but it's rare - so far. BTW the
MS-PPC message in your log showed that MPPC was not turned on.
|away if it is new. Or are these covered in ppp-2.3.11 I can't test it
|right now as I have access to the modem only on the production box and I
|am not going to do a upgrade unless it is necessary for security or
There's not anything different between ppp-2.3.10 and ppp-2.3.11 that
would address the concerns you expessed. Except that it may be able
to identify more rejected protocols by name in the Configure-Reject
message.
|performance reasons. The documentation doesn't seem to suggest either but
|code and documentation might not be in sync who knows!!.
Documentation is always secondary to development. Pppd's could use a
little spiffing up here and there but it is generally up to date.
---
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]
