From: carlsonj@workingcode.com
To: linux-ppp@vger.kernel.org
Subject: Re: ppp 2.4.3 cvs authentication issue
Date: Thu, 28 Oct 2004 14:08:55 +0000 [thread overview]
Message-ID: <16768.64887.665355.330103@carlson.workingcode.com> (raw)
In-Reply-To: <20041028124517.7204.qmail@web25210.mail.ukl.yahoo.com>
a b writes:
> require-mschap-v2 # (from
> /etc/ppp/options.poptop)
> refuse-pap # (from
> /etc/ppp/options.poptop)
> refuse-chap # (from
> /etc/ppp/options.poptop)
> refuse-mschap # (from
> /etc/ppp/options.poptop)
> refuse-eap # (from
> /etc/ppp/options.poptop)
For what it's worth, you likely don't need all of those options. A
simple "auth" should do it -- and even that is not really required.
pppd automatically detects what credentials you have configured, and
will refuse authentication schemes that don't have appropriate
credentials.
This is by design. The defaults for the configuration options are
meant to make sense for most users. Having too many configuration
options specified is itself a symptom of a problem.
> sent [CCP ConfReq id=0x1 <mppe +H -M +S -L -D -C>]
> rcvd [CCP ConfReq id=0x1 <deflate 15> <deflate(old#)
> 15> <bsd v1 15>]
> MPPE required but peer negotiation failed
That looks like a combination of things. MPPE obviously has a bug --
it should not have just given up there, but rather sent Configure-Nak
first. The other thing is that the peer apparently isn't configured
to use MPPE.
--
James Carlson <carlsonj@workingcode.com>
next prev parent reply other threads:[~2004-10-28 14:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-28 12:45 ppp 2.4.3 cvs authentication issue a b
2004-10-28 12:54 ` carlsonj
2004-10-28 13:10 ` a b
2004-10-28 13:45 ` a b
2004-10-28 14:08 ` carlsonj [this message]
2004-10-28 14:52 ` a b
2004-10-28 15:00 ` carlsonj
2004-10-28 15:33 ` a b
2004-10-28 15:41 ` carlsonj
2004-10-28 15:52 ` a b
2004-10-28 15:57 ` carlsonj
2004-10-28 16:04 ` Bill Unruh
2004-10-28 16:07 ` Bill Unruh
2004-10-28 16:10 ` Bill Unruh
2004-10-28 17:01 ` a b
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=16768.64887.665355.330103@carlson.workingcode.com \
--to=carlsonj@workingcode.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.