linux-ppp.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: James Cameron <james.cameron@hp.com>
To: linux-ppp@vger.kernel.org
Subject: Re: has anyone gotten PPP and MPPE working with kernel 2.6.x yet??
Date: Sun, 16 May 2004 23:29:33 +0000	[thread overview]
Message-ID: <20040516232933.GD27992@hp.com> (raw)
In-Reply-To: <1084670191.4575.151.camel@bast.picotech.net>

On Sat, May 15, 2004 at 07:16:31PM -0600, Jeffrey D. Means wrote:
> pppd options in effect: [...]
> plugin radius.so # (from /etc/ppp/options.pptpd) [...]
> sent [CHAP Success id=0xf1 "S'686CD047B851E473605718551CC73DA16E58FA"]
> MPPE required, but keys are not available. Possible plugin problem?
> sent [LCP TermReq id=0x4 "MPPE required but not available"]
> rcvd [LCP TermAck id=0x4 "MPPE required but not available"]

The radius plugin did not provide key material during the
authentication, and so MPPE cannot be started.

> In my mind this looks like a bug with the 2.6 kernel or could it be a
> bug with pppd??

In my mind it looks to be a bug with the radius plugin, or a
misconfiguration of the radius pppd options leading to the result
observed.  I don't see any evidence of kernel being the cause, yet.

(Perhaps it worked before but didn't after upgrade of only the kernel?
If you upgraded pppd or the radius plugin, I'd suspect it more than the
kernel.)

-- 
James Cameron                         http://quozl.netrek.org/
HP Open Source, Volunteer             http://opensource.hp.com/
PPTP Client Project, Release Engineer http://pptpclient.sourceforge.net/

  reply	other threads:[~2004-05-16 23:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-16  1:16 has anyone gotten PPP and MPPE working with kernel 2.6.x yet?? Jeffrey D. Means
2004-05-16 23:29 ` James Cameron [this message]
2004-05-17  5:19 ` Jeffrey D. Means
2004-05-17  5:33 ` James Cameron

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20040516232933.GD27992@hp.com \
    --to=james.cameron@hp.com \
    --cc=linux-ppp@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).